From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 02:26:13 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 4DFA129B for ; Sun, 27 Jan 2013 02:26:13 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-ve0-f173.google.com (mail-ve0-f173.google.com [209.85.128.173]) by mx1.freebsd.org (Postfix) with ESMTP id E452FA73 for ; Sun, 27 Jan 2013 02:26:12 +0000 (UTC) Received: by mail-ve0-f173.google.com with SMTP id oz10so175951veb.18 for ; Sat, 26 Jan 2013 18:26:06 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=RgEYslhCP0pr3dAcyO15Fs6d0+so6VwdKaaOo/ePwmc=; b=M16xYGef/Y4uW2VRc+GHCN2u4zEYfYLmxA1ZRQmbOLdhr7hOOLt4+kCa+Fv4Btumwd gzkwo1cG1JjrpMgaXoZPRIzW1D5zr/lGMOMplm7rwxF3nY/zR1allVBFrltNFOYfU+4C /cffA2Nz/ugGsymlM1gY6OYD3/3XNUR9R/Mrc+YczeI5KtCzgpq1sTmqabz4TAey3yUA R0V596RMxAX3dJ/q0a7Eu6T0g5167Zm+qZzIYh2BTT2vUz3UvaCN2KecLeNMcXvY/AJP lSuM5ql8hFmB8HuIomxLcaisYaEJ8WpnStkEL3XaNWkH+sWB702NRAP9n7EGOKqMUIiB vebw== MIME-Version: 1.0 X-Received: by 10.52.155.205 with SMTP id vy13mr9597099vdb.119.1359253566079; Sat, 26 Jan 2013 18:26:06 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.58.206.105 with HTTP; Sat, 26 Jan 2013 18:26:05 -0800 (PST) In-Reply-To: <1359240382.8698.60.camel@eva02> References: <1359223263.8698.17.camel@eva02> <51042871.2090605@martenvijn.nl> <1359240382.8698.60.camel@eva02> Date: Sat, 26 Jan 2013 18:26:05 -0800 X-Google-Sender-Auth: SFUwm8PQjLGeI4TuhcoaddTDShI Message-ID: Subject: Re: stuck beacon hung wifi adapter AR5008 From: Adrian Chadd To: paranormal Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 02:26:13 -0000 Hi, So the AR5416 and later NICs almost all implement MIMO. The only exception is the AR9285 which is a 1x1 with the diversity implementation matching previous (pre-11n) NICs. Anyway, for MIMO, all the antennas are on by default. So yes, you need to connect all of the antennas. If you want to avoid this, you can override things. I _think_ it's: hint.dev.ath.0.rx_antenna=0x5 hint.dev.ath.0.tx_antenna=0x5 in /boot/loader.conf If it's not that, it's hint.ath.0.xxx .. Then connect antennas to the connectors marked "chain 0" and "chain 2". The boot messages should then say that the RX and TX chainmasks are being set. Otherwise - yes, connect all three! Adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 10:06:17 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 63AE4552 for ; Sun, 27 Jan 2013 10:06:17 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 23757931 for ; Sun, 27 Jan 2013 10:06:17 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2577:cf36:d0d4:4986]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id CA9F24AC2D; Sun, 27 Jan 2013 14:06:11 +0400 (MSK) Date: Sun, 27 Jan 2013 14:06:05 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1102411019.20130127140605@serebryakov.spb.ru> To: paranormal Subject: Re: stuck beacon hung wifi adapter AR5008 In-Reply-To: <1359223263.8698.17.camel@eva02> References: <1359223263.8698.17.camel@eva02> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 10:06:17 -0000 Hello, paranormal. You wrote 26 =D1=8F=D0=BD=D0=B2=D0=B0=D1=80=D1=8F 2013 =D0=B3., 22:01:03: p> 70 Jan 26 17:41:48 mbsd kernel: ath0: stuck beacon; resetting (bmiss p> count 4) =20 p> 71 Jan 26 17:42:02 mbsd last message repeated 62 p> times =20 I have almost same problem with my 9220 ath0: mem 0xa0060000-0xa006ffff irq 15 at device 17.0 on pci0 [ath] enabling AN_TOP2_FIXUP [ath]: default pwr offset: -5 dBm !=3D EEPROM pwr offset: 0 dBm; curves wil= l be adjusted. ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams; 2 TX streams ath0: AR9220 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 And, yes, I have both antennas connected. It doesn't hang forever, driver is able to reset it, but all clients disassociate and need to associate again in such case (pause in WiFi service could be more than 1 minute). I can not see whole film on my notebook without interruption :( I'm using -HEAD... --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 12:31:38 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 005212BC for ; Sun, 27 Jan 2013 12:31:37 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id 97347E18 for ; Sun, 27 Jan 2013 12:31:37 +0000 (UTC) Received: from vincemacbook.unsane.co.uk (vincemacbook.unsane.co.uk [10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.6/8.14.6) with ESMTP id r0RCVYrL005022 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO) for ; Sun, 27 Jan 2013 12:31:35 GMT (envelope-from vince@unsane.co.uk) Message-ID: <51051E26.1050300@unsane.co.uk> Date: Sun, 27 Jan 2013 12:31:34 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: "freebsd-wireless@freebsd.org" Subject: wireless link flaps (ath ar9280) X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 12:31:38 -0000 Hi all, I'm running a recent -current (r245741) and seem to be getting interface flaps. Since this machine is mainly used for home mail and a little light file serving I'm not sure when they started occuring as i only have logging going back to the 18th Jan. Sample log messages are: Jan 24 16:26:22 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 24 16:26:22 ostracod kernel: AR_CR=0x00000024 Jan 24 16:26:22 ostracod kernel: AR_DIAG_SW=0x42000020 Jan 24 16:26:23 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED bssid=e0:91:f5:48:5b:b9 reason=0 Jan 24 16:26:23 ostracod kernel: wlan0: link state changed to DOWN Jan 24 16:26:26 ostracod wpa_supplicant[568]: Trying to associate with e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) Jan 24 16:26:26 ostracod wpa_supplicant[568]: Associated with e0:91:f5:48:5b:b9 Jan 24 16:26:26 ostracod kernel: wlan0: link state changed to UP Jan 24 16:26:27 ostracod wpa_supplicant[568]: WPA: Key negotiation completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] I sometime get just Jan 25 00:57:36 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 25 00:57:36 ostracod kernel: AR_CR=0x00000024 Jan 25 00:57:36 ostracod kernel: AR_DIAG_SW=0x42000020 or Jan 25 09:39:24 ostracod wpa_supplicant[568]: WPA: Group rekeying completed with e0:91:f5:48:5b:b9 [GTK=TKIP] Jan 25 09:41:13 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 25 09:41:13 ostracod kernel: AR_CR=0x00000024 Jan 25 09:41:13 ostracod kernel: AR_DIAG_SW=0x42000020 Jan 25 09:46:50 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 25 09:46:50 ostracod kernel: AR_CR=0x00000024 Jan 25 09:46:50 ostracod kernel: AR_DIAG_SW=0x42000020 Jan 25 09:49:24 ostracod wpa_supplicant[568]: WPA: Group rekeying completed with e0:91:f5:48:5b:b9 [GTK=TKIP] Jan 25 09:52:10 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 25 09:52:10 ostracod kernel: AR_CR=0x00000024 Jan 25 09:52:10 ostracod kernel: AR_DIAG_SW=0x42000020 Jan 25 09:57:07 ostracod kernel: ath0: bb hang detected (0x4), resetting or Jan 26 17:24:46 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 26 17:24:46 ostracod kernel: AR_CR=0x00000024 Jan 26 17:24:46 ostracod kernel: AR_DIAG_SW=0x42000020 Jan 26 17:25:31 ostracod kernel: ar5416PerCalibrationN: NF calibration didn't finish; delaying CCA with no interface flaps. And sometimes much more info Jan 25 16:56:27 ostracod kernel: ar5416StopDmaReceive: dma failed to stop in 10ms Jan 25 16:56:27 ostracod kernel: AR_CR=0x00000024 Jan 25 16:56:27 ostracod kernel: AR_DIAG_SW=0x42000020 Jan 25 16:56:28 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED bssid=e0:91:f5:48:5b:b9 reason=0 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff8014828000: bf=0xffffff80008b23e8: addbaw=1, dobaw=1, seqno=3447, retry=6 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8014828000: bf=0xffffff80008b23e8: txq[1] axq_depth=0, axq_aggr_depth=0 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8014828000: bf=0xffffff80008b23e8: tid txq_depth=10 hwq_depth=0, bar_wait=1, isfiltered=0 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node 0xffffff8014828000: tid 0: sched=0, paused=1, incomp=0, baw_head=114, baw_tail=116 txa_start=3446, ni_txseqs=3456 Jan 25 16:56:28 ostracod kernel: TODS 00:24:23:07:fb:5d->e0:91:f5:48:5b:b9(e0:91:f5:48:5b:b9) data QoS [TID 0] WEP [IV b6 89 00 0c 00 00 KID 0] 0M Jan 25 16:56:28 ostracod kernel: 8849 0000 e091 f548 5bb9 0024 2307 fb5d e091 f548 5bb9 70d7 0000 dec0 b689 0020 0c00 0000 aaaa 0300 0000 0800 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3448 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3449 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3450 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3451 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3452 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3453 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3454 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 3455 Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008a9e08: seqno 3448: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008aa468: seqno 3449: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008c8a80: seqno 3450: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008cf080: seqno 3451: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008a8488: seqno 3452: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008a64a8: seqno 3453: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008aa930: seqno 3454: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008a8ae8: seqno 3455: dobaw should've been cleared! Jan 25 16:56:28 ostracod kernel: wlan0: link state changed to DOWN Jan 25 16:56:39 ostracod wpa_supplicant[568]: Trying to associate with e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) Jan 25 16:56:39 ostracod wpa_supplicant[568]: Associated with e0:91:f5:48:5b:b9 Jan 25 16:56:39 ostracod kernel: wlan0: link state changed to UP Jan 25 16:56:40 ostracod wpa_supplicant[568]: WPA: Key negotiation completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] Device is ath0: mem 0xfebf0000-0xfebfffff irq 16 at device 0.0 on pci4 ath0: [HT] enabling HT modes ath0: [HT] 2 RX streams; 1 TX streams ath0: AR9280 mac 128.2 RF5133 phy 13.0 ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 Any suggestions? I'm happy to provide more info if needed. Vince From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 17:11:46 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 29756E39 for ; Sun, 27 Jan 2013 17:11:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by mx1.freebsd.org (Postfix) with ESMTP id 9BB51BF4 for ; Sun, 27 Jan 2013 17:11:45 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn14so816623wib.10 for ; Sun, 27 Jan 2013 09:11:38 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=xXz/MHf0aaDYJaoGZFMXWfk1aHS8F7lR6GmppASAhd4=; b=DXtuoDNOBtAyfXyyNGeiEWJZ7afOOEWG/0ELhp8idy37beOfuHfT1lPAXknHl4ogR0 EHAyso3HwSjCnY/ImNy4objBcIUIFZVQBdxH0FSHgt9PkOV9LwJZcSqDbLpT3aFPy4ZX Rfg3pjmdFywHcvYdK92IiGsqdSemb1S5hUyZSebBiTjKHR2gsVTySiyX5VChnoPbOzFP ush526hUj415sth3rOHy9mPdCeccqO26y3aSPu/DQkBoid56ZoQWONurKFHDa8+FX8mE IhOxdV3W/dlqbLuQFj2/Lwg0DACfPdWHEt+o4r1ZrANtQsGRDn2Bzm5pMsumRV2y98KH IohQ== MIME-Version: 1.0 X-Received: by 10.194.172.197 with SMTP id be5mr17161476wjc.20.1359306698422; Sun, 27 Jan 2013 09:11:38 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Sun, 27 Jan 2013 09:11:38 -0800 (PST) In-Reply-To: <51051E26.1050300@unsane.co.uk> References: <51051E26.1050300@unsane.co.uk> Date: Sun, 27 Jan 2013 09:11:38 -0800 X-Google-Sender-Auth: bGYmhUbeLnJ8j21N34RPjJZVfdw Message-ID: Subject: Re: wireless link flaps (ath ar9280) From: Adrian Chadd To: Vincent Hoffman Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 17:11:46 -0000 Hm, see if it's a beacon miss thing: sysctl dev.ath.0.debug=0x80 adrian On 27 January 2013 04:31, Vincent Hoffman wrote: > Hi all, > I'm running a recent -current (r245741) and seem to be getting > interface flaps. Since this machine is mainly used for home mail and a > little light file serving I'm not sure when they started occuring as i > only have logging going back to the 18th Jan. > > Sample log messages are: > Jan 24 16:26:22 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 24 16:26:22 ostracod kernel: AR_CR=0x00000024 > Jan 24 16:26:22 ostracod kernel: AR_DIAG_SW=0x42000020 > Jan 24 16:26:23 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED > bssid=e0:91:f5:48:5b:b9 reason=0 > Jan 24 16:26:23 ostracod kernel: wlan0: link state changed to DOWN > Jan 24 16:26:26 ostracod wpa_supplicant[568]: Trying to associate with > e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) > Jan 24 16:26:26 ostracod wpa_supplicant[568]: Associated with > e0:91:f5:48:5b:b9 > Jan 24 16:26:26 ostracod kernel: wlan0: link state changed to UP > Jan 24 16:26:27 ostracod wpa_supplicant[568]: WPA: Key negotiation > completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] > > I sometime get just > > > > Jan 25 00:57:36 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 25 00:57:36 ostracod kernel: AR_CR=0x00000024 > Jan 25 00:57:36 ostracod kernel: AR_DIAG_SW=0x42000020 > > or > > Jan 25 09:39:24 ostracod wpa_supplicant[568]: WPA: Group rekeying > completed with e0:91:f5:48:5b:b9 [GTK=TKIP] > Jan 25 09:41:13 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 25 09:41:13 ostracod kernel: AR_CR=0x00000024 > Jan 25 09:41:13 ostracod kernel: AR_DIAG_SW=0x42000020 > Jan 25 09:46:50 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 25 09:46:50 ostracod kernel: AR_CR=0x00000024 > Jan 25 09:46:50 ostracod kernel: AR_DIAG_SW=0x42000020 > Jan 25 09:49:24 ostracod wpa_supplicant[568]: WPA: Group rekeying > completed with e0:91:f5:48:5b:b9 [GTK=TKIP] > Jan 25 09:52:10 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 25 09:52:10 ostracod kernel: AR_CR=0x00000024 > Jan 25 09:52:10 ostracod kernel: AR_DIAG_SW=0x42000020 > Jan 25 09:57:07 ostracod kernel: ath0: bb hang detected (0x4), resetting > > or > > Jan 26 17:24:46 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 26 17:24:46 ostracod kernel: AR_CR=0x00000024 > Jan 26 17:24:46 ostracod kernel: AR_DIAG_SW=0x42000020 > Jan 26 17:25:31 ostracod kernel: ar5416PerCalibrationN: NF calibration > didn't finish; delaying CCA > > with no interface flaps. > And sometimes much more info > > Jan 25 16:56:27 ostracod kernel: ar5416StopDmaReceive: dma failed to > stop in 10ms > Jan 25 16:56:27 ostracod kernel: AR_CR=0x00000024 > Jan 25 16:56:27 ostracod kernel: AR_DIAG_SW=0x42000020 > Jan 25 16:56:28 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED > bssid=e0:91:f5:48:5b:b9 reason=0 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: norm: > node 0xffffff8014828000: bf=0xffffff80008b23e8: addbaw=1, dobaw=1, > seqno=3447, retry=6 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node > 0xffffff8014828000: bf=0xffffff80008b23e8: txq[1] axq_depth=0, > axq_aggr_depth=0 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node > 0xffffff8014828000: bf=0xffffff80008b23e8: tid txq_depth=10 hwq_depth=0, > bar_wait=1, isfiltered=0 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node > 0xffffff8014828000: tid 0: sched=0, paused=1, incomp=0, baw_head=114, > baw_tail=116 txa_start=3446, ni_txseqs=3456 > Jan 25 16:56:28 ostracod kernel: TODS > 00:24:23:07:fb:5d->e0:91:f5:48:5b:b9(e0:91:f5:48:5b:b9) data QoS [TID 0] > WEP [IV b6 89 00 0c 00 00 KID 0] 0M > Jan 25 16:56:28 ostracod kernel: 8849 0000 e091 f548 5bb9 0024 2307 fb5d > e091 f548 5bb9 70d7 0000 dec0 b689 0020 0c00 0000 aaaa 0300 0000 0800 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3448 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3449 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3450 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3451 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3452 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3453 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3454 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 3455 > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008a9e08: seqno 3448: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008aa468: seqno 3449: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008c8a80: seqno 3450: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008cf080: seqno 3451: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008a8488: seqno 3452: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008a64a8: seqno 3453: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008aa930: seqno 3454: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008a8ae8: seqno 3455: dobaw should've been cleared! > Jan 25 16:56:28 ostracod kernel: wlan0: link state changed to DOWN > Jan 25 16:56:39 ostracod wpa_supplicant[568]: Trying to associate with > e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) > Jan 25 16:56:39 ostracod wpa_supplicant[568]: Associated with > e0:91:f5:48:5b:b9 > Jan 25 16:56:39 ostracod kernel: wlan0: link state changed to UP > Jan 25 16:56:40 ostracod wpa_supplicant[568]: WPA: Key negotiation > completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] > > > Device is > ath0: mem 0xfebf0000-0xfebfffff irq 16 at device 0.0 on pci4 > ath0: [HT] enabling HT modes > ath0: [HT] 2 RX streams; 1 TX streams > ath0: AR9280 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > Any suggestions? I'm happy to provide more info if needed. > > Vince > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 17:17:56 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 8D54292F; Sun, 27 Jan 2013 17:17:56 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wg0-f44.google.com (mail-wg0-f44.google.com [74.125.82.44]) by mx1.freebsd.org (Postfix) with ESMTP id F2315CD5; Sun, 27 Jan 2013 17:17:55 +0000 (UTC) Received: by mail-wg0-f44.google.com with SMTP id dr12so605738wgb.11 for ; Sun, 27 Jan 2013 09:17:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type :content-transfer-encoding; bh=CRouuig0asw1Lb8Om+BSrYwIzqQ96iaNfOltTOZj/zM=; b=AqWKofZBXhPswL8bfFhqLKEVuO+OMTXHg76TqdzlmbB/WvY/oQBmsK1WvTWyua9/DZ 0RGnwDY6tNRP37ZLYYfypPUGzttd1+W/OGNB7+GJz5yaj4sN/zNsxmnamNe/5D/cJUAK 6cwUHbtqm8CUDIiGl+rwD21V3kmkRL2zx/EWGNhjPPpoZRJ5arSiu8LgxCuh2kYzUxbb 4hoXcH6XLZjqoczc3lRoexr/2R3+UqJugjAVZSLdwMJLFZzPiXqTF9kJH2Ej6BcDIx9p Ta6leVvoXUb/NV2UXmbbQulHAAdLk6zO8RQs6zQob+JVgJzvdeyqC9KuqoSTZiSzvI7u pxgw== MIME-Version: 1.0 X-Received: by 10.180.90.147 with SMTP id bw19mr5805687wib.28.1359307068888; Sun, 27 Jan 2013 09:17:48 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Sun, 27 Jan 2013 09:17:48 -0800 (PST) In-Reply-To: <1102411019.20130127140605@serebryakov.spb.ru> References: <1359223263.8698.17.camel@eva02> <1102411019.20130127140605@serebryakov.spb.ru> Date: Sun, 27 Jan 2013 09:17:48 -0800 X-Google-Sender-Auth: vynIOLY5l7S4gry30WxpPwprbZA Message-ID: Subject: Re: stuck beacon hung wifi adapter AR5008 From: Adrian Chadd To: Lev Serebryakov Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Cc: paranormal , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 17:17:56 -0000 Are you using it in HT40 or HT20 mode? For 2GHz in noisy environments, use it in HT20 mode. adrian On 27 January 2013 02:06, Lev Serebryakov wrote: > Hello, paranormal. > You wrote 26 =D1=8F=D0=BD=D0=B2=D0=B0=D1=80=D1=8F 2013 =D0=B3., 22:01:03: > > p> 70 Jan 26 17:41:48 mbsd kernel: ath0: stuck beacon; resetting (bmiss > p> count 4) > p> 71 Jan 26 17:42:02 mbsd last message repeated 62 > p> times > I have almost same problem with my 9220 > > ath0: mem 0xa0060000-0xa006ffff irq 15 at device 17.0 on p= ci0 > [ath] enabling AN_TOP2_FIXUP > [ath]: default pwr offset: -5 dBm !=3D EEPROM pwr offset: 0 dBm; curves w= ill be adjusted. > ath0: [HT] enabling HT modes > ath0: [HT] 2 RX streams; 2 TX streams > ath0: AR9220 mac 128.2 RF5133 phy 13.0 > ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 > > And, yes, I have both antennas connected. It doesn't hang forever, > driver is able to reset it, but all clients disassociate and need to > associate again in such case (pause in WiFi service could be more than > 1 minute). I can not see whole film on my notebook without > interruption :( > > I'm using -HEAD... > > -- > // Black Lion AKA Lev Serebryakov > > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 17:45:06 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id BEDCA5A1; Sun, 27 Jan 2013 17:45:06 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 78076DD3; Sun, 27 Jan 2013 17:45:06 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2577:cf36:d0d4:4986]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 7646B4AC32; Sun, 27 Jan 2013 21:45:03 +0400 (MSK) Date: Sun, 27 Jan 2013 21:44:57 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <1255037243.20130127214457@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: stuck beacon hung wifi adapter AR5008 In-Reply-To: References: <1359223263.8698.17.camel@eva02> <1102411019.20130127140605@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: paranormal , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 17:45:06 -0000 Hello, Adrian. You wrote 27 =D1=8F=D0=BD=D0=B2=D0=B0=D1=80=D1=8F 2013 =D0=B3., 21:17:48: AC> Are you using it in HT40 or HT20 mode? AC> For 2GHz in noisy environments, use it in HT20 mode. I'm using HT20, and it seems, card in my box overheats with 802.11n clients (it hangs very hard under load with 802.11n client), so I don't use 802.11n on notebook (I want to change box to new one, atom-based, but every month here are more high-priority expenditures than $200+ on MoBo, case, memory, etc). --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 17:59:34 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AE128929; Sun, 27 Jan 2013 17:59:34 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by mx1.freebsd.org (Postfix) with ESMTP id F1A6AE48; Sun, 27 Jan 2013 17:59:33 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn14so833296wib.16 for ; Sun, 27 Jan 2013 09:59:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=6qRoW9G/EouHRQlxO5JEpWN9X7uKRejgsX3gAKTLwlY=; b=v23rb1az9YISHl0KeKUG3/Rg4FEin38ujh3ET/oFVnm6MXyMYzyPwFC2MCyCZ2BY4j 5m6ooFdvsxtVxQ8zQzT2AfD8hKMKtVIq9+HHu8EXWl7VmETljR+zfx50q6RE+a6a6Mqe 5pYRiiZ7FDh6ZxpYqxEYm+sVVgba8taPXAeZSt91uUl1r66jgeYFPULm4d7OBzRywNRe oEzFw8ERbFabEl04VuOFh8bTbbwDLL187cyBn7RCPpiNGkDDAW3rt8ElAHLdhuanJb5y yJpsUTvQOYJDt9odoE56mJqYLqSp/FnR3yzE8F3IejWg2v9LUI5QlYj7luGDKdciTGiZ 0LXQ== MIME-Version: 1.0 X-Received: by 10.194.20.74 with SMTP id l10mr1722046wje.21.1359309573107; Sun, 27 Jan 2013 09:59:33 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Sun, 27 Jan 2013 09:59:32 -0800 (PST) In-Reply-To: <1255037243.20130127214457@serebryakov.spb.ru> References: <1359223263.8698.17.camel@eva02> <1102411019.20130127140605@serebryakov.spb.ru> <1255037243.20130127214457@serebryakov.spb.ru> Date: Sun, 27 Jan 2013 09:59:32 -0800 X-Google-Sender-Auth: dtB7uCxvlY8hwGemqL7R4g6ipHs Message-ID: Subject: Re: stuck beacon hung wifi adapter AR5008 From: Adrian Chadd To: lev@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 Cc: paranormal , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 17:59:34 -0000 On 27 January 2013 09:44, Lev Serebryakov wrote: > AC> For 2GHz in noisy environments, use it in HT20 mode. > I'm using HT20, and it seems, card in my box overheats with 802.11n > clients (it hangs very hard under load with 802.11n client), so I > don't use 802.11n on notebook (I want to change box to new one, > atom-based, but every month here are more high-priority expenditures > than $200+ on MoBo, case, memory, etc). Hm, overheating is a problem. It's quite likely that your issues are due to this. adrian From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 18:04:29 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 7AB87BAB; Sun, 27 Jan 2013 18:04:29 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [IPv6:2a01:4f8:131:60a2::2]) by mx1.freebsd.org (Postfix) with ESMTP id 40DA7E7A; Sun, 27 Jan 2013 18:04:29 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2577:cf36:d0d4:4986]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id EBF2F4AC2D; Sun, 27 Jan 2013 22:04:27 +0400 (MSK) Date: Sun, 27 Jan 2013 22:04:21 +0400 From: Lev Serebryakov Organization: FreeBSD Project X-Priority: 3 (Normal) Message-ID: <11510589486.20130127220421@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: stuck beacon hung wifi adapter AR5008 In-Reply-To: References: <1359223263.8698.17.camel@eva02> <1102411019.20130127140605@serebryakov.spb.ru> <1255037243.20130127214457@serebryakov.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=windows-1251 Content-Transfer-Encoding: quoted-printable Cc: paranormal , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: lev@FreeBSD.org List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 18:04:29 -0000 Hello, Adrian. You wrote 27 =FF=ED=E2=E0=F0=FF 2013 =E3., 21:59:32: >> AC> For 2GHz in noisy environments, use it in HT20 mode. >> I'm using HT20, and it seems, card in my box overheats with 802.11n >> clients (it hangs very hard under load with 802.11n client), so I >> don't use 802.11n on notebook (I want to change box to new one, >> atom-based, but every month here are more high-priority expenditures >> than $200+ on MoBo, case, memory, etc). AC> Hm, overheating is a problem. It's quite likely that your issues are AC> due to this. It is why I don't poke you about this problem till I exclude overheating for sure. --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Sun Jan 27 21:56:59 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 3B163559; Sun, 27 Jan 2013 21:56:59 +0000 (UTC) (envelope-from vince@unsane.co.uk) Received: from unsane.co.uk (unsane-pt.tunnel.tserv5.lon1.ipv6.he.net [IPv6:2001:470:1f08:110::2]) by mx1.freebsd.org (Postfix) with ESMTP id C48748B9; Sun, 27 Jan 2013 21:56:58 +0000 (UTC) Received: from vincemacbook.unsane.co.uk (vincemacbook.unsane.co.uk [10.10.10.20]) (authenticated bits=0) by unsane.co.uk (8.14.6/8.14.6) with ESMTP id r0RLuueB025924 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Sun, 27 Jan 2013 21:56:57 GMT (envelope-from vince@unsane.co.uk) Message-ID: <5105A2A9.2020803@unsane.co.uk> Date: Sun, 27 Jan 2013 21:56:57 +0000 From: Vincent Hoffman User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:17.0) Gecko/20130107 Thunderbird/17.0.2 MIME-Version: 1.0 To: Adrian Chadd Subject: Re: wireless link flaps (ath ar9280) References: <51051E26.1050300@unsane.co.uk> In-Reply-To: X-Enigmail-Version: 1.5 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Jan 2013 21:56:59 -0000 On 27/01/2013 17:11, Adrian Chadd wrote: > Hm, see if it's a beacon miss thing: > > > sysctl dev.ath.0.debug=0x80 now with added debugging. Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1 Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt 33171100 intval 100 (100) Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf 33967936054 tsf:tu 33171814 intval 100 nexttbtt 33171900 dtim 100 nextdtim 33171900 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next 33171900 timoffset 0 Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33967937503 lastrx 727896 (33967209607) bmiss 716800 Jan 27 21:49:09 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED bssid=e0:91:f5:48:5b:b9 reason=0 Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1 Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt 33171100 intval 100 (100) Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf 33968652767 tsf:tu 33172514 intval 100 nexttbtt 33172600 dtim 100 nextdtim 33172600 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next 33172600 timoffset 0 Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33968654221 lastrx 1444614 (33967209607) bmiss 716800 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: norm: node 0xffffff800b388000: bf=0xffffff80008c3140: addbaw=0, dobaw=1, seqno=2485, retry=0 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b388000: bf=0xffffff80008c3140: txq[1] axq_depth=0, axq_aggr_depth=0 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b388000: bf=0xffffff80008c3140: tid txq_depth=4 hwq_depth=0, bar_wait=1, isfiltered=0 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node 0xffffff800b388000: tid 0: sched=0, paused=1, incomp=0, baw_head=98, baw_tail=98 txa_start=2485, ni_txseqs=2489 Jan 27 21:49:09 ostracod kernel: TODS 00:24:23:07:fb:5d->60:33:4b:0d:e1:f8(e0:91:f5:48:5b:b9) data QoS [TID 0] WEP [IV 05 34 00 09 00 00 KID 0] 0M Jan 27 21:49:09 ostracod kernel: 8841 0000 e091 f548 5bb9 0024 2307 fb5d 6033 4b0d e1f8 509b 0000 dec0 0534 0020 0900 0000 aaaa 0300 0000 0800 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 2485 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 2486 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 2487 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't added: seqno 2488 Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008c3140: seqno 2485: dobaw should've been cleared! Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008c1e20: seqno 2486: dobaw should've been cleared! Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008a6178: seqno 2487: dobaw should've been cleared! Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf 0xffffff80008b7b90: seqno 2488: dobaw should've been cleared! Jan 27 21:49:09 ostracod kernel: wlan0: link state changed to DOWN Jan 27 21:49:12 ostracod wpa_supplicant[568]: Trying to associate with e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) Jan 27 21:49:12 ostracod wpa_supplicant[568]: Associated with e0:91:f5:48:5b:b9 Jan 27 21:49:12 ostracod kernel: wlan0: link state changed to UP Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: nexttbtt 7300 intval 100 (100) Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: tsf 33971573916 tsf:tu 33175367 intval 100 nexttbtt 33175400 dtim 100 nextdtim 33175400 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next 33175400 timoffset 0 Jan 27 21:49:13 ostracod wpa_supplicant[568]: WPA: Key negotiation completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] Jan 27 21:49:13 ostracod wpa_supplicant[568]: CTRL-EVENT-CONNECTED - Connection to e0:91:f5:48:5b:b9 completed (reauth) [id=0 id_str=] Thanks as ever for all the work Adrian, Vince > > > adrian > > On 27 January 2013 04:31, Vincent Hoffman wrote: >> Hi all, >> I'm running a recent -current (r245741) and seem to be getting >> interface flaps. Since this machine is mainly used for home mail and a >> little light file serving I'm not sure when they started occuring as i >> only have logging going back to the 18th Jan. >> >> Sample log messages are: >> Jan 24 16:26:22 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 24 16:26:22 ostracod kernel: AR_CR=0x00000024 >> Jan 24 16:26:22 ostracod kernel: AR_DIAG_SW=0x42000020 >> Jan 24 16:26:23 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED >> bssid=e0:91:f5:48:5b:b9 reason=0 >> Jan 24 16:26:23 ostracod kernel: wlan0: link state changed to DOWN >> Jan 24 16:26:26 ostracod wpa_supplicant[568]: Trying to associate with >> e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) >> Jan 24 16:26:26 ostracod wpa_supplicant[568]: Associated with >> e0:91:f5:48:5b:b9 >> Jan 24 16:26:26 ostracod kernel: wlan0: link state changed to UP >> Jan 24 16:26:27 ostracod wpa_supplicant[568]: WPA: Key negotiation >> completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] >> >> I sometime get just >> >> >> >> Jan 25 00:57:36 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 25 00:57:36 ostracod kernel: AR_CR=0x00000024 >> Jan 25 00:57:36 ostracod kernel: AR_DIAG_SW=0x42000020 >> >> or >> >> Jan 25 09:39:24 ostracod wpa_supplicant[568]: WPA: Group rekeying >> completed with e0:91:f5:48:5b:b9 [GTK=TKIP] >> Jan 25 09:41:13 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 25 09:41:13 ostracod kernel: AR_CR=0x00000024 >> Jan 25 09:41:13 ostracod kernel: AR_DIAG_SW=0x42000020 >> Jan 25 09:46:50 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 25 09:46:50 ostracod kernel: AR_CR=0x00000024 >> Jan 25 09:46:50 ostracod kernel: AR_DIAG_SW=0x42000020 >> Jan 25 09:49:24 ostracod wpa_supplicant[568]: WPA: Group rekeying >> completed with e0:91:f5:48:5b:b9 [GTK=TKIP] >> Jan 25 09:52:10 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 25 09:52:10 ostracod kernel: AR_CR=0x00000024 >> Jan 25 09:52:10 ostracod kernel: AR_DIAG_SW=0x42000020 >> Jan 25 09:57:07 ostracod kernel: ath0: bb hang detected (0x4), resetting >> >> or >> >> Jan 26 17:24:46 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 26 17:24:46 ostracod kernel: AR_CR=0x00000024 >> Jan 26 17:24:46 ostracod kernel: AR_DIAG_SW=0x42000020 >> Jan 26 17:25:31 ostracod kernel: ar5416PerCalibrationN: NF calibration >> didn't finish; delaying CCA >> >> with no interface flaps. >> And sometimes much more info >> >> Jan 25 16:56:27 ostracod kernel: ar5416StopDmaReceive: dma failed to >> stop in 10ms >> Jan 25 16:56:27 ostracod kernel: AR_CR=0x00000024 >> Jan 25 16:56:27 ostracod kernel: AR_DIAG_SW=0x42000020 >> Jan 25 16:56:28 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED >> bssid=e0:91:f5:48:5b:b9 reason=0 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: norm: >> node 0xffffff8014828000: bf=0xffffff80008b23e8: addbaw=1, dobaw=1, >> seqno=3447, retry=6 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node >> 0xffffff8014828000: bf=0xffffff80008b23e8: txq[1] axq_depth=0, >> axq_aggr_depth=0 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node >> 0xffffff8014828000: bf=0xffffff80008b23e8: tid txq_depth=10 hwq_depth=0, >> bar_wait=1, isfiltered=0 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node >> 0xffffff8014828000: tid 0: sched=0, paused=1, incomp=0, baw_head=114, >> baw_tail=116 txa_start=3446, ni_txseqs=3456 >> Jan 25 16:56:28 ostracod kernel: TODS >> 00:24:23:07:fb:5d->e0:91:f5:48:5b:b9(e0:91:f5:48:5b:b9) data QoS [TID 0] >> WEP [IV b6 89 00 0c 00 00 KID 0] 0M >> Jan 25 16:56:28 ostracod kernel: 8849 0000 e091 f548 5bb9 0024 2307 fb5d >> e091 f548 5bb9 70d7 0000 dec0 b689 0020 0c00 0000 aaaa 0300 0000 0800 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3448 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3449 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3450 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3451 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3452 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3453 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3454 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >> added: seqno 3455 >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008a9e08: seqno 3448: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008aa468: seqno 3449: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008c8a80: seqno 3450: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008cf080: seqno 3451: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008a8488: seqno 3452: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008a64a8: seqno 3453: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008aa930: seqno 3454: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >> 0xffffff80008a8ae8: seqno 3455: dobaw should've been cleared! >> Jan 25 16:56:28 ostracod kernel: wlan0: link state changed to DOWN >> Jan 25 16:56:39 ostracod wpa_supplicant[568]: Trying to associate with >> e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) >> Jan 25 16:56:39 ostracod wpa_supplicant[568]: Associated with >> e0:91:f5:48:5b:b9 >> Jan 25 16:56:39 ostracod kernel: wlan0: link state changed to UP >> Jan 25 16:56:40 ostracod wpa_supplicant[568]: WPA: Key negotiation >> completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] >> >> >> Device is >> ath0: mem 0xfebf0000-0xfebfffff irq 16 at device 0.0 on pci4 >> ath0: [HT] enabling HT modes >> ath0: [HT] 2 RX streams; 1 TX streams >> ath0: AR9280 mac 128.2 RF5133 phy 13.0 >> ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >> >> Any suggestions? I'm happy to provide more info if needed. >> >> Vince >> _______________________________________________ >> freebsd-wireless@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 28 01:45:57 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id CFB112B4 for ; Mon, 28 Jan 2013 01:45:57 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22a.google.com (we-in-x022a.1e100.net [IPv6:2a00:1450:400c:c03::22a]) by mx1.freebsd.org (Postfix) with ESMTP id 5F3A7DE for ; Mon, 28 Jan 2013 01:45:57 +0000 (UTC) Received: by mail-we0-f170.google.com with SMTP id z53so1181656wey.15 for ; Sun, 27 Jan 2013 17:45:55 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=Zme5FLV39mjDng4EWbfA0kmtFnzc0rM5u59AIZdM/9I=; b=rSvku7G0IEBxPnmPTtx0arJeeQ1w5rK+cBKjk2UeeeJ1DcNnYUveLg/3NCUU0BraaA AQ9gyYuf+1U6nTQNK6MBNRH1YJ0HZ6KuYfSUMxtzSULOgkpfmpcIRfk9hEP8HyLwEg9P z8MPbsP8pxEScUCyhCmPUhQDTBwwtCjCfon6zL5eVGo2deWoVFAsF7L0YU3hRQwqzDrL fsUp3Zf3bUNoR8Xk86kqI+AdFadg/fTKKk/GhzsoCovsCjaInSgz3ZdxqNR9v7gsUcjd x6OA+IqJUaCR0hp13TAeIEbmR478rSJ2FKSYVxe4KSYaJJpt/s1NcZl/IHpjlajeWHpE 3Qtw== MIME-Version: 1.0 X-Received: by 10.180.8.130 with SMTP id r2mr7012554wia.28.1359337555745; Sun, 27 Jan 2013 17:45:55 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Sun, 27 Jan 2013 17:45:55 -0800 (PST) In-Reply-To: <5105A2A9.2020803@unsane.co.uk> References: <51051E26.1050300@unsane.co.uk> <5105A2A9.2020803@unsane.co.uk> Date: Sun, 27 Jan 2013 17:45:55 -0800 X-Google-Sender-Auth: Inehy-HTb3E94OL6LeemiC8lt9g Message-ID: Subject: Re: wireless link flaps (ath ar9280) From: Adrian Chadd To: Vincent Hoffman Content-Type: text/plain; charset=ISO-8859-1 Cc: "freebsd-wireless@freebsd.org" X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 01:45:57 -0000 Right, this looks like you're missing beacons. My latest -HEAD changes causes a non-loss hardware reset, in case it's gone deaf. But if you are going deaf and missing the occasional beacon, it shouldn't be disconnecting you. I wonder how that logic is working.. Adrian On 27 January 2013 13:56, Vincent Hoffman wrote: > On 27/01/2013 17:11, Adrian Chadd wrote: >> Hm, see if it's a beacon miss thing: >> >> >> sysctl dev.ath.0.debug=0x80 > now with added debugging. > > Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1 > Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt > 33171100 intval 100 (100) > Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf > 33967936054 tsf:tu 33171814 intval 100 nexttbtt 33171900 dtim 100 > nextdtim 33171900 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next > 33171900 timoffset 0 > Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33967937503 > lastrx 727896 (33967209607) bmiss 716800 > Jan 27 21:49:09 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED > bssid=e0:91:f5:48:5b:b9 reason=0 > Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_proc: pending 1 > Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: nexttbtt > 33171100 intval 100 (100) > Jan 27 21:49:09 ostracod kernel: ath0: ath_beacon_config: tsf > 33968652767 tsf:tu 33172514 intval 100 nexttbtt 33172600 dtim 100 > nextdtim 33172600 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next > 33172600 timoffset 0 > Jan 27 21:49:09 ostracod kernel: ath0: ath_bmiss_vap: tsf 33968654221 > lastrx 1444614 (33967209607) bmiss 716800 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: norm: > node 0xffffff800b388000: bf=0xffffff80008c3140: addbaw=0, dobaw=1, > seqno=2485, retry=0 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node > 0xffffff800b388000: bf=0xffffff80008c3140: txq[1] axq_depth=0, > axq_aggr_depth=0 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node > 0xffffff800b388000: bf=0xffffff80008c3140: tid txq_depth=4 hwq_depth=0, > bar_wait=1, isfiltered=0 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_print: node > 0xffffff800b388000: tid 0: sched=0, paused=1, incomp=0, baw_head=98, > baw_tail=98 txa_start=2485, ni_txseqs=2489 > Jan 27 21:49:09 ostracod kernel: TODS > 00:24:23:07:fb:5d->60:33:4b:0d:e1:f8(e0:91:f5:48:5b:b9) data QoS [TID 0] > WEP [IV 05 34 00 09 00 00 KID 0] 0M > Jan 27 21:49:09 ostracod kernel: 8841 0000 e091 f548 5bb9 0024 2307 fb5d > 6033 4b0d e1f8 509b 0000 dec0 0534 0020 0900 0000 aaaa 0300 0000 0800 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 2485 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 2486 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 2487 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't > added: seqno 2488 > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008c3140: seqno 2485: dobaw should've been cleared! > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008c1e20: seqno 2486: dobaw should've been cleared! > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008a6178: seqno 2487: dobaw should've been cleared! > Jan 27 21:49:09 ostracod kernel: ath0: ath_tx_default_comp: bf > 0xffffff80008b7b90: seqno 2488: dobaw should've been cleared! > Jan 27 21:49:09 ostracod kernel: wlan0: link state changed to DOWN > Jan 27 21:49:12 ostracod wpa_supplicant[568]: Trying to associate with > e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) > Jan 27 21:49:12 ostracod wpa_supplicant[568]: Associated with > e0:91:f5:48:5b:b9 > Jan 27 21:49:12 ostracod kernel: wlan0: link state changed to UP > Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: nexttbtt 7300 > intval 100 (100) > Jan 27 21:49:12 ostracod kernel: ath0: ath_beacon_config: tsf > 33971573916 tsf:tu 33175367 intval 100 nexttbtt 33175400 dtim 100 > nextdtim 33175400 bmiss 7 sleep 100 cfp:period 100 maxdur 0 next > 33175400 timoffset 0 > Jan 27 21:49:13 ostracod wpa_supplicant[568]: WPA: Key negotiation > completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] > Jan 27 21:49:13 ostracod wpa_supplicant[568]: CTRL-EVENT-CONNECTED - > Connection to e0:91:f5:48:5b:b9 completed (reauth) [id=0 id_str=] > > > Thanks as ever for all the work Adrian, > > Vince > > >> >> >> adrian >> >> On 27 January 2013 04:31, Vincent Hoffman wrote: >>> Hi all, >>> I'm running a recent -current (r245741) and seem to be getting >>> interface flaps. Since this machine is mainly used for home mail and a >>> little light file serving I'm not sure when they started occuring as i >>> only have logging going back to the 18th Jan. >>> >>> Sample log messages are: >>> Jan 24 16:26:22 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 24 16:26:22 ostracod kernel: AR_CR=0x00000024 >>> Jan 24 16:26:22 ostracod kernel: AR_DIAG_SW=0x42000020 >>> Jan 24 16:26:23 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED >>> bssid=e0:91:f5:48:5b:b9 reason=0 >>> Jan 24 16:26:23 ostracod kernel: wlan0: link state changed to DOWN >>> Jan 24 16:26:26 ostracod wpa_supplicant[568]: Trying to associate with >>> e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) >>> Jan 24 16:26:26 ostracod wpa_supplicant[568]: Associated with >>> e0:91:f5:48:5b:b9 >>> Jan 24 16:26:26 ostracod kernel: wlan0: link state changed to UP >>> Jan 24 16:26:27 ostracod wpa_supplicant[568]: WPA: Key negotiation >>> completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] >>> >>> I sometime get just >>> >>> >>> >>> Jan 25 00:57:36 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 25 00:57:36 ostracod kernel: AR_CR=0x00000024 >>> Jan 25 00:57:36 ostracod kernel: AR_DIAG_SW=0x42000020 >>> >>> or >>> >>> Jan 25 09:39:24 ostracod wpa_supplicant[568]: WPA: Group rekeying >>> completed with e0:91:f5:48:5b:b9 [GTK=TKIP] >>> Jan 25 09:41:13 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 25 09:41:13 ostracod kernel: AR_CR=0x00000024 >>> Jan 25 09:41:13 ostracod kernel: AR_DIAG_SW=0x42000020 >>> Jan 25 09:46:50 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 25 09:46:50 ostracod kernel: AR_CR=0x00000024 >>> Jan 25 09:46:50 ostracod kernel: AR_DIAG_SW=0x42000020 >>> Jan 25 09:49:24 ostracod wpa_supplicant[568]: WPA: Group rekeying >>> completed with e0:91:f5:48:5b:b9 [GTK=TKIP] >>> Jan 25 09:52:10 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 25 09:52:10 ostracod kernel: AR_CR=0x00000024 >>> Jan 25 09:52:10 ostracod kernel: AR_DIAG_SW=0x42000020 >>> Jan 25 09:57:07 ostracod kernel: ath0: bb hang detected (0x4), resetting >>> >>> or >>> >>> Jan 26 17:24:46 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 26 17:24:46 ostracod kernel: AR_CR=0x00000024 >>> Jan 26 17:24:46 ostracod kernel: AR_DIAG_SW=0x42000020 >>> Jan 26 17:25:31 ostracod kernel: ar5416PerCalibrationN: NF calibration >>> didn't finish; delaying CCA >>> >>> with no interface flaps. >>> And sometimes much more info >>> >>> Jan 25 16:56:27 ostracod kernel: ar5416StopDmaReceive: dma failed to >>> stop in 10ms >>> Jan 25 16:56:27 ostracod kernel: AR_CR=0x00000024 >>> Jan 25 16:56:27 ostracod kernel: AR_DIAG_SW=0x42000020 >>> Jan 25 16:56:28 ostracod wpa_supplicant[568]: CTRL-EVENT-DISCONNECTED >>> bssid=e0:91:f5:48:5b:b9 reason=0 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: norm: >>> node 0xffffff8014828000: bf=0xffffff80008b23e8: addbaw=1, dobaw=1, >>> seqno=3447, retry=6 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node >>> 0xffffff8014828000: bf=0xffffff80008b23e8: txq[1] axq_depth=0, >>> axq_aggr_depth=0 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node >>> 0xffffff8014828000: bf=0xffffff80008b23e8: tid txq_depth=10 hwq_depth=0, >>> bar_wait=1, isfiltered=0 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_print: node >>> 0xffffff8014828000: tid 0: sched=0, paused=1, incomp=0, baw_head=114, >>> baw_tail=116 txa_start=3446, ni_txseqs=3456 >>> Jan 25 16:56:28 ostracod kernel: TODS >>> 00:24:23:07:fb:5d->e0:91:f5:48:5b:b9(e0:91:f5:48:5b:b9) data QoS [TID 0] >>> WEP [IV b6 89 00 0c 00 00 KID 0] 0M >>> Jan 25 16:56:28 ostracod kernel: 8849 0000 e091 f548 5bb9 0024 2307 fb5d >>> e091 f548 5bb9 70d7 0000 dec0 b689 0020 0c00 0000 aaaa 0300 0000 0800 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3448 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3449 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3450 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3451 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3452 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3453 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3454 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_tid_drain_pkt: wasn't >>> added: seqno 3455 >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008a9e08: seqno 3448: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008aa468: seqno 3449: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008c8a80: seqno 3450: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008cf080: seqno 3451: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008a8488: seqno 3452: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008a64a8: seqno 3453: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008aa930: seqno 3454: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: ath0: ath_tx_default_comp: bf >>> 0xffffff80008a8ae8: seqno 3455: dobaw should've been cleared! >>> Jan 25 16:56:28 ostracod kernel: wlan0: link state changed to DOWN >>> Jan 25 16:56:39 ostracod wpa_supplicant[568]: Trying to associate with >>> e0:91:f5:48:5b:b9 (SSID='vhoff' freq=2462 MHz) >>> Jan 25 16:56:39 ostracod wpa_supplicant[568]: Associated with >>> e0:91:f5:48:5b:b9 >>> Jan 25 16:56:39 ostracod kernel: wlan0: link state changed to UP >>> Jan 25 16:56:40 ostracod wpa_supplicant[568]: WPA: Key negotiation >>> completed with e0:91:f5:48:5b:b9 [PTK=CCMP GTK=TKIP] >>> >>> >>> Device is >>> ath0: mem 0xfebf0000-0xfebfffff irq 16 at device 0.0 on pci4 >>> ath0: [HT] enabling HT modes >>> ath0: [HT] 2 RX streams; 1 TX streams >>> ath0: AR9280 mac 128.2 RF5133 phy 13.0 >>> ath0: 2GHz radio: 0x0000; 5GHz radio: 0x00c0 >>> >>> Any suggestions? I'm happy to provide more info if needed. >>> >>> Vince >>> _______________________________________________ >>> freebsd-wireless@freebsd.org mailing list >>> http://lists.freebsd.org/mailman/listinfo/freebsd-wireless >>> To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" > From owner-freebsd-wireless@FreeBSD.ORG Mon Jan 28 11:06:54 2013 Return-Path: Delivered-To: freebsd-wireless@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 2DC1698A for ; Mon, 28 Jan 2013 11:06:54 +0000 (UTC) (envelope-from owner-bugmaster@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 105D9CF2 for ; Mon, 28 Jan 2013 11:06:54 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0SB6rMj034758 for ; Mon, 28 Jan 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0SB6rOG034756 for freebsd-wireless@FreeBSD.org; Mon, 28 Jan 2013 11:06:53 GMT (envelope-from owner-bugmaster@FreeBSD.org) Date: Mon, 28 Jan 2013 11:06:53 GMT Message-Id: <201301281106.r0SB6rOG034756@freefall.freebsd.org> X-Authentication-Warning: freefall.freebsd.org: gnats set sender to owner-bugmaster@FreeBSD.org using -f From: FreeBSD bugmaster To: freebsd-wireless@FreeBSD.org Subject: Current problem reports assigned to freebsd-wireless@FreeBSD.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 Jan 2013 11:06:54 -0000 Note: to view an individual PR, use: http://www.freebsd.org/cgi/query-pr.cgi?pr=(number). The following is a listing of current problems submitted by FreeBSD users. These represent problem reports covering all versions including experimental development code and obsolete releases. S Tracker Resp. Description -------------------------------------------------------------------------------- o kern/175446 wireless [ath] high volumes of PHY errors lead to BB/MAC hangs o kern/175227 wireless [ath] beacon timers aren't necessarily reprogrammed af o kern/175183 wireless [iwn] iwn(4) becomes unresponsive during initial confi o kern/175053 wireless [iwn] iwn firmware error on 9-stable with Ultimate-N 6 o kern/174891 wireless [ieee80211] struct ieee80211_node is freed during acti o kern/174722 wireless [wlan] can't use channel 12 and 13 (14) with my wifi i o kern/174661 wireless [wlan] lost alias on wlan interface o kern/174283 wireless [net80211] panics in ieee80211_ff_age() and ieee80211_ o kern/174276 wireless [ath] if_ath memory modified after free o kern/174273 wireless [net80211] taking down a net80211 node with active fas o kern/173917 wireless [iwn] wpa-supplicant issues on iwn o kern/173883 wireless [ath] ath0: unable to attach - pci issue? o kern/173711 wireless [ath] powerd kills ath on the Asus EeePC 1005HA o kern/173342 wireless PS-Poll isn't working o kern/173336 wireless [ath] Atheros card improper device poweroff handling o o kern/172955 wireless [ath] 11n does not work in adhoc mode o kern/172706 wireless [wpi] wpi0 fails to load firmware when using country o kern/172672 wireless [ubt] Bluetooth device recognised but not working o kern/172661 wireless hostapd(8) securing wireless adapter in HostAP mode is o kern/172338 wireless [ath] [net80211] CCMP IV transmit counters are not cor o kern/171598 wireless [ath] TP-Link TL-WN951N W-LAN PCI Adapter 300 MBit stu o kern/171235 wireless [ath] ath loses connection, system freezes on netif re o kern/170904 wireless [ath] ath driver: configure related parameters when ra o kern/170889 wireless [ath] ath driver uses some uninitilized memory o kern/170620 wireless [ath] LOR and deadlock when multiple vaps are used o kern/170573 wireless [iwi] Intel 2200BG iwi NIC hangs with need multicast c o kern/170513 wireless [ath] ath logs: ath_tx_aggr_comp_aggr: AR5416 bug: o kern/170433 wireless [ath] TX hang after a stuck beacon message with active o kern/170397 wireless [ath] [patch] Uninitialized variables in ah_eeprom_928 o kern/170302 wireless [ath] 802.11n frames are not being transmitted with mu o kern/170281 wireless [ath] 802.11n locks up on aggregation setup (ampdutx) o kern/170098 wireless [ath] [net80211] VAPs (Virtual access points) with Ath o kern/170066 wireless [ral] ral(4) rt61pci Linksys freezes the machine as so o kern/169432 wireless [ath] BAR TX hang when aggregation session is reset du p kern/169362 wireless [ath] AR5416: radar pulse PHY errors sometimes include o kern/169336 wireless [ath] ANI isn't triggering in a busy/noisy environment o kern/169199 wireless [ath] Cannot set up static ip addresses for wireless w o kern/169084 wireless [ath] suspend/resume doesn't cause a rescan; the assoc o kern/168530 wireless [ath] Broken WEP probably o kern/168393 wireless AR9285: suspend/resume sometimes fails o kern/168170 wireless [net80211] ieee80211_send_bar() doesn't complete corre o kern/167870 wireless [ath] adhoc wifi client does not join an existing IBSS o kern/167834 wireless [ath] kickpcu; 'handled 0 packets' o kern/167828 wireless [iwn] iwn(4) doesn't recover automatically after firmw o kern/167798 wireless ifconfig(8): problem with "ifconfig list scan" command o kern/167491 wireless [ath] TID != hardware queue TID in ath_tx_aggr_comp_ag o kern/167113 wireless [ath] AR5210: "stuck" TX seems to be occuring, without o kern/167080 wireless [ath] channel switch on another VAP break channel setu o kern/166684 wireless [ath] [net80211] mgmtrate/mcastrate isn't updated base p kern/166642 wireless [ieee80211] [patch] in 802.11n mode for FreeBSD AP, ha o kern/166641 wireless [ieee80211] [patch] mbuf/cluster leak in AP mode in 80 p kern/166357 wireless [ath] 802.11n TX stall when the first frame in the BAW o kern/166286 wireless [net80211] [ath] initial switch to HT40 isn't causing p kern/166190 wireless [ath] TX hangs and frames stuck in TX queue o kern/166086 wireless [Patch][ath] Reflect state of rfkill switch in a sysct o kern/165969 wireless [ath] Slower performance in adhoc mode vs Client/AP mo o kern/165966 wireless [ath] ath0: device timeout on SMP machines due to race o kern/165895 wireless [ath] overly busy cabq can tie up all tx buffers o kern/165870 wireless [bwn] bwn driver does not attach on HP Pavilion dv9420 o kern/165866 wireless [ath] TX hangs, requiring a "scan" to properly reset t o kern/165849 wireless [ath] [hang] network ath driver freeze o kern/165595 wireless [ipw] ipw(4): Can't load firmare for ipw2200bg o kern/165543 wireless [ath] ath0 endless scanning of channels without connec o kern/165517 wireless [net80211] bgscan isn't triggered when invalid beacons o kern/165475 wireless [ath] operational mode change doesn't poke the underly o kern/165382 wireless [kernel] taskqueue_unblock doesn't unblock currently q o kern/165306 wireless [ath] race conditions between scanning and beacon time o kern/165220 wireless [ath] "ath_rx_tasklet: sc_inreset_cnt > 0; skipping" m o kern/165214 wireless [ieee80211] Kernel panic in ieee80211_output.c:2505 o kern/165212 wireless [ath] No WiFi on Acer Aspire One 751h (Atheros AR5BHB6 o kern/165149 wireless [ath] [net80211] Ping with data length more than iv_fr o kern/165146 wireless [net80211] Net802.11 Fragment number is assigned 1 (sh o kern/165060 wireless [ath] vap->iv_bss race conditions causing crashes insi o kern/165021 wireless [ath] ath device timeout during scan/attach, if wlan_c o kern/164721 wireless [ath] ath device timeouts o kern/164499 wireless [wi] [patch] if_wi needs fix for big endian architectu o kern/164382 wireless [ath] crash when down/deleting a vap - inside ieee8021 o kern/164365 wireless [iwi] iwi0: UP/DOWN in o bin/164102 wireless hostapd not configured for 802.11n o kern/163759 wireless [ath] ath(4) "stops working" in hostap mode o kern/163724 wireless [mwl] [patch] NULL check before dereference o kern/163719 wireless [ath] ath interface do not receive multicast o kern/163689 wireless [ath] TX timeouts when sending probe/mgmt frames durin o kern/163574 wireless [net80211] overly-frequent HT occupancy changes o kern/163573 wireless [ath] hostap mode TX buffer hang o kern/163559 wireless [ath] kernel panic AH_DEBUG o kern/163318 wireless [ath] ath(4) stops working p kern/163312 wireless [panic] [ath driver] kernel panic: page fault with ath o kern/163237 wireless [ath] AR5416 as HostAP. Delays among clients when a cl o kern/163082 wireless [ath] ar9285 diversity fixes o kern/162648 wireless [ath] AR9227 ADC DC calibration failure o kern/162647 wireless [ath] 11n TX aggregation session / TX hang o kern/161293 wireless [iwn] hang at startup when starting network o kern/161035 wireless [ieee80211] Incorrect number describing 11ng MCS rate o kern/160391 wireless [ieee80211] [patch] Panic in mesh mode o kern/160296 wireless [zyd] [panic] 802.11 usb device reboots system on 'ifc o misc/160176 wireless [mips] [panic] Kernel panic on AR7161 platform with AR o kern/157449 wireless [ath] MAC address conflict causes system to freeze o kern/157243 wireless [ath] investigate beacon TX (AP) / RX (STA) when under o kern/156904 wireless [ath] AR9285 antenna diversity algorithm is buggy and o kern/156884 wireless [ath] ath instablity o kern/156327 wireless [bwn] bwn driver causes 20%-50% packet loss o kern/156322 wireless [wpi] no ahdemo support for if_wpi o kern/156321 wireless [ath] ahdemo doesn't work with if_ath o kern/155498 wireless [ral] ral(4) needs to be resynced with OpenBSD's to ga o kern/155100 wireless [ath] ath driver on busy channel: "stuck beacon" p kern/154598 wireless [ath] Atheros 5424/2424 can't connect to WPA network o kern/154567 wireless [ath] ath(4) lot of bad series(0) o kern/154327 wireless [ath] AR5416 in station mode hangs when transmitting f o kern/154284 wireless [ath] Modern ath wifi cards (such as AR9285) have miss o kern/154153 wireless [ath] AR5213 + MIPS + WPA group key packet corruption o kern/153594 wireless [wlan] netif/devd race o kern/153448 wireless [ath] ath networking device loses association after a o kern/152750 wireless [ath] ath0 lot of bad series hwrate o kern/151198 wireless [ath] ath/5416 fails bgscan with "ath0: ath_chan_set: o kern/149786 wireless [bwn] bwn on Dell Inspiron 1150: connections stall o kern/149516 wireless [ath] ath(4) hostap with fake MAC/BSSID results in sta o kern/149373 wireless [realtek/atheros]: None of my network card working o kern/148322 wireless [ath] Triggering atheros wifi beacon misses in hostap o kern/148317 wireless [ath] FreeBSD 7.x hostap memory leak in net80211 or At o kern/148078 wireless [ath] wireless networking stops functioning o kern/146426 wireless [mwl] 802.11n rates not possible on mwl o kern/146425 wireless [mwl] mwl dropping all packets during and after high u o kern/145826 wireless [panic] [ath] Unable to configure adhoc mode on ath0/w o kern/144987 wireless [wpi] [panic] injecting packets with wlaninject using o kern/144755 wireless [wlan] netif/devd race o bin/144109 wireless hostapd(8) uses the MAC of the wireless interface, but o conf/143079 wireless hostapd(8) startup missing multi wlan functionality p kern/140567 wireless [ath] [patch] ath is not worked on my notebook PC o kern/140245 wireless [ath] [panic] Kernel panic during network activity on o kern/137592 wireless [ath] panic - 7-STABLE (Aug 7, 2009 UTC) crashes on ne p bin/137484 wireless [patch] Integer overflow in wpa_supplicant(8) base64 e o kern/136943 wireless [wpi] [lor] wpi0_com_lock / wpi0 o kern/136836 wireless [ath] atheros card stops functioning after about 12 ho o kern/132722 wireless [ath] Wifi ath0 associates fine with AP, but DHCP or I o bin/131549 wireless ifconfig(8) can't clear 'monitor' mode on the wireless o kern/126475 wireless [ath] [panic] ath pcmcia card inevitably panics under o kern/125721 wireless [ath] Terrible throughput/high ping latency with Ubiqu o kern/125617 wireless [ath] [panic] ath(4) related panic o kern/125501 wireless [ath] atheros cardbus driver hangs o kern/125332 wireless [ath] [panic] crash under any non-tiny networking unde o kern/124767 wireless [iwi] Wireless connection using iwi0 driver (Intel 220 o kern/124753 wireless [ieee80211] net80211 discards power-save queue packets o kern/121061 wireless [ath] [panic] panic while ejecting ath(4)-adapter duri o docs/120456 wireless ath(4) needs to specify requirement on wlan_scan_sta o kern/119513 wireless [ath] [irq] inserting dlink dwl-g630 wireless card res o kern/116747 wireless [ndis] FreeBSD 7.0-CURRENT crash with Dell TrueMobile f kern/105348 wireless [ath] ath device stopps TX 148 problems total. From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 30 16:29:24 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 40D68CA9 for ; Wed, 30 Jan 2013 16:29:23 +0000 (UTC) (envelope-from paranormal@isgroup.com.ua) Received: from isgroup.com.ua (mail.isgroup.com.ua [46.229.54.104]) by mx1.freebsd.org (Postfix) with ESMTP id 278B76EF for ; Wed, 30 Jan 2013 16:29:22 +0000 (UTC) Received: from [192.168.11.5] (unused-213.111.70.194.bilink.ua [213.111.70.194] (may be forged)) (authenticated bits=0) by isgroup.com.ua (8.14.5/8.14.5) with ESMTP id r0UEvA6I091449 (version=TLSv1/SSLv3 cipher=DHE-RSA-CAMELLIA256-SHA bits=256 verify=NO); Wed, 30 Jan 2013 16:57:10 +0200 (EET) (envelope-from paranormal@isgroup.com.ua) Subject: Re: stuck beacon hung wifi adapter AR5008 From: paranormal To: freebsd-wireless@freebsd.org In-Reply-To: References: <1359223263.8698.17.camel@eva02> <51042871.2090605@martenvijn.nl> <1359240382.8698.60.camel@eva02> Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature"; boundary="=-u0h3n38s7lo9ToDfDTbQ" Date: Wed, 30 Jan 2013 18:29:01 +0200 Message-ID: <1359563341.29231.21.camel@eva02> Mime-Version: 1.0 X-Mailer: Evolution 2.32.1 FreeBSD GNOME Team Port X-Spam-Status: No, score=-101.0 required=5.0 tests=ALL_TRUSTED, USER_IN_WHITELIST autolearn=ham version=3.3.2 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on isgroup.com.ua X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 16:29:24 -0000 --=-u0h3n38s7lo9ToDfDTbQ Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Thank you Adrian, your advice was perfect. I have a gym friend whose job is blacksmith (the friend has right hands, and I don't), I gave him my 3 antennas, and hi made them fitted with my wireless card. My card is able to reset it now. Instead of hung I have: wlan0: link state changed to DOWN wlan0: link state changed to UP So, thank you very much :) On Sat, 2013-01-26 at 18:26 -0800, Adrian Chadd wrote: > Hi, >=20 > So the AR5416 and later NICs almost all implement MIMO. The only > exception is the AR9285 which is a 1x1 with the diversity > implementation matching previous (pre-11n) NICs. >=20 > Anyway, for MIMO, all the antennas are on by default. So yes, you need > to connect all of the antennas. >=20 > If you want to avoid this, you can override things. I _think_ it's: >=20 > hint.dev.ath.0.rx_antenna=3D0x5 > hint.dev.ath.0.tx_antenna=3D0x5 >=20 > in /boot/loader.conf >=20 > If it's not that, it's hint.ath.0.xxx .. >=20 > Then connect antennas to the connectors marked "chain 0" and "chain 2". >=20 > The boot messages should then say that the RX and TX chainmasks are being= set. >=20 > Otherwise - yes, connect all three! >=20 >=20 >=20 > Adrian > _______________________________________________ > freebsd-wireless@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-wireless > To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.or= g" --=-u0h3n38s7lo9ToDfDTbQ Content-Type: application/pgp-signature; name="signature.asc" Content-Description: This is a digitally signed message part -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (FreeBSD) iQIcBAABAgAGBQJRCUpMAAoJEOKdyUSm7MVLH94P/iaRD1mM5Su8UKd8EDwmpEFm bSX9InQL5P+7ZHXIq05II1gXKNzJDfwljZBDYeqExD3wDUkwIdKG3QT/akJVr+jA rc/LUvRqsNe7z3F7u6amfYA9/CcFX89UjO+qackS9fFsSAIJtzdoLBtvYVb4hR1x ChorjlBoX/qRBhFm2hZUAgI15XXEJ4RUH6ZZt/ZpeTXjR4AkhJyQ+6C3RmYMQO4G +GI5g0fw84Ex5qE07a/V1AspTHWO5VcNht7TZb2lZC2ZjuYLUn60nmiF4tLwMlyb uSrkuwtqEfz+NU0cCAuq+lToVOaVIv/6dv4BBH3XvpCgDczDdaBaKz0nSmvCZNSv rpNa+HXtkhDrokIOiSNcfYXOojVxwJWny9AtGVjpZNiMhCwGRMWsUR4/+dzpC973 Kiuxs9+R7aeawuJGcBqWeKpX8pnzGY5GmohOhQVagGDpPkAcluo5rwiTmRFblU4w xflB4C/V0GglEuIhjpr/TQDSOpX7ZT9S9+vEKpjUOo96NzPirdZ1r3gH2WwJvuKw gZYUiej2D4LQc0WRNHGUOBl1V9RGgFErVuWOQ5FWhsqJs2uynWrlTKYWxiRnmdHd fptyV9XhS6nLxI8Ju07fOhekgKxkBvL43JMzdo5GpHliBbPZmD4NCNAsL4v9TFFF DGi7+ZjMCTVf3oY0TJmq =3juK -----END PGP SIGNATURE----- --=-u0h3n38s7lo9ToDfDTbQ-- From owner-freebsd-wireless@FreeBSD.ORG Wed Jan 30 17:06:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2142EF10 for ; Wed, 30 Jan 2013 17:06:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22c.google.com (mail-we0-x22c.google.com [IPv6:2a00:1450:400c:c03::22c]) by mx1.freebsd.org (Postfix) with ESMTP id B2B34927 for ; Wed, 30 Jan 2013 17:06:04 +0000 (UTC) Received: by mail-we0-f172.google.com with SMTP id x10so1376811wey.31 for ; Wed, 30 Jan 2013 09:06:03 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=0g2MXAjiScLobnteyT7eWOBOna9ICQDk5pF2R2PcOV4=; b=DHZLfddSsFL41LQ1F/yPgAtYVeq9Uu9KBOCPbPL/puAfq2rGjKKebE/GA/iZthZQsv dEGNFvkkxiDYFLaUh0Lzew+efVcLcZikDNC/8oIyhkPfjgy84YiBS1BclZWt1dPzPNpL Y/CNdSPBixdWIClI3ApMvDZk65UUUd1aJdwPAQ/5Ye+7ZnJyT+Q+57+e+ITj3Ki4XcEH /Qe1nxUutv69reIv6+XKhOHZY36ULtVZgFiyVrBV3W1nJ25XhPdts/aV2nUyVIywLRcX AkPoR38rGRO2XaQ3A0buoAidBbwvT0iy596kbZ/9ayiH1rr02BmdI8zHKr0g/CFw82uT qovw== MIME-Version: 1.0 X-Received: by 10.194.172.197 with SMTP id be5mr10408122wjc.20.1359565563315; Wed, 30 Jan 2013 09:06:03 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Wed, 30 Jan 2013 09:06:03 -0800 (PST) In-Reply-To: <1359563341.29231.21.camel@eva02> References: <1359223263.8698.17.camel@eva02> <51042871.2090605@martenvijn.nl> <1359240382.8698.60.camel@eva02> <1359563341.29231.21.camel@eva02> Date: Wed, 30 Jan 2013 09:06:03 -0800 X-Google-Sender-Auth: ZxtqfzJglFMx5yGwrDhOnjlTqgE Message-ID: Subject: Re: stuck beacon hung wifi adapter AR5008 From: Adrian Chadd To: paranormal Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jan 2013 17:06:05 -0000 On 30 January 2013 08:29, paranormal wrote: > Thank you Adrian, your advice was perfect. > > I have a gym friend whose job is blacksmith (the friend has right hands, > and I don't), I gave him my 3 antennas, and hi made them fitted with my > wireless card. ooo! > My card is able to reset it now. Instead of hung I have: > wlan0: link state changed to DOWN > wlan0: link state changed to UP > > So, thank you very much :) Good news! adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 31 00:19:35 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 36C52492 for ; Thu, 31 Jan 2013 00:19:35 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f171.google.com (mail-wi0-f171.google.com [209.85.212.171]) by mx1.freebsd.org (Postfix) with ESMTP id CF107EA9 for ; Thu, 31 Jan 2013 00:19:34 +0000 (UTC) Received: by mail-wi0-f171.google.com with SMTP id hn14so4256013wib.10 for ; Wed, 30 Jan 2013 16:19:28 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:date:x-google-sender-auth:message-id :subject:from:to:content-type; bh=AjdgdDgLSTlrdVlbG+ncEF8iseeM/5TvMgDzsmBZfpk=; b=ZEk0imgCe1+TeoJxGR8cCcTVwcE+vt1FK3sc462zaFlL7Mgwg/lXi0NVY+yH2ltnEv SLCu4EwZGMc0YnZXnC4BIvKFaq5A7NSoujse1RRi23VFZ79dQET28BJ0c98n2bKqHdPl uFAjEn0C0mlzSv6T1lA6dMLicGrRQZ2QhntWIIHzrHN72+bjZZNmORdYPTkZDUrURkHu 5KfKaPUpa9WQf/bHk7KncXfLXRT7PKAMRqCtKUl8nrOFBZmBZdQ2NH64VdXm7Au6i5vo Ibmh3SejjSOcMaN9ytF49zE9t/ZNo++w3BO+PTxf8r81KRJhKH/tx7pSmpFOcfqNxbH8 iUbg== MIME-Version: 1.0 X-Received: by 10.194.172.197 with SMTP id be5mr12116541wjc.20.1359591568594; Wed, 30 Jan 2013 16:19:28 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Wed, 30 Jan 2013 16:19:28 -0800 (PST) Date: Wed, 30 Jan 2013 16:19:28 -0800 X-Google-Sender-Auth: yfSPjTCrxQNn__QJzyfcYO9kp7M Message-ID: Subject: howto: tinkering with spectral scan From: Adrian Chadd To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 00:19:35 -0000 Hi, Here's the 30 second rundown for spectral scan: * update to -HEAD; * "make" and "make install" in src/tools/tools/ath/; (so you get athspectral) * checkout svn://svn.freebsd.org/base/user/adrian/ath_radar_stuff; * install SDL and the SDL TTF font ports; * "make" in ath_radar_stuff/lib; * "make" in ath_radar_stuff/src/fft_eval. Now to use tinker with spectral scan parameters: * athspectral get - lists parameters * athspectral start - start a spectral scan * athspectral enable_at_reset 1|0 - enable or disable spectral scan at reset (eg during a channel change for a scan operation); To enable receiving spectral scan PHY errors: * sysctl dev.ath.X.monpass=0xff - by default PHY errors aren't passed up via BPF, this (overkill!) enables that; * ./fft_eval ar9280 if wlanX + cursor left/right scrolls; + home jumps to 2ghz; + end jumps to 5ghz; On AR9280, if you set ss_count=128, it will just keep generating results; On AR9285 and AR9287, I think ss_count=0 will keep generating results; Don't clear ss_short_rpt - it will generate corrupted FFT frames and there's no way to correct for them (which I'm not yet correcting for right now - but at least with one FFT report per PHY error I'm able to); For extra fun: * athspectral enable_at_reset 1 * ifconfig wlan0 create wlandev ath0 ssid 'foo123' up * sysctl dev.ath.0.monpass=0xff * fft_eval ar9280 if wlan0 .. and scroll around. :-) I'd love to see screenshots of various kinds of interference seen by everyone here. :) Adrian From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 31 09:11:44 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 75E0DB44; Thu, 31 Jan 2013 09:11:44 +0000 (UTC) (envelope-from lev@FreeBSD.org) Received: from onlyone.friendlyhosting.spb.ru (onlyone.friendlyhosting.spb.ru [46.4.40.135]) by mx1.freebsd.org (Postfix) with ESMTP id 3E50F69B; Thu, 31 Jan 2013 09:11:44 +0000 (UTC) Received: from lion.home.serebryakov.spb.ru (unknown [IPv6:2001:470:923f:1:2577:cf36:d0d4:4986]) (Authenticated sender: lev@serebryakov.spb.ru) by onlyone.friendlyhosting.spb.ru (Postfix) with ESMTPA id 3C0BC4AC32; Thu, 31 Jan 2013 13:11:43 +0400 (MSK) Date: Thu, 31 Jan 2013 13:11:34 +0400 From: Lev Serebryakov X-Priority: 3 (Normal) Message-ID: <1548313397.20130131131134@serebryakov.spb.ru> To: Adrian Chadd Subject: Re: howto: tinkering with spectral scan In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 09:11:44 -0000 Hello, Adrian. You wrote 31 =D1=8F=D0=BD=D0=B2=D0=B0=D1=80=D1=8F 2013 =D0=B3., 4:19:28: AC> .. and scroll around. :-) I know, what I'll do with my old router after upgrade now! :) --=20 // Black Lion AKA Lev Serebryakov From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 31 13:58:16 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 72AB55A7; Thu, 31 Jan 2013 13:58:16 +0000 (UTC) (envelope-from eadler@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 4ED5E8D7; Thu, 31 Jan 2013 13:58:16 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0VDwGEs034671; Thu, 31 Jan 2013 13:58:16 GMT (envelope-from eadler@freefall.freebsd.org) Received: (from eadler@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0VDwGNJ034667; Thu, 31 Jan 2013 13:58:16 GMT (envelope-from eadler) Date: Thu, 31 Jan 2013 13:58:16 GMT Message-Id: <201301311358.r0VDwGNJ034667@freefall.freebsd.org> To: eadler@FreeBSD.org, eadler@FreeBSD.org, freebsd-wireless@FreeBSD.org From: eadler@FreeBSD.org Subject: Re: kern/173898: [iwn] [patch] iwn(4) DOES support 6235 chip. X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 13:58:16 -0000 Synopsis: [iwn] [patch] iwn(4) DOES support 6235 chip. Responsible-Changed-From-To: eadler->freebsd-wireless Responsible-Changed-By: eadler Responsible-Changed-When: Thu Jan 31 13:58:15 UTC 2013 Responsible-Changed-Why: sorry I held on to this for so long; at the moment I have no time to look at this PR so return to the pool http://www.freebsd.org/cgi/query-pr.cgi?pr=173898 From owner-freebsd-wireless@FreeBSD.ORG Thu Jan 31 17:24:32 2013 Return-Path: Delivered-To: freebsd-wireless@smarthost.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id C612B62A; Thu, 31 Jan 2013 17:24:32 +0000 (UTC) (envelope-from linimon@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2001:1900:2254:206c::16:87]) by mx1.freebsd.org (Postfix) with ESMTP id 998DF6C5; Thu, 31 Jan 2013 17:24:32 +0000 (UTC) Received: from freefall.freebsd.org (localhost [127.0.0.1]) by freefall.freebsd.org (8.14.6/8.14.6) with ESMTP id r0VHOWB0073996; Thu, 31 Jan 2013 17:24:32 GMT (envelope-from linimon@freefall.freebsd.org) Received: (from linimon@localhost) by freefall.freebsd.org (8.14.6/8.14.6/Submit) id r0VHOW4S073992; Thu, 31 Jan 2013 17:24:32 GMT (envelope-from linimon) Date: Thu, 31 Jan 2013 17:24:32 GMT Message-Id: <201301311724.r0VHOW4S073992@freefall.freebsd.org> To: linimon@FreeBSD.org, freebsd-bugs@FreeBSD.org, freebsd-wireless@FreeBSD.org From: linimon@FreeBSD.org Subject: Re: kern/175722: [ath]lot of bad seriesx hwrate in kernel messages X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 31 Jan 2013 17:24:32 -0000 Old Synopsis: ath(4) lot of bad seriesx hwrate in kernel messages New Synopsis: [ath]lot of bad seriesx hwrate in kernel messages Responsible-Changed-From-To: freebsd-bugs->freebsd-wireless Responsible-Changed-By: linimon Responsible-Changed-When: Thu Jan 31 17:24:11 UTC 2013 Responsible-Changed-Why: Over to maintainer(s). http://www.freebsd.org/cgi/query-pr.cgi?pr=175722 From owner-freebsd-wireless@FreeBSD.ORG Fri Feb 1 01:01:46 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id AB7AA48D; Fri, 1 Feb 2013 01:01:46 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f174.google.com (mail-wi0-f174.google.com [209.85.212.174]) by mx1.freebsd.org (Postfix) with ESMTP id 0E4F5F24; Fri, 1 Feb 2013 01:01:45 +0000 (UTC) Received: by mail-wi0-f174.google.com with SMTP id hj13so65115wib.1 for ; Thu, 31 Jan 2013 17:01:45 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=frp79jqIAZdm39ZDtxvghQ3kV9rVzXC4SaBjoF6JIUg=; b=GsiTsSba+aZwFRLqd3GUte2JPPMdDTe+PThG0dwaE26Hu77w1iax+V1Tuit97CoiV0 TTew5PHmnRmkVoI2jRB+dTpo1RFBqgE19YTimsQXKLoz7qBACDjDlETP4kpEm/AYxJWK hFUY8pVzSx61t+5XQCpRyz4jyG/Kwm1nQBApmo9+BDT15+uFlS2YnNgdCQRJp0Pew8nE pKK95Hk4qTjHQvmnKfuzomtOGzN6PfDIfmCkdQaNTX5fOgtYhFyLVCk9BHv+PRv4Nqyf qyBVYGtHxs28rGYLnaANjFh/CHlbGu47/6EHVwsPfhfjripSyBmNJ7/BvaMV1fgyQCMm R95g== MIME-Version: 1.0 X-Received: by 10.180.8.130 with SMTP id r2mr18077546wia.28.1359680505214; Thu, 31 Jan 2013 17:01:45 -0800 (PST) Sender: adrian.chadd@gmail.com Received: by 10.216.67.6 with HTTP; Thu, 31 Jan 2013 17:01:45 -0800 (PST) In-Reply-To: References: Date: Thu, 31 Jan 2013 17:01:45 -0800 X-Google-Sender-Auth: 9QlApiN2WjfqbRKXfVSpAJFV99s Message-ID: Subject: Re: Block ACK in Ralink RT2860 From: Adrian Chadd To: Ramanujan Seshadri Content-Type: text/plain; charset=ISO-8859-1 Cc: FreeBSD Net , PseudoCylon , freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Feb 2013 01:01:46 -0000 Hi, So the 30 second version: * the maximum aggregation size in 802.11n is 65536 bytes, including the between-frame delimiters; * mpdu density defines how big those delimiters are - they're calculated either in bytes or as a function of the currently selected rate and duration, which ends up being a set of bytes anyway; * some hardware may require extra delimiter time between frames to "reset" internal frame processing between MPDUs. The atheros hardware, for examples, sets the default mpdu density to 8 microseconds to allow the encryption hardware to reset fully. It's only needed at the higher rates, but I've not sat down and totally mapped out what behaviour is there so I do it for all rates; * .. and later atheros hardware has a minimum per-MPDU timing and delimiters are added to that to "pad" out a frame to a minimum duration in microseconds. Again, to meet timing requirements in the chip; * bawinsize is negotiated during ADDBA negotiation. The maximum window size is 64 frames but devices may negotiate smaller window sizes if they like; * some hardware / drivers may limit the size of aggregates anyway - eg, the ath(4) aggregation code limits the per-AMPDU size to 32 frames even if the window is 64 frames. This is done to limit the effects of poor reception. Again, I could do a smarter job of it in ideal(er) situations but I've been focusing on other things. HTH, adrian On 31 January 2013 16:48, Ramanujan Seshadri wrote: > I am testing the driver code witht he ralink nic. Yes the frame > aggregation works, since i get higher throughput. I am actually tryign to > know how many frames (MPDU's) are aggregated each time in an AMPDU. > > Regarding the MPDU density - i was wondering how it should affect the Frame > aggregation. Since MPDU density is the time duration between each MPDU sent > within the AMPDU. So, how does this matter to the hardware for aggregating > the number of frames. It just sends MPDU's with the set interval. > > The other two limits make sense, the BAWinSize and the MAX_LEN_CFG. > > Ram > > On Wed, Jan 30, 2013 at 5:45 PM, PseudoCylon wrote: > >> On Wed, Jan 30, 2013 at 1:20 PM, Ramanujan Seshadri >> wrote: >> > Thank you. I also wanted to know the function where the Block ACK Window >> > will be decided. is it decided during the ADDBA session establishment or >> > does it change dynamically. >> >> The hardware will aggregate packets until any of following limits hit max >> http://fxr.watson.org/fxr/source/dev/ral/rt2860reg.h#L782 >> * rt2860_txwi.flags >> RT2860_TX_MPDU_DSITY_SHIFT >> 000 == no restriction >> 001 == 1/4 us >> 010 == 1/2 us >> ... >> 111 == 16 us >> * rt2860_txwi.xflags >> RT2860_TX_BAWINSIZE_SHIFT (frame count) >> >> http://fxr.watson.org/fxr/source/dev/ral/rt2860reg.h#L93 >> * RT2860_MAX_LEN_CFG bit 12:13 >> 00 == 8k bytes >> 01 == 16k >> 10 == 32k >> 11 == 64k >> >> At a quick look, none of them is set in current code. Also, >> RT2860_TX_AMPDU flag need to be set to make the h/w aggregate packets. >> >> How is ampdu working on ral(4)? I cannot test because I do not have >> any ral(4) nic (only have run(4) nics). >> >> >> AK >> >> > >> > >> > On Thu, Jan 24, 2013 at 5:13 PM, PseudoCylon >> > wrote: >> >> >> >> > Message: 6 >> >> > Date: Thu, 24 Jan 2013 12:23:55 -0500 >> >> > From: Ramanujan Seshadri >> >> > To: freebsd-net@freebsd.org >> >> > Subject: Block ACK in Ralink RT2860 >> >> > Message-ID: >> >> > >> >> > >> >> > Content-Type: text/plain; charset=ISO-8859-1 >> >> > >> >> > Hi all, >> >> > I am trying to read the contents of block ack's in a Ralink RT2860 >> >> > driver. >> >> > Can you please help me to know which function i should be looking >> into ? >> >> >> >> At default, all BA packets are dropped by h/w. Clear RT2860_DROP_BA flag >> >> at >> >> http://fxr.watson.org/fxr/source/dev/ral/rt2860.c#L3559 >> >> >> >> Then, the diver should receive BA packets, and you can read them. >> >> >> >> >> >> AK >> > >> > >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 2 08:46:26 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2A8BEB19 for ; Sat, 2 Feb 2013 08:46:26 +0000 (UTC) (envelope-from hoptoa@gmail.com) Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by mx1.freebsd.org (Postfix) with ESMTP id BBB6769E for ; Sat, 2 Feb 2013 08:46:25 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id jx10so3519632veb.39 for ; Sat, 02 Feb 2013 00:46:19 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:content-type; bh=YuChQ5Hdso4QIfmUR3UkK4qnOvi+6Ssi4LbsKyTft6c=; b=SRVLFGvKH3/88WOCTB5p5Q8GXXTF5/rOkuUd1Qwmb+H8RsDJAO4paFzl5Cc1miL0Yx FyIm3MqChozoo20zqN6hhYWlWnWzFlriKAwxe4pgEbprqkzR7s7tDicLxA/Iu2V1ExDd iKcRPpVlIYNH/gswwTUCaQVbZIkeK6zEuirR2Pjw0bSXfvbruBEQdCJgY6gKtuTuCr1Y oXYDdZvU86SWO78ak6hzyy5ApfuB44GX3bsf+KISme1GPLap9TnvUH7OyD+r12X9kgDS l7pUMMrKlEzXeCGL3UQIrHrxarzhTe3djLVB7Cuad5a0HhC8kvWITGiNLJ0lf0bS4Dqj Kxfw== MIME-Version: 1.0 X-Received: by 10.221.0.79 with SMTP id nl15mr13679264vcb.41.1359794779449; Sat, 02 Feb 2013 00:46:19 -0800 (PST) Received: by 10.220.201.133 with HTTP; Sat, 2 Feb 2013 00:46:19 -0800 (PST) In-Reply-To: References: Date: Sat, 2 Feb 2013 10:46:19 +0200 Message-ID: Subject: Fwd: From: =?KOI8-R?B?4dLUo80g7c/Sz9rP1w==?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=KOI8-R Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 08:46:26 -0000 ---------- Forwarded message ---------- From: =E1=D2=D4=A3=CD =ED=CF=D2=CF=DA=CF=D7 Date: 2013/1/20 Subject: To: freebsd-wireless@freebsd.org D-link DWA-525 I'm trying to find solution for a long time, i want to lead this wireless NIC to work. NIC works on chipset rt3060 which support on Free BSD from 2012.05, but in spite of that NIC doesn't work. I setting up it without any errors, but when I settings it in client mode card cannot find any works access point. And when I settings card in access point mode, I cannot find even this access point. LED indicator on the NIC show, that card is works and transmit data, but really, it doesn't work. From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 2 08:49:51 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.FreeBSD.org [8.8.178.115]) by hub.freebsd.org (Postfix) with ESMTP id 2B6E7BCB for ; Sat, 2 Feb 2013 08:49:51 +0000 (UTC) (envelope-from hoptoa@gmail.com) Received: from mail-ve0-f180.google.com (mail-ve0-f180.google.com [209.85.128.180]) by mx1.freebsd.org (Postfix) with ESMTP id E535E6B3 for ; Sat, 2 Feb 2013 08:49:50 +0000 (UTC) Received: by mail-ve0-f180.google.com with SMTP id jx10so3495122veb.25 for ; Sat, 02 Feb 2013 00:49:50 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=uxlpESXrLKmojLCX+SjPaxNPJ/mwNXiNfHlyURxi/ls=; b=TehTl8q4N36/cd5gV/OiIihWcIPqmS6Kui8RgtVk8UuY73kbncpZ3G+jBGJcHaB2Oz kxxo0/MZLWveu+5lNZr2DrGpmAbxL4kgXhxizCo1jhnKYPwSG8fihqRcujLXZUFwSvUW xexzYVzr7lY4GTg81H/hKCw06ZjNf0R38uBiaEYu/wK+hvz8iySRxS1sZ5iMTUJF5vH+ BhOSS142iWtjqWhrywVYXNIv4OxB8MQ6luTiAKExcz5euFNgD9vMKf1IN4irG+vBLU3v 5r5BH9UtVCAIM0+74PTuKvzhqj5dYTSzOwbSVXz+q1aXjsw/G53knFb1i9d5esdub4hD w72Q== MIME-Version: 1.0 X-Received: by 10.52.66.14 with SMTP id b14mr12220417vdt.0.1359794990265; Sat, 02 Feb 2013 00:49:50 -0800 (PST) Received: by 10.220.201.133 with HTTP; Sat, 2 Feb 2013 00:49:50 -0800 (PST) Date: Sat, 2 Feb 2013 10:49:50 +0200 Message-ID: Subject: kern/175227: commit references a PR From: =?KOI8-R?B?4dLUo80g7c/Sz9rP1w==?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 08:49:51 -0000 ---------- Forwarded message ---------- From: Adrian Chadd Date: 2013/2/1 Subject: Re: Block ACK in Ralink RT2860 To: Ramanujan Seshadri Cc: FreeBSD Net , PseudoCylon < moonlightakkiy@yahoo.ca>, freebsd-wireless@freebsd.org Hi, So the 30 second version: * the maximum aggregation size in 802.11n is 65536 bytes, including the between-frame delimiters; * mpdu density defines how big those delimiters are - they're calculated either in bytes or as a function of the currently selected rate and duration, which ends up being a set of bytes anyway; * some hardware may require extra delimiter time between frames to "reset" internal frame processing between MPDUs. The atheros hardware, for examples, sets the default mpdu density to 8 microseconds to allow the encryption hardware to reset fully. It's only needed at the higher rates, but I've not sat down and totally mapped out what behaviour is there so I do it for all rates; * .. and later atheros hardware has a minimum per-MPDU timing and delimiters are added to that to "pad" out a frame to a minimum duration in microseconds. Again, to meet timing requirements in the chip; * bawinsize is negotiated during ADDBA negotiation. The maximum window size is 64 frames but devices may negotiate smaller window sizes if they like; * some hardware / drivers may limit the size of aggregates anyway - eg, the ath(4) aggregation code limits the per-AMPDU size to 32 frames even if the window is 64 frames. This is done to limit the effects of poor reception. Again, I could do a smarter job of it in ideal(er) situations but I've been focusing on other things. HTH, adrian On 31 January 2013 16:48, Ramanujan Seshadri wrote: > I am testing the driver code witht he ralink nic. Yes the frame > aggregation works, since i get higher throughput. I am actually tryign to > know how many frames (MPDU's) are aggregated each time in an AMPDU. > > Regarding the MPDU density - i was wondering how it should affect the Frame > aggregation. Since MPDU density is the time duration between each MPDU sent > within the AMPDU. So, how does this matter to the hardware for aggregating > the number of frames. It just sends MPDU's with the set interval. > > The other two limits make sense, the BAWinSize and the MAX_LEN_CFG. > > Ram > > On Wed, Jan 30, 2013 at 5:45 PM, PseudoCylon wrote: > >> On Wed, Jan 30, 2013 at 1:20 PM, Ramanujan Seshadri >> wrote: >> > Thank you. I also wanted to know the function where the Block ACK Window >> > will be decided. is it decided during the ADDBA session establishment or >> > does it change dynamically. >> >> The hardware will aggregate packets until any of following limits hit max >> http://fxr.watson.org/fxr/source/dev/ral/rt2860reg.h#L782 >> * rt2860_txwi.flags >> RT2860_TX_MPDU_DSITY_SHIFT >> 000 == no restriction >> 001 == 1/4 us >> 010 == 1/2 us >> ... >> 111 == 16 us >> * rt2860_txwi.xflags >> RT2860_TX_BAWINSIZE_SHIFT (frame count) >> >> http://fxr.watson.org/fxr/source/dev/ral/rt2860reg.h#L93 >> * RT2860_MAX_LEN_CFG bit 12:13 >> 00 == 8k bytes >> 01 == 16k >> 10 == 32k >> 11 == 64k >> >> At a quick look, none of them is set in current code. Also, >> RT2860_TX_AMPDU flag need to be set to make the h/w aggregate packets. >> >> How is ampdu working on ral(4)? I cannot test because I do not have >> any ral(4) nic (only have run(4) nics). >> >> >> AK >> >> > >> > >> > On Thu, Jan 24, 2013 at 5:13 PM, PseudoCylon >> > wrote: >> >> >> >> > Message: 6 >> >> > Date: Thu, 24 Jan 2013 12:23:55 -0500 >> >> > From: Ramanujan Seshadri >> >> > To: freebsd-net@freebsd.org >> >> > Subject: Block ACK in Ralink RT2860 >> >> > Message-ID: >> >> > >> >> > >> >> > Content-Type: text/plain; charset=ISO-8859-1 >> >> > >> >> > Hi all, >> >> > I am trying to read the contents of block ack's in a Ralink RT2860 >> >> > driver. >> >> > Can you please help me to know which function i should be looking >> into ? >> >> >> >> At default, all BA packets are dropped by h/w. Clear RT2860_DROP_BA flag >> >> at >> >> http://fxr.watson.org/fxr/source/dev/ral/rt2860.c#L3559 >> >> >> >> Then, the diver should receive BA packets, and you can read them. >> >> >> >> >> >> AK >> > >> > >> > _______________________________________________ > freebsd-net@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-net > To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" _______________________________________________ freebsd-wireless@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-wireless To unsubscribe, send any mail to "freebsd-wireless-unsubscribe@freebsd.org" From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 2 08:54:01 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 1CE49C0F for ; Sat, 2 Feb 2013 08:54:01 +0000 (UTC) (envelope-from hoptoa@gmail.com) Received: from mail-vc0-f172.google.com (mail-vc0-f172.google.com [209.85.220.172]) by mx1.freebsd.org (Postfix) with ESMTP id AEF416C7 for ; Sat, 2 Feb 2013 08:54:00 +0000 (UTC) Received: by mail-vc0-f172.google.com with SMTP id l6so2929496vcl.31 for ; Sat, 02 Feb 2013 00:53:54 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:date:message-id:subject:from:to :content-type; bh=wpRIllUVRFD+WkWE56XuTVV6fUy5cWmWRdAf6PfTEYw=; b=WD+EVT/kZtAJssJotKg4/gtn7wbZbfqqd+C4ka1UC0tNXbufFi5TD2Dt9zpvwYSwK7 nY1iuBBDWBRoAlWw7elrMLqlrneQjv1d/Ra2CUafAYdHc8EFKGillYUMnYjFnIs2QKzj BP/ar2lOVlBbj6NFdu/N0KY025sOcOJi5Vj3a3ZUHeX2hhYO0Uf5U5ET0IhW28b3dkq9 40bxm6vRWXoch9exR4W9b+XbAsdLq8YlnNsuID+MzO/yZ1N2CUAHBII0c0cgKuQfY34N i3RgvuuCrTCAjRy1s/h43dyFnOtHJc3yidtp3u2GMBiNC0tzXF7sld9hpAwosRK5jA+w uTcw== MIME-Version: 1.0 X-Received: by 10.52.27.50 with SMTP id q18mr12149251vdg.20.1359795234638; Sat, 02 Feb 2013 00:53:54 -0800 (PST) Received: by 10.220.201.133 with HTTP; Sat, 2 Feb 2013 00:53:54 -0800 (PST) Date: Sat, 2 Feb 2013 10:53:54 +0200 Message-ID: Subject: D-link DWA-525 From: =?KOI8-R?B?4dLUo80g7c/Sz9rP1w==?= To: freebsd-wireless@freebsd.org Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.14 X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 08:54:01 -0000 Freebsd 9.1 D-link DWA-525 I'm trying to find solution for a long time, i want to lead this wireless NIC to work. NIC works on chipset rt3060 which support on Free BSD from 2012.05, but in spite of that NIC doesn't work. I setting up it without any errors, but when I settings it in client mode card cannot find any works access point. And when I settings card in access point mode, I cannot find even this access point. LED indicator on the NIC show, that card is works and transmit data, but really, it doesn't work. ################################################################################################# root@terst:/usr/home/asd # ifconfig -a ral0: flags=8843 metric 0 mtu 2290 ether 84:c9:b2:7f:07:98 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect mode 11g status: associated vr0: flags=8802 metric 0 mtu 1500 options=82808 ether 00:19:5b:86:11:51 nd6 options=29 media: Ethernet autoselect rl0: flags=8843 metric 0 mtu 1500 options=2008 ether 00:e0:4c:72:62:99 inet 192.168.1.3 netmask 0xffffff00 broadcast 192.168.1.255 nd6 options=29 media: Ethernet autoselect (100baseTX ) status: active re0: flags=8802 metric 0 mtu 1500 options=8209b ether 14:da:e9:ef:88:a2 nd6 options=29 media: Ethernet autoselect (10baseT/UTP ) status: no carrier lo0: flags=8049 metric 0 mtu 16384 options=600003 inet6 ::1 prefixlen 128 inet6 fe80::1%lo0 prefixlen 64 scopeid 0x8 inet 127.0.0.1 netmask 0xff000000 nd6 options=21 wlan0: flags=8843 metric 0 mtu 1500 ether 84:c9:b2:7f:07:98 nd6 options=29 media: IEEE 802.11 Wireless Ethernet autoselect (autoselect) status: no carrier ssid "" channel 7 (2442 MHz 11g) country US authmode OPEN privacy OFF txpower 0 bmiss 7 scanvalid 60 protmode CTS wme bintval 0 ################################################################################################# Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz (3110.54-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x1d9ae3bf AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8210862080 (7830 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392) ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380) acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xe000-0xe07f mem 0xfa000000-0xfaffffff,0xc0000000-0xcfffffff,0xd0000000-0xd1ffffff irq 16 at device 0.0 on pci1 hdac0: mem 0xfb080000-0xfb083fff irq 17 at device 0.1 on pci1 pci0: at device 22.0 (no driver attached) ehci0: mem 0xfb407000-0xfb4073ff irq 23 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 hdac1: mem 0xfb400000-0xfb403fff irq 22 at device 27.0 on pci0 pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 18 at device 28.2 on pci0 pci3: on pcib3 pcib4: irq 19 at device 28.3 on pci0 pci4: on pcib4 pcib5: irq 17 at device 28.4 on pci0 pci5: on pcib5 pcib6: irq 17 at device 0.0 on pci5 pci6: on pcib6 ral0: mem 0xfb310000-0xfb31ffff irq 16 at device 0.0 on pci6 vr0: port 0xd100-0xd1ff mem 0xfb321000-0xfb3210ff irq 17 at device 1.0 on pci6 vr0: Quirks: 0x0 vr0: Revision: 0x8b miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow vr0: Ethernet address: 00:19:5b:86:11:51 rl0: port 0xd000-0xd0ff mem 0xfb320000-0xfb3200ff irq 18 at device 2.0 on pci6 miibus1: on rl0 rlphy0: PHY 0 on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:4c:72:62:99 pcib7: irq 16 at device 28.5 on pci0 pci7: on pcib7 atapci0: port 0xc040-0xc047,0xc030-0xc033,0xc020-0xc027,0xc010-0xc013,0xc000-0xc00f irq 17 at device 0.0 on pci7 ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 pcib8: irq 18 at device 28.6 on pci0 pci8: on pcib8 re0: port 0xb000-0xb0ff mem 0xd2104000-0xd2104fff,0xd2100000-0xd2103fff irq 18 at device 0.0 on pci re0: Using 1 MSI-X message re0: Chip rev. 0x2c000000 re0: MAC rev. 0x00000000 miibus2: on re0 rgephy0: PHY 1 on miibus2 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-F re0: Ethernet address: 14:da:e9:ef:88:a2 pcib9: irq 19 at device 28.7 on pci0 pci9: on pcib9 xhci0: mem 0xfb100000-0xfb107fff irq 19 at device 0.0 on pci9 xhci0: 32 byte context size. usbus1 on xhci0 ehci1: mem 0xfb406000-0xfb4063ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfb405000-0xfb4057ff irq 20 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: cannot reserve I/O port range ctl: CAM Target Layer loaded est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 est2: on cpu2 p4tcc2: on cpu2 est3: on cpu3 p4tcc3: on cpu3 Timecounters tick every 1.000 msec hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 5 on hdaa0 hdacc1: at cad 1 on hdac0 hdaa1: at nid 1 on hdacc1 pcm1: at nid 5 on hdaa1 hdacc2: at cad 2 on hdac0 hdaa2: at nid 1 on hdacc2 pcm2: at nid 5 on hdaa2 hdacc3: at cad 3 on hdac0 hdaa3: at nid 1 on hdacc3 pcm3: at nid 5 on hdaa3 hdacc4: at cad 0 on hdac1 hdaa4: at nid 1 on hdacc4 pcm4: at nid 20,22,21,23 and 24,26 on hdaa4 pcm5: at nid 27 and 25 on hdaa4 pcm6: at nid 30 on hdaa4 pcm7: at nid 17 on hdaa4 usbus0: 480Mbps High Speed USB v2.0 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: <0x1b21> at usbus1 uhub1: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 uhub1: 4 ports with 4 removable, self powered uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered ugen0.2: at usbus0 uhub3: on usbus0 ugen2.2: at usbus2 uhub4: on usbus2 uhub3: 6 ports with 6 removable, self powered uhub4: 8 ports with 8 removable, self powered ugen2.3: at usbus2 ukbd0: on usbus2 kbd2 at ukbd0 ums0: on usbus2 ums0: 16 buttons and [XYZT] coordinates ID=0 ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad8 ada1 at ahcich3 bus 0 scbus3 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad10 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Timecounter "TSC-low" frequency 12150537 Hz quality 1000 Trying to mount root from ufs:/dev/ada0p2 [rw]... Waiting (max 60 seconds) for system process `vnlru' to stop...done Waiting (max 60 seconds) for system process `bufdaemon' to stop...done Waiting (max 60 seconds) for system process `syncer' to stop... Syncing disks, vnodes remaining...1 0 0 done All buffers synced. Copyright (c) 1992-2012 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD is a registered trademark of The FreeBSD Foundation. FreeBSD 9.1-RELEASE #0 r243825: Tue Dec 4 09:23:10 UTC 2012 root@farrell.cse.buffalo.edu:/usr/obj/usr/src/sys/GENERIC amd64 CPU: Intel(R) Core(TM) i3-2100 CPU @ 3.10GHz (3110.53-MHz K8-class CPU) Origin = "GenuineIntel" Id = 0x206a7 Family = 6 Model = 2a Stepping = 7 Features=0xbfebfbff Features2=0x1d9ae3bf AMD Features=0x28100800 AMD Features2=0x1 TSC: P-state invariant, performance statistics real memory = 8589934592 (8192 MB) avail memory = 8210862080 (7830 MB) Event timer "LAPIC" quality 600 ACPI APIC Table: FreeBSD/SMP: Multiprocessor System Detected: 4 CPUs FreeBSD/SMP: 1 package(s) x 2 core(s) x 2 SMT threads cpu0 (BSP): APIC ID: 0 cpu1 (AP): APIC ID: 1 cpu2 (AP): APIC ID: 2 cpu3 (AP): APIC ID: 3 ioapic0 irqs 0-23 on motherboard kbd1 at kbdmux0 acpi0: on motherboard ACPI Error: [RAMB] Namespace lookup failure, AE_NOT_FOUND (20110527/psargs-392) ACPI Exception: AE_NOT_FOUND, Could not execute arguments for [RAMW] (Region) (20110527/nsinit-380) acpi0: Power Button (fixed) cpu0: on acpi0 cpu1: on acpi0 cpu2: on acpi0 cpu3: on acpi0 attimer0: port 0x40-0x43 irq 0 on acpi0 Timecounter "i8254" frequency 1193182 Hz quality 0 Event timer "i8254" frequency 1193182 Hz quality 100 atrtc0: port 0x70-0x71 irq 8 on acpi0 Event timer "RTC" frequency 32768 Hz quality 0 hpet0: iomem 0xfed00000-0xfed003ff on acpi0 Timecounter "HPET" frequency 14318180 Hz quality 950 Event timer "HPET" frequency 14318180 Hz quality 550 Event timer "HPET1" frequency 14318180 Hz quality 440 Event timer "HPET2" frequency 14318180 Hz quality 440 Event timer "HPET3" frequency 14318180 Hz quality 440 Event timer "HPET4" frequency 14318180 Hz quality 440 Timecounter "ACPI-fast" frequency 3579545 Hz quality 900 acpi_timer0: <24-bit timer at 3.579545MHz> port 0x408-0x40b on acpi0 pcib0: port 0xcf8-0xcff on acpi0 pci0: on pcib0 pcib1: irq 16 at device 1.0 on pci0 pci1: on pcib1 vgapci0: port 0xe000-0xe07f mem 0xfa000000-0xfaffffff,0xc0000000-0xcfffffff,0xd0000000-0xd1ffffff irq 16 at device 0.0 on pci1 hdac0: mem 0xfb080000-0xfb083fff irq 17 at device 0.1 on pci1 pci0: at device 22.0 (no driver attached) ehci0: mem 0xfb407000-0xfb4073ff irq 23 at device 26.0 on pci0 usbus0: EHCI version 1.0 usbus0 on ehci0 hdac1: mem 0xfb400000-0xfb403fff irq 22 at device 27.0 on pci0 pcib2: irq 17 at device 28.0 on pci0 pci2: on pcib2 pcib3: irq 18 at device 28.2 on pci0 pci3: on pcib3 pcib4: irq 19 at device 28.3 on pci0 pci4: on pcib4 pcib5: irq 17 at device 28.4 on pci0 pci5: on pcib5 pcib6: irq 17 at device 0.0 on pci5 pci6: on pcib6 ral0: mem 0xfb310000-0xfb31ffff irq 16 at device 0.0 on pci6 vr0: port 0xd100-0xd1ff mem 0xfb321000-0xfb3210ff irq 17 at device 1.0 on pci6 vr0: Quirks: 0x0 vr0: Revision: 0x8b miibus0: on vr0 ukphy0: PHY 1 on miibus0 ukphy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto, auto-flow vr0: Ethernet address: 00:19:5b:86:11:51 rl0: port 0xd000-0xd0ff mem 0xfb320000-0xfb3200ff irq 18 at device 2.0 on pci6 miibus1: on rl0 rlphy0: PHY 0 on miibus1 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto rl0: Ethernet address: 00:e0:4c:72:62:99 pcib7: irq 16 at device 28.5 on pci0 pci7: on pcib7 atapci0: port 0xc040-0xc047,0xc030-0xc033,0xc020-0xc027,0xc010-0xc013,0xc000-0xc00f irq 17 at device 0.0 on pci7 ata2: at channel 0 on atapci0 ata3: at channel 1 on atapci0 pcib8: irq 18 at device 28.6 on pci0 pci8: on pcib8 re0: port 0xb000-0xb0ff mem 0xd2104000-0xd2104fff,0xd2100000-0xd2103fff irq 18 at device 0.0 on pci8 re0: Using 1 MSI-X message re0: Chip rev. 0x2c000000 re0: MAC rev. 0x00000000 miibus2: on re0 rgephy0: PHY 1 on miibus2 rgephy0: none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX, 100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1000baseT-FDX-flow-master, auto, auto-flow re0: Ethernet address: 14:da:e9:ef:88:a2 pcib9: irq 19 at device 28.7 on pci0 pci9: on pcib9 xhci0: mem 0xfb100000-0xfb107fff irq 19 at device 0.0 on pci9 xhci0: 32 byte context size. usbus1 on xhci0 ehci1: mem 0xfb406000-0xfb4063ff irq 23 at device 29.0 on pci0 usbus2: EHCI version 1.0 usbus2 on ehci1 isab0: at device 31.0 on pci0 isa0: on isab0 ahci0: port 0xf070-0xf077,0xf060-0xf063,0xf050-0xf057,0xf040-0xf043,0xf020-0xf03f mem 0xfb405000-0xfb4057ff irq 20 at device 31.2 on pci0 ahci0: AHCI v1.30 with 6 6Gbps ports, Port Multiplier not supported ahcich2: at channel 2 on ahci0 ahcich3: at channel 3 on ahci0 pci0: at device 31.3 (no driver attached) acpi_button0: on acpi0 uart0: <16550 or compatible> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 sc0: at flags 0x100 on isa0 sc0: VGA <16 virtual consoles, flags=0x300> vga0: at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0 atkbdc0: at port 0x60,0x64 on isa0 atkbd0: irq 1 on atkbdc0 kbd0 at atkbd0 atkbd0: [GIANT-LOCKED] ppc0: cannot reserve I/O port range ctl: CAM Target Layer loaded est0: on cpu0 p4tcc0: on cpu0 est1: on cpu1 p4tcc1: on cpu1 est2: on cpu2 p4tcc2: on cpu2 est3: on cpu3 p4tcc3: on cpu3 Timecounters tick every 1.000 msec hdacc0: at cad 0 on hdac0 hdaa0: at nid 1 on hdacc0 pcm0: at nid 5 on hdaa0 hdacc1: at cad 1 on hdac0 hdaa1: at nid 1 on hdacc1 pcm1: at nid 5 on hdaa1 hdacc2: at cad 2 on hdac0 hdaa2: at nid 1 on hdacc2 pcm2: at nid 5 on hdaa2 hdacc3: at cad 3 on hdac0 hdaa3: at nid 1 on hdacc3 pcm3: at nid 5 on hdaa3 hdacc4: at cad 0 on hdac1 hdaa4: at nid 1 on hdacc4 pcm4: at nid 20,22,21,23 and 24,26 on hdaa4 pcm5: at nid 27 and 25 on hdaa4 pcm6: at nid 30 on hdaa4 pcm7: at nid 17 on hdaa4 usbus0: 480Mbps High Speed USB v2.0 usbus1: 5.0Gbps Super Speed USB v3.0 usbus2: 480Mbps High Speed USB v2.0 ugen0.1: at usbus0 uhub0: on usbus0 ugen1.1: <0x1b21> at usbus1 uhub1: <0x1b21 XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1 ugen2.1: at usbus2 uhub2: on usbus2 uhub1: 4 ports with 4 removable, self powered uhub0: 2 ports with 2 removable, self powered uhub2: 2 ports with 2 removable, self powered ugen0.2: at usbus0 uhub3: on usbus0 ugen2.2: at usbus2 uhub4: on usbus2 uhub3: 6 ports with 6 removable, self powered uhub4: 8 ports with 8 removable, self powered ugen2.3: at usbus2 ukbd0: on usbus2 kbd2 at ukbd0 ums0: on usbus2 ums0: 16 buttons and [XYZT] coordinates ID=0 ada0 at ahcich2 bus 0 scbus2 target 0 lun 0 ada0: ATA-8 SATA 2.x device ada0: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada0: Command Queueing enabled ada0: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada0: Previously was known as ad8 ada1 at ahcich3 bus 0 scbus3 target 0 lun 0 ada1: ATA-8 SATA 2.x device ada1: 300.000MB/s transfers (SATA 2.x, UDMA6, PIO 8192bytes) ada1: Command Queueing enabled ada1: 953869MB (1953525168 512 byte sectors: 16H 63S/T 16383C) ada1: Previously was known as ad10 SMP: AP CPU #1 Launched! SMP: AP CPU #2 Launched! SMP: AP CPU #3 Launched! Timecounter "TSC-low" frequency 12150518 Hz quality 1000 Trying to mount root from ufs:/dev/ada0p2 [rw]... wlan0: Ethernet address: 84:c9:b2:7f:07:98 From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 2 10:06:52 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 350FDF8C for ; Sat, 2 Feb 2013 10:06:52 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-wi0-f175.google.com (mail-wi0-f175.google.com [209.85.212.175]) by mx1.freebsd.org (Postfix) with ESMTP id C1FDB8B5 for ; Sat, 2 Feb 2013 10:06:51 +0000 (UTC) Received: by mail-wi0-f175.google.com with SMTP id l13so897060wie.2 for ; Sat, 02 Feb 2013 02:06:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:content-transfer-encoding; bh=JCQ7SL95BBpYMMUKRwZyebfPUT2iNEBNMHeIOZdqPSg=; b=fURRd9sOY7h0BywMsYQjmh7Wy3qvAvA194Y5ygBwnj5wkKPlVcA5eFsZOBNiv1FdGa gBSWlC31inffl+/iJZWsVMn0TlsmI+pNBzx3k661gKvXFi84rzw40Z/GTAiBSHYUQ2ZD 5i1AzK13mR4kgjt1EA9fB3RW6wd7/iFTH3Ds/iP+zTIu8h+N4Ubg4J7jt4sFuXUkwc/Q FHpYzkCvZgR0gYk9s8HFE2msUw8YRK5PXuHAAP08vgHOO4klbr1YI34Afgqwbr4Uv6rH NsMUB7O8sBe07h2bRuT02Gk24ooeZ/hzxGl9MCjdVAgUPllp6bDq9B3CieupiVdNdjzb OLpw== MIME-Version: 1.0 X-Received: by 10.194.172.197 with SMTP id be5mr26244410wjc.20.1359799604748; Sat, 02 Feb 2013 02:06:44 -0800 (PST) Received: by 10.216.98.5 with HTTP; Sat, 2 Feb 2013 02:06:44 -0800 (PST) In-Reply-To: References: <4f00f1d5.1446e70a.3836.ffffc25f@mx.google.com> Date: Sat, 2 Feb 2013 02:06:44 -0800 Message-ID: Subject: Re: ath "stops working" in hostap mode From: Adrian Chadd To: "Lay, Nathan" Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 10:06:52 -0000 Hi, So what happens when you turn off the devices in question? Do things settle down? Adrian On 1 February 2013 22:45, Lay, Nathan wrote: > One last observation, the Roku and the tablet both employ Broadcom Wi-Fi = chipsets ... > > Lastly, thanks for all your hard work on if_ath and FreeBSD. > > Nate > > ________________________________________ > From: Lay, Nathan > Sent: Saturday, February 02, 2013 1:26 AM > To: Adrian Chadd > Subject: RE: ath "stops working" in hostap mode > > Hi Adrian, > Ugh, I neglected to provide this updated information: > > FreeBSD RADIO.LOCAL 9.1-STABLE FreeBSD 9.1-STABLE #0 r245019: Fri Jan 4 = 00:02:39 EST 2013 root@RADIO.LOCAL:/usr/obj/usr/src/sys/RADIO amd64 > > ath0@pci0:1:0:0: class=3D0x028000 card=3D0x3a701186 chip=3D0x00241= 68c rev=3D0x01 hdr=3D0x00 > vendor =3D 'Atheros Communications Inc.' > device =3D 'AR5008 Wireless Network Adapter' > class =3D network > > ath0: mem 0xfe9f0000-0xfe9fffff irq 16 at device 0.0 on pc= i1 > ath0: AR5418 mac 12.10 RF2133 phy 8.1 > > NOTE: I claimed that it worked flawlessly in FreeBSD 8.x (and it did) ...= but I did not test 8.x with this kind of device. This bug may manifest its= elf in 8.x with Roku too. But it does seem to correlate with low power devi= ces. I had introduced a phone and tablet to the network when the problem fi= rst appeared (9.0-RELEASE had just been released or was released for a whil= e). I no longer use the tablet and haven't seen this problem in most of the= 2012 year. > > Best regards, > Nathan Lay > ________________________________________ > From: Lay, Nathan > Sent: Saturday, February 02, 2013 1:16 AM > To: Adrian Chadd > Subject: RE: ath "stops working" in hostap mode > > Hi Adrian, > The problem vanished for most of the year and has recently resurfaced. I = just introduced a Roku 2 XD onto the network two days ago. It is a low pow= er device and, as far as I can tell, sits idle on the Wi-Fi network most of= the time. The introduction of this device appears to be responsible for at= h "stopping." > > Just as a recap, the problem NIC is an AR2416 (D-Link DWA 556). It somet= imes drops off of Wi-Fi scans and is unresponsive and requires the driver i= tself being reloaded to restore service. > > One symptom of the problem is that bexmit (from athstats) drops below 5. = Once that happens, ath is "stuck" and the driver must be unloaded and loade= d again to "unstuck" it. This heuristic is so reliable that I employ a cron= script that checks bexmit every minute and it has triggered maybe twice in= the entire year of 2012. And it has triggered about 4-5 times since I intr= oduced Roku 2 two days ago. > > I hope that this new information is helpful. Since it is now quasi-reprod= ucible, I would be happy to help you collect debug information. > > Best regards, > Nathan Lay > > ________________________________________ > From: Lay, Nathan > Sent: Friday, January 06, 2012 9:01 PM > To: Adrian Chadd > Subject: RE: ath "stops working" in hostap mode > > It's fine. I'm horrendously busy too! As I said, I never expected immedia= te responses to my problem. > > I'll do what I can and let you know if I find anything. > > Best Regards, > Nathan Lay > > ________________________________________ > From: Adrian Chadd [adrian.chadd@gmail.com] > Sent: Friday, January 06, 2012 5:52 PM > To: Lay, Nathan > Subject: Re: ath "stops working" in hostap mode > > Hi, > > I've not forgotten about this, I'm just working on other things at the mo= ment. > > Are you able to try older snapshots of a -HEAD kernel to see where I > introduced it? I think that's going to be by far the easiest way to > establish what happened. > > Thanks, > > > > Adrian > > On 2 January 2012 14:51, Lay, Nathan wrote: >> You'll be delighted/disappointed to know that this still happens when co= nfigured to use channel 5:g (as opposed to 5:ht/40). >> >> Thought you would like to know. >> >> Best Regards, >> Nathan Lay >> ________________________________________ >> From: Adrian Chadd [adrian.chadd@gmail.com] >> Sent: Sunday, January 01, 2012 6:52 PM >> To: Lay, Nathan >> Subject: RE: ath "stops working" in hostap mode >> >> Hah it's fine! I want it fixed! >> >> Thanks for chasing this up with me. >> >> Where in the us are you, btw? >> >> >> >> Adrian >> >> >> >> Sent from my Palm Pre on AT&T >> >> ________________________________ >> On Jan 1, 2012 3:37 PM, Lay, Nathan wrote: >> >> Of course! I hope you don't have the impression that I expect immediate = responses! >> >> I'll create the PR now. >> >> Best Regards, >> Nathan Lay >> >> ________________________________ >> From: Adrian Chadd [adrian.chadd@gmail.com] >> Sent: Sunday, January 01, 2012 6:34 PM >> To: Lay, Nathan >> Subject: RE: ath "stops working" in hostap mode >> >> I'm currently out today, lets revisit this tuesday? >> >> Please create a pr. :) >> >> >> Adrian >> >> >> >> Sent from my Palm Pre on AT&T >> >> ________________________________ >> On Jan 1, 2012 3:32 PM, Lay, Nathan wrote: >> >> Shall I check out various revisions and try them out? >> >> Can you name any SVN revisions that are suspect? It also seems to happen= more frequently when debug options are turned on (which is a good thing). >> >> Best Regards, >> Nathan Lay >> >> ________________________________ >> From: Adrian Chadd [adrian.chadd@gmail.com] >> Sent: Sunday, January 01, 2012 6:31 PM >> To: Lay, Nathan >> Subject: RE: ath "stops working" in hostap mode >> >> Ah good! A regression we can track down. >> >> >> Adrian >> >> >> >> Sent from my Palm Pre on AT&T >> >> ________________________________ >> On Jan 1, 2012 2:15 PM, Lay, Nathan wrote: >> >> Of course! I'll do it today! I promise. >> >> However, I should also mention that this bug appears to be introduced. T= his card was very stable in hostap mode on 8.x. I'm glad that I ran into th= is problem if there are so few AR5416 users. >> >> Best Regards, >> Nathan Lay >> >> ________________________________________ >> From: Adrian Chadd [adrian.chadd@gmail.com] >> Sent: Sunday, January 01, 2012 5:00 PM >> To: Lay, Nathan >> Subject: Re: ath "stops working" in hostap mode >> >> On 1 January 2012 13:38, Lay, Nathan wrote: >>> Unloading/reloading the module seems to fix it. >>> >>> I'll just make a cron job that checks for bexmit <=3D 5 and fixes the w= lan if it happens. >> >> That's fine, just please don't forget to create a PR. I'd like to fix >> the driver so you don't _have_ to unload and reload it. >> It's also plausible this sort of bug affects later chips too, as the >> 11n NICs all share code with the AR5416 NIC. >> >> >> Adrian >> >> >> > > From owner-freebsd-wireless@FreeBSD.ORG Sat Feb 2 20:10:05 2013 Return-Path: Delivered-To: freebsd-wireless@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id B06289D5 for ; Sat, 2 Feb 2013 20:10:05 +0000 (UTC) (envelope-from adrian.chadd@gmail.com) Received: from mail-we0-x22b.google.com (we-in-x022b.1e100.net [IPv6:2a00:1450:400c:c03::22b]) by mx1.freebsd.org (Postfix) with ESMTP id 498382A9 for ; Sat, 2 Feb 2013 20:10:05 +0000 (UTC) Received: by mail-we0-f171.google.com with SMTP id u54so3912834wey.16 for ; Sat, 02 Feb 2013 12:10:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=hF1WYSnZEUyjmVXpOFqm2/XWxny5HNPw7b/r8yMazeA=; b=S1XfmHbgU6GkGadyqPHDOnfw1hPsPDUygzfcPQ4otz0Rzme8dZLISYDOY+Ggl3saSK 10QHBPcBSuMSgEubqkXT1rH6oU+IUtdSlNUDD9qtp2Wx5ruVOBVfCGcgrCDevYbGmaDw zo4VQe3r+GBOiFyvCpXnKFcugvOciONNRFf8xgWUjLusRgAIZ2E2zkq98uFYS0TSJsRs ErkOqQRHx9J+jxUke9NvPpslMJ7JkLuXEPnzPIX0XMYQvBsxXbM5y3oZigvdyw2+wp2i KkpMombY+mktX+CHk5svCi0lxSIBejuqzEFQkHkJT8x65lOrgpJ7oTg/86w6PQwZutE/ A79g== MIME-Version: 1.0 X-Received: by 10.194.156.170 with SMTP id wf10mr9662658wjb.25.1359835804547; Sat, 02 Feb 2013 12:10:04 -0800 (PST) Received: by 10.216.98.5 with HTTP; Sat, 2 Feb 2013 12:10:04 -0800 (PST) In-Reply-To: References: <4f00f1d5.1446e70a.3836.ffffc25f@mx.google.com> Date: Sat, 2 Feb 2013 12:10:04 -0800 Message-ID: Subject: Re: ath "stops working" in hostap mode From: Adrian Chadd To: "Lay, Nathan" Content-Type: text/plain; charset=ISO-8859-1 Cc: freebsd-wireless@freebsd.org X-BeenThere: freebsd-wireless@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Discussions of 802.11 stack, tools device driver development." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 20:10:05 -0000 Hi, On 2 February 2013 07:59, Lay, Nathan wrote: > Hi Adrian, > That's a good question. I'm going to try various things this week to pinpoint the problem. I'll let you know what I find. Please do. I have an earlier model Roku that doesn't show any of the same behaviour. adrian