* Auth Packet TX Delay [not found] <CAMgrJ3Y9=K4umoLD=htrrW-Wn4Hgi7qfaKDpY55_GKd=KgD==A@mail.gmail.com> @ 2013-01-15 22:06 ` Robert Shade 2013-01-16 23:09 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-01-15 22:06 UTC (permalink / raw) To: linux-wireless, ath9k-devel I'm seeing a periodic issue where the device seems to get stuck in a state where the TX of authentication packets is delayed so that authentication fails. The log snippet below shows the auth packets getting queued after each "wlan0: send auth to XX", but they're not actually sent until after it gives up and restarts scanning. Once the device gets into this state, it stays in a SCAN->AUTH->AUTH FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 down, the device usually recovers and works correctly for a few minutes to hours. This is with the latest compat-drivers. The authentication is EAP-TLS and it's in an environment where it periodically roams using wpa_supplicant's bgscan. Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc 0x10f eol 0x10f urn 0x0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, rssi=67[lo=7 hi=40] Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level 3=>7[def:3] cycpwrThr1[level]=14 ini=6 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level 2=>6[def:2] firstep[level]=10 ini=2 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level 2=>6[def:2] firstep_low[level]=14 ini=6 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, rssi=67[lo=7 hi=40] Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet associated..skipping beacon config Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured for a station interface Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: ffff880137846a80 Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): supplicant interface state: scanning -> authenticating Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 ifi_flags=0x1003 ([UP]) Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed already cleared - ignore event Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station 00:24:6c:74:0a:40 Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: ffff8801265cc2c0 Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] (ffff8800378480c8)=37847568 (ffff880037847568) Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: ffff8801261aac80 Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] (ffff880037847568)=378465f8 (ffff8800378465f8) Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station 00:24:6c:74:0a:40 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; timeout with 00:24:6c:74:0a:40 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event AUTH_TIMED_OUT (14) received Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: Authentication timed out Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID 00:24:6c:74:0a:40 into blacklist Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in this ESS has been seen; try it next Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 blacklist count incremented to 2 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan request: 0 sec 100000 usec Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: AUTHENTICATING -> DISCONNECTED Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: linkmode=-1, operstate=5 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External notification - portEnabled=0 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port status: Unauthorized Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External notification - portValid=0 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port status: Unauthorized Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with 00:24:6c:74:0a:40 timed out Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1 Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): supplicant interface state: authenticating -> disconnected Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: DISCONNECTED -> SCANNING Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan for wildcard SSID Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), correcting to MAX Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), correcting to MAX Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), correcting to MAX Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 17:00.0 Network controller: Atheros Communications Inc. AR9160 Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless Mini PCI Adapter Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx- Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx- Latency: 168, Cache Line Size: 32 bytes Interrupt: pin A routed to IRQ 18 Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] Capabilities: [44] Power Management version 2 Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA PME(D0+,D1-,D2-,D3hot+,D3cold-) Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- Kernel driver in use: ath9k Kernel modules: ath9k The last time I saw this on a device that I could debug with, I saw the following in the log just before it entered this state: Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan results available Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event SCAN_RESULTS (3) received Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with 00:17:59:2c:c3:20 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan results (45 BSSes) Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results indicate BSS status with 00:17:59:2c:c3:20 as associated Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan result notification Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS from priority group 0 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 caps=0xc31 level=-56 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for other virtual interfaces sharing same radio (phy1) in event_scan_results Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: flush_object_timeout_handler: Timeout - sending changed properties of object /fi/w1/wpa_supplicant1/Interfaces/1 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, IFLA_IFNAME: Interface 'wlan0' added Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed already cleared - ignore event Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, reset status -5 Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP 00:17:59:2c:c3:20 after 500ms, disconnecting Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station 00:17:59:2c:c3:20 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 14 00 17 59 2c c3 20 00 00 04 00 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication notification Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 (locally generated) Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address 00:17:59:2c:c3:20 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame IE(s) - hexdump(len=0): [NULL] Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 locally_generated=1 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect enabled: try to reconnect (wps=0 wpa_state=9) Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan request: 0 sec 100000 usec Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID 00:17:59:2c:c3:20 into blacklist Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in this ESS has been seen; try it next Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 blacklist count incremented to 2 Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling scan to ensure that specific SSID scans occur Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event - remove keys Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 set_tx=0 seq_len=0 key_len=0 Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 (goes into associate timeout loop) Please let me know if you need any additional information or testing done. Thanks. ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-01-15 22:06 ` Auth Packet TX Delay Robert Shade @ 2013-01-16 23:09 ` Adrian Chadd 2013-01-17 1:00 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-01-16 23:09 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in fast channel change. Maybe ath9k's fast channel change code isn't working right, and it's not trying a full channel change afterwards? Adrian On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: > I'm seeing a periodic issue where the device seems to get stuck in a > state where the TX of authentication packets is delayed so that > authentication fails. The log snippet below shows the auth packets > getting queued after each "wlan0: send auth to XX", but they're not > actually sent until after it gives up and restarts scanning. Once the > device gets into this state, it stays in a SCAN->AUTH->AUTH > FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 > down, the device usually recovers and works correctly for a few minutes to > hours. > > This is with the latest compat-drivers. The authentication is EAP-TLS > and it's in an environment where it periodically roams using > wpa_supplicant's bgscan. > > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc > 0x10f eol 0x10f urn 0x0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc > 0x10f eol 0x10f urn 0x0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc > 0x10f eol 0x10f urn 0x0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc > 0x10f eol 0x10f urn 0x0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc > 0x10f eol 0x10f urn 0x0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc > 0x10f eol 0x10f urn 0x0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration > Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration > Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration > Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 > chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, > rssi=67[lo=7 hi=40] > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level > 3=>7[def:3] cycpwrThr1[level]=14 ini=6 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level > 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, > ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level > 2=>6[def:2] firstep[level]=10 ini=2 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level > 2=>6[def:2] firstep_low[level]=14 ini=6 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, > ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off > Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, > ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, > rssi=67[lo=7 hi=40] > Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet > associated..skipping beacon config > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured > for a station interface > Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 > Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) > Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: > ffff880137846a80 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 > Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): > supplicant interface state: scanning -> authenticating > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 > ifi_flags=0x1003 ([UP]) > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, > IFLA_IFNAME: Interface 'wlan0' added > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed > already cleared - ignore event > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station > 00:24:6c:74:0a:40 > Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) > Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: > ffff8801265cc2c0 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] > (ffff8800378480c8)=37847568 (ffff880037847568) > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 > Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) > Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: > ffff8801261aac80 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 > Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] > (ffff880037847568)=378465f8 (ffff8800378465f8) > Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station > 00:24:6c:74:0a:40 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; > timeout with 00:24:6c:74:0a:40 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event > AUTH_TIMED_OUT (14) received > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: > Authentication timed out > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID > 00:24:6c:74:0a:40 into blacklist > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in > this ESS has been seen; try it next > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 > blacklist count incremented to 2 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan > request: 0 sec 100000 usec > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: > AUTHENTICATING -> DISCONNECTED > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: > wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: > linkmode=-1, operstate=5 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External > notification - portEnabled=0 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port > status: Unauthorized > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External > notification - portValid=0 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port > status: Unauthorized > Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with > 00:24:6c:74:0a:40 timed out > Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: > flush_object_timeout_handler: Timeout - sending changed properties of > object /fi/w1/wpa_supplicant1/Interfaces/1 > Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): > supplicant interface state: authenticating -> disconnected > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: > DISCONNECTED -> SCANNING > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan > for wildcard SSID > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz > Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz > Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP > Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE > Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP > Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE > Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), > correcting to MAX > Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), > correcting to MAX > Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), > correcting to MAX > Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI > Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER > Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters > Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 > Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 > > 17:00.0 Network controller: Atheros Communications Inc. AR9160 > Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) > Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless > Mini PCI Adapter > Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- > Stepping- SERR- FastB2B- DisINTx- > Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- > <TAbort- <MAbort- >SERR- <PERR- INTx- > Latency: 168, Cache Line Size: 32 bytes > Interrupt: pin A routed to IRQ 18 > Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] > Capabilities: [44] Power Management version 2 > Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA > PME(D0+,D1-,D2-,D3hot+,D3cold-) > Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- > Kernel driver in use: ath9k > Kernel modules: ath9k > > The last time I saw this on a device that I could debug with, I saw > the following in the log just before it entered this state: > > Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX > Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX > Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX > Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 > Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX > Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan > results available > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event > SCAN_RESULTS (3) received > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with > 00:17:59:2c:c3:20 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan > results (45 BSSes) > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results > indicate BSS status with 00:17:59:2c:c3:20 as associated > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan > result notification > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS > from priority group 0 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: > 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 > caps=0xc31 level=-56 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS > 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for > other virtual interfaces sharing same radio (phy1) in > event_scan_results > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: > flush_object_timeout_handler: Timeout - sending changed properties of > object /fi/w1/wpa_supplicant1/Interfaces/1 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 > ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, > IFLA_IFNAME: Interface 'wlan0' added > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed > already cleared - ignore event > Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg > 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 > Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, > reset status -5 > Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available > Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP > 00:17:59:2c:c3:20 after 500ms, disconnecting > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station > 00:17:59:2c:c3:20 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event > frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 > 14 00 17 59 2c c3 20 00 00 04 00 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication > notification > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 > (locally generated) > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address > 00:17:59:2c:c3:20 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame > IE(s) - hexdump(len=0): [NULL] > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: > CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 > locally_generated=1 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect > enabled: try to reconnect (wps=0 wpa_state=9) > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan > request: 0 sec 100000 usec > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID > 00:17:59:2c:c3:20 into blacklist > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in > this ESS has been seen; try it next > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 > blacklist count incremented to 2 > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling > scan to ensure that specific SSID scans occur > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event > - remove keys > Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: > wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 > set_tx=0 seq_len=0 key_len=0 > Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 > Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 > Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 > Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 > (goes into associate timeout loop) > > Please let me know if you need any additional information or testing > done. Thanks. > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-01-16 23:09 ` Adrian Chadd @ 2013-01-17 1:00 ` Robert Shade 2013-01-17 3:12 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-01-17 1:00 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel I was able to grab a log with debugging on when the issue started all the way to when it started timing out association due to TX delay: https://dl.dropbox.com/u/12121487/delay-messages.gz On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in > fast channel change. > > Maybe ath9k's fast channel change code isn't working right, and it's > not trying a full channel change afterwards? > > > > Adrian > > > On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >> I'm seeing a periodic issue where the device seems to get stuck in a >> state where the TX of authentication packets is delayed so that >> authentication fails. The log snippet below shows the auth packets >> getting queued after each "wlan0: send auth to XX", but they're not >> actually sent until after it gives up and restarts scanning. Once the >> device gets into this state, it stays in a SCAN->AUTH->AUTH >> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >> down, the device usually recovers and works correctly for a few minutes to >> hours. >> >> This is with the latest compat-drivers. The authentication is EAP-TLS >> and it's in an environment where it periodically roams using >> wpa_supplicant's bgscan. >> >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >> 0x10f eol 0x10f urn 0x0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >> 0x10f eol 0x10f urn 0x0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >> 0x10f eol 0x10f urn 0x0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >> 0x10f eol 0x10f urn 0x0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >> 0x10f eol 0x10f urn 0x0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >> 0x10f eol 0x10f urn 0x0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >> rssi=67[lo=7 hi=40] >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >> 2=>6[def:2] firstep[level]=10 ini=2 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >> 2=>6[def:2] firstep_low[level]=14 ini=6 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >> rssi=67[lo=7 hi=40] >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >> associated..skipping beacon config >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >> for a station interface >> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >> ffff880137846a80 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >> supplicant interface state: scanning -> authenticating >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >> ifi_flags=0x1003 ([UP]) >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >> IFLA_IFNAME: Interface 'wlan0' added >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >> already cleared - ignore event >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >> 00:24:6c:74:0a:40 >> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >> ffff8801265cc2c0 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >> (ffff8800378480c8)=37847568 (ffff880037847568) >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >> ffff8801261aac80 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >> (ffff880037847568)=378465f8 (ffff8800378465f8) >> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >> 00:24:6c:74:0a:40 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >> timeout with 00:24:6c:74:0a:40 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >> AUTH_TIMED_OUT (14) received >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >> Authentication timed out >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >> 00:24:6c:74:0a:40 into blacklist >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >> this ESS has been seen; try it next >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >> blacklist count incremented to 2 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >> request: 0 sec 100000 usec >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >> AUTHENTICATING -> DISCONNECTED >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >> linkmode=-1, operstate=5 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >> notification - portEnabled=0 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >> status: Unauthorized >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >> notification - portValid=0 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >> status: Unauthorized >> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >> 00:24:6c:74:0a:40 timed out >> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >> flush_object_timeout_handler: Timeout - sending changed properties of >> object /fi/w1/wpa_supplicant1/Interfaces/1 >> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >> supplicant interface state: authenticating -> disconnected >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >> DISCONNECTED -> SCANNING >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >> for wildcard SSID >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >> correcting to MAX >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >> correcting to MAX >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >> correcting to MAX >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >> >> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >> Mini PCI Adapter >> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >> Stepping- SERR- FastB2B- DisINTx- >> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >> <TAbort- <MAbort- >SERR- <PERR- INTx- >> Latency: 168, Cache Line Size: 32 bytes >> Interrupt: pin A routed to IRQ 18 >> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >> Capabilities: [44] Power Management version 2 >> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >> PME(D0+,D1-,D2-,D3hot+,D3cold-) >> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >> Kernel driver in use: ath9k >> Kernel modules: ath9k >> >> The last time I saw this on a device that I could debug with, I saw >> the following in the log just before it entered this state: >> >> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >> results available >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >> SCAN_RESULTS (3) received >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >> 00:17:59:2c:c3:20 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >> results (45 BSSes) >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >> indicate BSS status with 00:17:59:2c:c3:20 as associated >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >> result notification >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >> from priority group 0 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >> caps=0xc31 level=-56 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >> other virtual interfaces sharing same radio (phy1) in >> event_scan_results >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >> flush_object_timeout_handler: Timeout - sending changed properties of >> object /fi/w1/wpa_supplicant1/Interfaces/1 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >> IFLA_IFNAME: Interface 'wlan0' added >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >> already cleared - ignore event >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >> reset status -5 >> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >> 00:17:59:2c:c3:20 after 500ms, disconnecting >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >> 00:17:59:2c:c3:20 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >> 14 00 17 59 2c c3 20 00 00 04 00 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >> notification >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >> (locally generated) >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >> 00:17:59:2c:c3:20 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >> IE(s) - hexdump(len=0): [NULL] >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >> locally_generated=1 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >> enabled: try to reconnect (wps=0 wpa_state=9) >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >> request: 0 sec 100000 usec >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >> 00:17:59:2c:c3:20 into blacklist >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >> this ESS has been seen; try it next >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >> blacklist count incremented to 2 >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >> scan to ensure that specific SSID scans occur >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >> - remove keys >> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >> set_tx=0 seq_len=0 key_len=0 >> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >> (goes into associate timeout loop) >> >> Please let me know if you need any additional information or testing >> done. Thanks. >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-01-17 1:00 ` Robert Shade @ 2013-01-17 3:12 ` Adrian Chadd 2013-02-06 2:51 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-01-17 3:12 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel Find where the fast channel change code is (maybe) called, and just disable it so it always calls the full channel change? Adrian On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: > I was able to grab a log with debugging on when the issue started all > the way to when it started timing out association due to TX delay: > https://dl.dropbox.com/u/12121487/delay-messages.gz > > On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >> fast channel change. >> >> Maybe ath9k's fast channel change code isn't working right, and it's >> not trying a full channel change afterwards? >> >> >> >> Adrian >> >> >> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>> I'm seeing a periodic issue where the device seems to get stuck in a >>> state where the TX of authentication packets is delayed so that >>> authentication fails. The log snippet below shows the auth packets >>> getting queued after each "wlan0: send auth to XX", but they're not >>> actually sent until after it gives up and restarts scanning. Once the >>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>> down, the device usually recovers and works correctly for a few minutes to >>> hours. >>> >>> This is with the latest compat-drivers. The authentication is EAP-TLS >>> and it's in an environment where it periodically roams using >>> wpa_supplicant's bgscan. >>> >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>> 0x10f eol 0x10f urn 0x0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>> 0x10f eol 0x10f urn 0x0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>> 0x10f eol 0x10f urn 0x0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>> 0x10f eol 0x10f urn 0x0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>> 0x10f eol 0x10f urn 0x0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>> 0x10f eol 0x10f urn 0x0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>> rssi=67[lo=7 hi=40] >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>> 2=>6[def:2] firstep[level]=10 ini=2 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>> rssi=67[lo=7 hi=40] >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>> associated..skipping beacon config >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>> for a station interface >>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>> ffff880137846a80 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>> supplicant interface state: scanning -> authenticating >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>> ifi_flags=0x1003 ([UP]) >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>> IFLA_IFNAME: Interface 'wlan0' added >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>> already cleared - ignore event >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>> 00:24:6c:74:0a:40 >>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>> ffff8801265cc2c0 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>> (ffff8800378480c8)=37847568 (ffff880037847568) >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>> ffff8801261aac80 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>> 00:24:6c:74:0a:40 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>> timeout with 00:24:6c:74:0a:40 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>> AUTH_TIMED_OUT (14) received >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>> Authentication timed out >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>> 00:24:6c:74:0a:40 into blacklist >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>> this ESS has been seen; try it next >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>> blacklist count incremented to 2 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>> request: 0 sec 100000 usec >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>> AUTHENTICATING -> DISCONNECTED >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>> linkmode=-1, operstate=5 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>> notification - portEnabled=0 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>> status: Unauthorized >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>> notification - portValid=0 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>> status: Unauthorized >>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>> 00:24:6c:74:0a:40 timed out >>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>> flush_object_timeout_handler: Timeout - sending changed properties of >>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>> supplicant interface state: authenticating -> disconnected >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>> DISCONNECTED -> SCANNING >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>> for wildcard SSID >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>> correcting to MAX >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>> correcting to MAX >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>> correcting to MAX >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>> >>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>> Mini PCI Adapter >>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>> Stepping- SERR- FastB2B- DisINTx- >>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>> Latency: 168, Cache Line Size: 32 bytes >>> Interrupt: pin A routed to IRQ 18 >>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>> Capabilities: [44] Power Management version 2 >>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>> Kernel driver in use: ath9k >>> Kernel modules: ath9k >>> >>> The last time I saw this on a device that I could debug with, I saw >>> the following in the log just before it entered this state: >>> >>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>> results available >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>> SCAN_RESULTS (3) received >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>> 00:17:59:2c:c3:20 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>> results (45 BSSes) >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>> result notification >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>> from priority group 0 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>> caps=0xc31 level=-56 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>> other virtual interfaces sharing same radio (phy1) in >>> event_scan_results >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>> flush_object_timeout_handler: Timeout - sending changed properties of >>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>> IFLA_IFNAME: Interface 'wlan0' added >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>> already cleared - ignore event >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>> reset status -5 >>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>> 00:17:59:2c:c3:20 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>> 14 00 17 59 2c c3 20 00 00 04 00 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>> notification >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>> (locally generated) >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>> 00:17:59:2c:c3:20 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>> IE(s) - hexdump(len=0): [NULL] >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>> locally_generated=1 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>> enabled: try to reconnect (wps=0 wpa_state=9) >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>> request: 0 sec 100000 usec >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>> 00:17:59:2c:c3:20 into blacklist >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>> this ESS has been seen; try it next >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>> blacklist count incremented to 2 >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>> scan to ensure that specific SSID scans occur >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>> - remove keys >>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>> set_tx=0 seq_len=0 key_len=0 >>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>> (goes into associate timeout loop) >>> >>> Please let me know if you need any additional information or testing >>> done. Thanks. >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-wireless" in > the body of a message to majordomo@vger.kernel.org > More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-01-17 3:12 ` Adrian Chadd @ 2013-02-06 2:51 ` Robert Shade 2013-02-06 3:08 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-02-06 2:51 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel I was finally able to do some additional testing on this. I disabled the one and only block that calls ath9k_hw_do_fastcc. The issue is still reproducible[1], starting with a timeout on AR_PHY_AGC_CONTROL kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 kernel: ath: phy1: offset calibration failed to complete in 1ms; noisy environment? kernel: ath: phy1: Unable to reset channel, reset status -5 kernel: ath: phy1: Unable to set channel It fails to change channel a number of times as it tries to scan, then auth. After it gives up on the auth it goes through a AWAKE -> FULL-SLEEP, FULL-SLEEP -> AWAKE, AWAKE -> FULL-SLEEP, FULL-SLEEP -> AWAKE cycle. Afterward, it's able to change channel to the channel the SSID is on and xmit the auth requests, however by that time it's too late. It continues to scan and re-auth, however the auth packets are not sent until it gives up and goes through another AWAKE/FULL-SLEEP cycle after the auth times out. The radio seems to actually be transmitting because I see the SSID probe requests going out and I see my non-broadcasted SSID in the scan logs. [1] It happens randomly on my devices in the field, but I'm able to make it happen pretty quickly if I start a flood ping to my wireless gw and do continuous scans with iw. On Wed, Jan 16, 2013 at 10:12 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Find where the fast channel change code is (maybe) called, and just > disable it so it always calls the full channel change? > > > > Adrian > > > On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: >> I was able to grab a log with debugging on when the issue started all >> the way to when it started timing out association due to TX delay: >> https://dl.dropbox.com/u/12121487/delay-messages.gz >> >> On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >>> fast channel change. >>> >>> Maybe ath9k's fast channel change code isn't working right, and it's >>> not trying a full channel change afterwards? >>> >>> >>> >>> Adrian >>> >>> >>> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>>> I'm seeing a periodic issue where the device seems to get stuck in a >>>> state where the TX of authentication packets is delayed so that >>>> authentication fails. The log snippet below shows the auth packets >>>> getting queued after each "wlan0: send auth to XX", but they're not >>>> actually sent until after it gives up and restarts scanning. Once the >>>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>>> down, the device usually recovers and works correctly for a few minutes to >>>> hours. >>>> >>>> This is with the latest compat-drivers. The authentication is EAP-TLS >>>> and it's in an environment where it periodically roams using >>>> wpa_supplicant's bgscan. >>>> >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>> 0x10f eol 0x10f urn 0x0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>> 0x10f eol 0x10f urn 0x0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>> 0x10f eol 0x10f urn 0x0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>> 0x10f eol 0x10f urn 0x0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>> 0x10f eol 0x10f urn 0x0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>> 0x10f eol 0x10f urn 0x0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>>> rssi=67[lo=7 hi=40] >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>> 2=>6[def:2] firstep[level]=10 ini=2 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>>> rssi=67[lo=7 hi=40] >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>>> associated..skipping beacon config >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>>> for a station interface >>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>> ffff880137846a80 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>> supplicant interface state: scanning -> authenticating >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>>> ifi_flags=0x1003 ([UP]) >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>>> IFLA_IFNAME: Interface 'wlan0' added >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>>> already cleared - ignore event >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>>> 00:24:6c:74:0a:40 >>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>> ffff8801265cc2c0 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>> (ffff8800378480c8)=37847568 (ffff880037847568) >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>> ffff8801261aac80 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>>> 00:24:6c:74:0a:40 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>>> timeout with 00:24:6c:74:0a:40 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>>> AUTH_TIMED_OUT (14) received >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>>> Authentication timed out >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>>> 00:24:6c:74:0a:40 into blacklist >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>>> this ESS has been seen; try it next >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>>> blacklist count incremented to 2 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>>> request: 0 sec 100000 usec >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>> AUTHENTICATING -> DISCONNECTED >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>>> linkmode=-1, operstate=5 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>> notification - portEnabled=0 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>> status: Unauthorized >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>> notification - portValid=0 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>> status: Unauthorized >>>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>>> 00:24:6c:74:0a:40 timed out >>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>> supplicant interface state: authenticating -> disconnected >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>> DISCONNECTED -> SCANNING >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>>> for wildcard SSID >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>>> correcting to MAX >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>>> correcting to MAX >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>>> correcting to MAX >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>>> >>>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>>> Mini PCI Adapter >>>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>>> Stepping- SERR- FastB2B- DisINTx- >>>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>> Latency: 168, Cache Line Size: 32 bytes >>>> Interrupt: pin A routed to IRQ 18 >>>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>>> Capabilities: [44] Power Management version 2 >>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>>> Kernel driver in use: ath9k >>>> Kernel modules: ath9k >>>> >>>> The last time I saw this on a device that I could debug with, I saw >>>> the following in the log just before it entered this state: >>>> >>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>>> results available >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>>> SCAN_RESULTS (3) received >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>>> 00:17:59:2c:c3:20 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>>> results (45 BSSes) >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>>> result notification >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>>> from priority group 0 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>>> caps=0xc31 level=-56 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>>> other virtual interfaces sharing same radio (phy1) in >>>> event_scan_results >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>>> IFLA_IFNAME: Interface 'wlan0' added >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>>> already cleared - ignore event >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>> reset status -5 >>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>>> 00:17:59:2c:c3:20 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>>> 14 00 17 59 2c c3 20 00 00 04 00 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>>> notification >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>>> (locally generated) >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>>> 00:17:59:2c:c3:20 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>>> IE(s) - hexdump(len=0): [NULL] >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>>> locally_generated=1 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>>> enabled: try to reconnect (wps=0 wpa_state=9) >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>>> request: 0 sec 100000 usec >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>>> 00:17:59:2c:c3:20 into blacklist >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>>> this ESS has been seen; try it next >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>>> blacklist count incremented to 2 >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>>> scan to ensure that specific SSID scans occur >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>>> - remove keys >>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>>> set_tx=0 seq_len=0 key_len=0 >>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>>> (goes into associate timeout loop) >>>> >>>> Please let me know if you need any additional information or testing >>>> done. Thanks. >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >> -- >> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >> the body of a message to majordomo@vger.kernel.org >> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-06 2:51 ` Robert Shade @ 2013-02-06 3:08 ` Adrian Chadd 2013-02-06 12:53 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-02-06 3:08 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel Try bumping that up to 10ms. adrian On 5 February 2013 18:51, Robert Shade <robert.shade@gmail.com> wrote: > I was finally able to do some additional testing on this. I disabled > the one and only block that calls ath9k_hw_do_fastcc. The issue is > still reproducible[1], starting with a timeout on AR_PHY_AGC_CONTROL > > kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & > 0x00000001 != 0x00000000 > kernel: ath: phy1: offset calibration failed to complete in 1ms; noisy > environment? > kernel: ath: phy1: Unable to reset channel, reset status -5 > kernel: ath: phy1: Unable to set channel > > It fails to change channel a number of times as it tries to scan, then > auth. After it gives up on the auth it goes through a AWAKE -> > FULL-SLEEP, FULL-SLEEP -> AWAKE, AWAKE -> FULL-SLEEP, FULL-SLEEP -> > AWAKE cycle. Afterward, it's able to change channel to the channel > the SSID is on and xmit the auth requests, however by that time it's > too late. > > It continues to scan and re-auth, however the auth packets are not > sent until it gives up and goes through another AWAKE/FULL-SLEEP cycle > after the auth times out. > > The radio seems to actually be transmitting because I see the SSID > probe requests going out and I see my non-broadcasted SSID in the scan > logs. > > [1] It happens randomly on my devices in the field, but I'm able to > make it happen pretty quickly if I start a flood ping to my wireless > gw and do continuous scans with iw. > > On Wed, Jan 16, 2013 at 10:12 PM, Adrian Chadd <adrian@freebsd.org> wrote: >> Find where the fast channel change code is (maybe) called, and just >> disable it so it always calls the full channel change? >> >> >> >> Adrian >> >> >> On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: >>> I was able to grab a log with debugging on when the issue started all >>> the way to when it started timing out association due to TX delay: >>> https://dl.dropbox.com/u/12121487/delay-messages.gz >>> >>> On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >>>> fast channel change. >>>> >>>> Maybe ath9k's fast channel change code isn't working right, and it's >>>> not trying a full channel change afterwards? >>>> >>>> >>>> >>>> Adrian >>>> >>>> >>>> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>>>> I'm seeing a periodic issue where the device seems to get stuck in a >>>>> state where the TX of authentication packets is delayed so that >>>>> authentication fails. The log snippet below shows the auth packets >>>>> getting queued after each "wlan0: send auth to XX", but they're not >>>>> actually sent until after it gives up and restarts scanning. Once the >>>>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>>>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>>>> down, the device usually recovers and works correctly for a few minutes to >>>>> hours. >>>>> >>>>> This is with the latest compat-drivers. The authentication is EAP-TLS >>>>> and it's in an environment where it periodically roams using >>>>> wpa_supplicant's bgscan. >>>>> >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>> 0x10f eol 0x10f urn 0x0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>> 0x10f eol 0x10f urn 0x0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>> 0x10f eol 0x10f urn 0x0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>> 0x10f eol 0x10f urn 0x0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>> 0x10f eol 0x10f urn 0x0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>> 0x10f eol 0x10f urn 0x0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>>>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>>>> rssi=67[lo=7 hi=40] >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>> 2=>6[def:2] firstep[level]=10 ini=2 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>>>> rssi=67[lo=7 hi=40] >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>>>> associated..skipping beacon config >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>>>> for a station interface >>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>> ffff880137846a80 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>> supplicant interface state: scanning -> authenticating >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>>>> ifi_flags=0x1003 ([UP]) >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>>>> already cleared - ignore event >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>>>> 00:24:6c:74:0a:40 >>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>> ffff8801265cc2c0 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>> (ffff8800378480c8)=37847568 (ffff880037847568) >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>> ffff8801261aac80 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>>>> 00:24:6c:74:0a:40 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>>>> timeout with 00:24:6c:74:0a:40 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>>>> AUTH_TIMED_OUT (14) received >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>>>> Authentication timed out >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>>>> 00:24:6c:74:0a:40 into blacklist >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>>>> this ESS has been seen; try it next >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>>>> blacklist count incremented to 2 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>>>> request: 0 sec 100000 usec >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>> AUTHENTICATING -> DISCONNECTED >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>>>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>>>> linkmode=-1, operstate=5 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>> notification - portEnabled=0 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>> status: Unauthorized >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>> notification - portValid=0 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>> status: Unauthorized >>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>>>> 00:24:6c:74:0a:40 timed out >>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>> supplicant interface state: authenticating -> disconnected >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>> DISCONNECTED -> SCANNING >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>>>> for wildcard SSID >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>>>> correcting to MAX >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>>>> correcting to MAX >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>>>> correcting to MAX >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>>>> >>>>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>>>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>>>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>>>> Mini PCI Adapter >>>>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>>>> Stepping- SERR- FastB2B- DisINTx- >>>>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>>>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>> Latency: 168, Cache Line Size: 32 bytes >>>>> Interrupt: pin A routed to IRQ 18 >>>>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>>>> Capabilities: [44] Power Management version 2 >>>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>>>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>>>> Kernel driver in use: ath9k >>>>> Kernel modules: ath9k >>>>> >>>>> The last time I saw this on a device that I could debug with, I saw >>>>> the following in the log just before it entered this state: >>>>> >>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>>>> results available >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>>>> SCAN_RESULTS (3) received >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>>>> 00:17:59:2c:c3:20 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>>>> results (45 BSSes) >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>>>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>>>> result notification >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>>>> from priority group 0 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>>>> caps=0xc31 level=-56 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>>>> other virtual interfaces sharing same radio (phy1) in >>>>> event_scan_results >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>>>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>>>> already cleared - ignore event >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>> reset status -5 >>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>>>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>>>> 00:17:59:2c:c3:20 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>>>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>>>> 14 00 17 59 2c c3 20 00 00 04 00 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>>>> notification >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>>>> (locally generated) >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>>>> 00:17:59:2c:c3:20 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>>>> IE(s) - hexdump(len=0): [NULL] >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>>>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>>>> locally_generated=1 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>>>> enabled: try to reconnect (wps=0 wpa_state=9) >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>>>> request: 0 sec 100000 usec >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>>>> 00:17:59:2c:c3:20 into blacklist >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>>>> this ESS has been seen; try it next >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>>>> blacklist count incremented to 2 >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>>>> scan to ensure that specific SSID scans occur >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>>>> - remove keys >>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>>>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>>>> set_tx=0 seq_len=0 key_len=0 >>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>>>> (goes into associate timeout loop) >>>>> >>>>> Please let me know if you need any additional information or testing >>>>> done. Thanks. >>>>> -- >>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>> the body of a message to majordomo@vger.kernel.org >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>> -- >>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>> the body of a message to majordomo@vger.kernel.org >>> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-06 3:08 ` Adrian Chadd @ 2013-02-06 12:53 ` Robert Shade 2013-02-06 22:58 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-02-06 12:53 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel The "1ms" in the message is hard coded. The actual timeout on the register poll is 100ms. On Tue, Feb 5, 2013 at 10:08 PM, Adrian Chadd <adrian@freebsd.org> wrote: > Try bumping that up to 10ms. > > > > adrian > > On 5 February 2013 18:51, Robert Shade <robert.shade@gmail.com> wrote: >> I was finally able to do some additional testing on this. I disabled >> the one and only block that calls ath9k_hw_do_fastcc. The issue is >> still reproducible[1], starting with a timeout on AR_PHY_AGC_CONTROL >> >> kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & >> 0x00000001 != 0x00000000 >> kernel: ath: phy1: offset calibration failed to complete in 1ms; noisy >> environment? >> kernel: ath: phy1: Unable to reset channel, reset status -5 >> kernel: ath: phy1: Unable to set channel >> >> It fails to change channel a number of times as it tries to scan, then >> auth. After it gives up on the auth it goes through a AWAKE -> >> FULL-SLEEP, FULL-SLEEP -> AWAKE, AWAKE -> FULL-SLEEP, FULL-SLEEP -> >> AWAKE cycle. Afterward, it's able to change channel to the channel >> the SSID is on and xmit the auth requests, however by that time it's >> too late. >> >> It continues to scan and re-auth, however the auth packets are not >> sent until it gives up and goes through another AWAKE/FULL-SLEEP cycle >> after the auth times out. >> >> The radio seems to actually be transmitting because I see the SSID >> probe requests going out and I see my non-broadcasted SSID in the scan >> logs. >> >> [1] It happens randomly on my devices in the field, but I'm able to >> make it happen pretty quickly if I start a flood ping to my wireless >> gw and do continuous scans with iw. >> >> On Wed, Jan 16, 2013 at 10:12 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>> Find where the fast channel change code is (maybe) called, and just >>> disable it so it always calls the full channel change? >>> >>> >>> >>> Adrian >>> >>> >>> On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: >>>> I was able to grab a log with debugging on when the issue started all >>>> the way to when it started timing out association due to TX delay: >>>> https://dl.dropbox.com/u/12121487/delay-messages.gz >>>> >>>> On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>>> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >>>>> fast channel change. >>>>> >>>>> Maybe ath9k's fast channel change code isn't working right, and it's >>>>> not trying a full channel change afterwards? >>>>> >>>>> >>>>> >>>>> Adrian >>>>> >>>>> >>>>> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>>>>> I'm seeing a periodic issue where the device seems to get stuck in a >>>>>> state where the TX of authentication packets is delayed so that >>>>>> authentication fails. The log snippet below shows the auth packets >>>>>> getting queued after each "wlan0: send auth to XX", but they're not >>>>>> actually sent until after it gives up and restarts scanning. Once the >>>>>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>>>>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>>>>> down, the device usually recovers and works correctly for a few minutes to >>>>>> hours. >>>>>> >>>>>> This is with the latest compat-drivers. The authentication is EAP-TLS >>>>>> and it's in an environment where it periodically roams using >>>>>> wpa_supplicant's bgscan. >>>>>> >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>> 0x10f eol 0x10f urn 0x0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>> 0x10f eol 0x10f urn 0x0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>> 0x10f eol 0x10f urn 0x0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>> 0x10f eol 0x10f urn 0x0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>> 0x10f eol 0x10f urn 0x0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>> 0x10f eol 0x10f urn 0x0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>>>>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>>>>> rssi=67[lo=7 hi=40] >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>> 2=>6[def:2] firstep[level]=10 ini=2 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>>>>> rssi=67[lo=7 hi=40] >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>>>>> associated..skipping beacon config >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>>>>> for a station interface >>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>> ffff880137846a80 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>> supplicant interface state: scanning -> authenticating >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>>>>> ifi_flags=0x1003 ([UP]) >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>>>>> already cleared - ignore event >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>>>>> 00:24:6c:74:0a:40 >>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>> ffff8801265cc2c0 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>> (ffff8800378480c8)=37847568 (ffff880037847568) >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>> ffff8801261aac80 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>>>>> 00:24:6c:74:0a:40 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>>>>> timeout with 00:24:6c:74:0a:40 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>>>>> AUTH_TIMED_OUT (14) received >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>>>>> Authentication timed out >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>>>>> 00:24:6c:74:0a:40 into blacklist >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>>>>> this ESS has been seen; try it next >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>>>>> blacklist count incremented to 2 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>>>>> request: 0 sec 100000 usec >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>> AUTHENTICATING -> DISCONNECTED >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>>>>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>>>>> linkmode=-1, operstate=5 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>> notification - portEnabled=0 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>> status: Unauthorized >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>> notification - portValid=0 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>> status: Unauthorized >>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>>>>> 00:24:6c:74:0a:40 timed out >>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>> supplicant interface state: authenticating -> disconnected >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>> DISCONNECTED -> SCANNING >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>>>>> for wildcard SSID >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>>>>> correcting to MAX >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>>>>> correcting to MAX >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>>>>> correcting to MAX >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>>>>> >>>>>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>>>>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>>>>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>>>>> Mini PCI Adapter >>>>>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>>>>> Stepping- SERR- FastB2B- DisINTx- >>>>>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>>>>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>> Latency: 168, Cache Line Size: 32 bytes >>>>>> Interrupt: pin A routed to IRQ 18 >>>>>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>>>>> Capabilities: [44] Power Management version 2 >>>>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>>>>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>>>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>>>>> Kernel driver in use: ath9k >>>>>> Kernel modules: ath9k >>>>>> >>>>>> The last time I saw this on a device that I could debug with, I saw >>>>>> the following in the log just before it entered this state: >>>>>> >>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>>>>> results available >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>>>>> SCAN_RESULTS (3) received >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>>>>> 00:17:59:2c:c3:20 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>>>>> results (45 BSSes) >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>>>>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>>>>> result notification >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>>>>> from priority group 0 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>>>>> caps=0xc31 level=-56 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>>>>> other virtual interfaces sharing same radio (phy1) in >>>>>> event_scan_results >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>>>>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>>>>> already cleared - ignore event >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>> reset status -5 >>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>>>>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>>>>> 00:17:59:2c:c3:20 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>>>>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>>>>> 14 00 17 59 2c c3 20 00 00 04 00 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>>>>> notification >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>>>>> (locally generated) >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>>>>> 00:17:59:2c:c3:20 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>>>>> IE(s) - hexdump(len=0): [NULL] >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>>>>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>>>>> locally_generated=1 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>>>>> enabled: try to reconnect (wps=0 wpa_state=9) >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>>>>> request: 0 sec 100000 usec >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>>>>> 00:17:59:2c:c3:20 into blacklist >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>>>>> this ESS has been seen; try it next >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>>>>> blacklist count incremented to 2 >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>>>>> scan to ensure that specific SSID scans occur >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>>>>> - remove keys >>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>>>>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>>>>> set_tx=0 seq_len=0 key_len=0 >>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>>>>> (goes into associate timeout loop) >>>>>> >>>>>> Please let me know if you need any additional information or testing >>>>>> done. Thanks. >>>>>> -- >>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>> the body of a message to majordomo@vger.kernel.org >>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>> -- >>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>> the body of a message to majordomo@vger.kernel.org >>>> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-06 12:53 ` Robert Shade @ 2013-02-06 22:58 ` Robert Shade 2013-02-07 5:06 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-02-06 22:58 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel I tested this all the way up to 1s and am still able to replicate the timeout. Out of curiosity I collected how long the calibration usually takes: avg 825.829us, min 620us, max 830us (16k+ samples) On Wed, Feb 6, 2013 at 7:53 AM, Robert Shade <robert.shade@gmail.com> wrote: > The "1ms" in the message is hard coded. The actual timeout on the > register poll is 100ms. > > On Tue, Feb 5, 2013 at 10:08 PM, Adrian Chadd <adrian@freebsd.org> wrote: >> Try bumping that up to 10ms. >> >> >> >> adrian >> >> On 5 February 2013 18:51, Robert Shade <robert.shade@gmail.com> wrote: >>> I was finally able to do some additional testing on this. I disabled >>> the one and only block that calls ath9k_hw_do_fastcc. The issue is >>> still reproducible[1], starting with a timeout on AR_PHY_AGC_CONTROL >>> >>> kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & >>> 0x00000001 != 0x00000000 >>> kernel: ath: phy1: offset calibration failed to complete in 1ms; noisy >>> environment? >>> kernel: ath: phy1: Unable to reset channel, reset status -5 >>> kernel: ath: phy1: Unable to set channel >>> >>> It fails to change channel a number of times as it tries to scan, then >>> auth. After it gives up on the auth it goes through a AWAKE -> >>> FULL-SLEEP, FULL-SLEEP -> AWAKE, AWAKE -> FULL-SLEEP, FULL-SLEEP -> >>> AWAKE cycle. Afterward, it's able to change channel to the channel >>> the SSID is on and xmit the auth requests, however by that time it's >>> too late. >>> >>> It continues to scan and re-auth, however the auth packets are not >>> sent until it gives up and goes through another AWAKE/FULL-SLEEP cycle >>> after the auth times out. >>> >>> The radio seems to actually be transmitting because I see the SSID >>> probe requests going out and I see my non-broadcasted SSID in the scan >>> logs. >>> >>> [1] It happens randomly on my devices in the field, but I'm able to >>> make it happen pretty quickly if I start a flood ping to my wireless >>> gw and do continuous scans with iw. >>> >>> On Wed, Jan 16, 2013 at 10:12 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>> Find where the fast channel change code is (maybe) called, and just >>>> disable it so it always calls the full channel change? >>>> >>>> >>>> >>>> Adrian >>>> >>>> >>>> On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: >>>>> I was able to grab a log with debugging on when the issue started all >>>>> the way to when it started timing out association due to TX delay: >>>>> https://dl.dropbox.com/u/12121487/delay-messages.gz >>>>> >>>>> On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>>>> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >>>>>> fast channel change. >>>>>> >>>>>> Maybe ath9k's fast channel change code isn't working right, and it's >>>>>> not trying a full channel change afterwards? >>>>>> >>>>>> >>>>>> >>>>>> Adrian >>>>>> >>>>>> >>>>>> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>>>>>> I'm seeing a periodic issue where the device seems to get stuck in a >>>>>>> state where the TX of authentication packets is delayed so that >>>>>>> authentication fails. The log snippet below shows the auth packets >>>>>>> getting queued after each "wlan0: send auth to XX", but they're not >>>>>>> actually sent until after it gives up and restarts scanning. Once the >>>>>>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>>>>>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>>>>>> down, the device usually recovers and works correctly for a few minutes to >>>>>>> hours. >>>>>>> >>>>>>> This is with the latest compat-drivers. The authentication is EAP-TLS >>>>>>> and it's in an environment where it periodically roams using >>>>>>> wpa_supplicant's bgscan. >>>>>>> >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>>>>>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>>>>>> rssi=67[lo=7 hi=40] >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>> 2=>6[def:2] firstep[level]=10 ini=2 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>>>>>> rssi=67[lo=7 hi=40] >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>>>>>> associated..skipping beacon config >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>>>>>> for a station interface >>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>> ffff880137846a80 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>>> supplicant interface state: scanning -> authenticating >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>>>>>> ifi_flags=0x1003 ([UP]) >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>>>>>> already cleared - ignore event >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>>>>>> 00:24:6c:74:0a:40 >>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>> ffff8801265cc2c0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>>> (ffff8800378480c8)=37847568 (ffff880037847568) >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>> ffff8801261aac80 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>>>>>> 00:24:6c:74:0a:40 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>>>>>> timeout with 00:24:6c:74:0a:40 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>>>>>> AUTH_TIMED_OUT (14) received >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>>>>>> Authentication timed out >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>>>>>> 00:24:6c:74:0a:40 into blacklist >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>>>>>> this ESS has been seen; try it next >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>>>>>> blacklist count incremented to 2 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>>>>>> request: 0 sec 100000 usec >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>>> AUTHENTICATING -> DISCONNECTED >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>>>>>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>>>>>> linkmode=-1, operstate=5 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>>> notification - portEnabled=0 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>>> status: Unauthorized >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>>> notification - portValid=0 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>>> status: Unauthorized >>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>>>>>> 00:24:6c:74:0a:40 timed out >>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>>> supplicant interface state: authenticating -> disconnected >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>>> DISCONNECTED -> SCANNING >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>>>>>> for wildcard SSID >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>>>>>> correcting to MAX >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>>>>>> correcting to MAX >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>>>>>> correcting to MAX >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>>>>>> >>>>>>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>>>>>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>>>>>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>>>>>> Mini PCI Adapter >>>>>>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>>>>>> Stepping- SERR- FastB2B- DisINTx- >>>>>>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>>>>>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>> Latency: 168, Cache Line Size: 32 bytes >>>>>>> Interrupt: pin A routed to IRQ 18 >>>>>>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>>>>>> Capabilities: [44] Power Management version 2 >>>>>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>>>>>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>>>>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>>>>>> Kernel driver in use: ath9k >>>>>>> Kernel modules: ath9k >>>>>>> >>>>>>> The last time I saw this on a device that I could debug with, I saw >>>>>>> the following in the log just before it entered this state: >>>>>>> >>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>>>>>> results available >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>>>>>> SCAN_RESULTS (3) received >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>>>>>> 00:17:59:2c:c3:20 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>>>>>> results (45 BSSes) >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>>>>>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>>>>>> result notification >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>>>>>> from priority group 0 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>>>>>> caps=0xc31 level=-56 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>>>>>> other virtual interfaces sharing same radio (phy1) in >>>>>>> event_scan_results >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>>>>>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>>>>>> already cleared - ignore event >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>> reset status -5 >>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>>>>>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>>>>>> 00:17:59:2c:c3:20 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>>>>>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>>>>>> 14 00 17 59 2c c3 20 00 00 04 00 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>>>>>> notification >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>>>>>> (locally generated) >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>>>>>> 00:17:59:2c:c3:20 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>>>>>> IE(s) - hexdump(len=0): [NULL] >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>>>>>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>>>>>> locally_generated=1 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>>>>>> enabled: try to reconnect (wps=0 wpa_state=9) >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>>>>>> request: 0 sec 100000 usec >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>>>>>> 00:17:59:2c:c3:20 into blacklist >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>>>>>> this ESS has been seen; try it next >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>>>>>> blacklist count incremented to 2 >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>>>>>> scan to ensure that specific SSID scans occur >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>>>>>> - remove keys >>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>>>>>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>>>>>> set_tx=0 seq_len=0 key_len=0 >>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>>>>>> (goes into associate timeout loop) >>>>>>> >>>>>>> Please let me know if you need any additional information or testing >>>>>>> done. Thanks. >>>>>>> -- >>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>>> the body of a message to majordomo@vger.kernel.org >>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>> -- >>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>> the body of a message to majordomo@vger.kernel.org >>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-06 22:58 ` Robert Shade @ 2013-02-07 5:06 ` Adrian Chadd 2013-02-07 16:25 ` [ath9k-devel] " David Littell 2013-02-07 19:43 ` Robert Shade 0 siblings, 2 replies; 36+ messages in thread From: Adrian Chadd @ 2013-02-07 5:06 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel Okay. Then the radio is truely confused. :-( Which chipset is this again? Adrian On 6 February 2013 14:58, Robert Shade <robert.shade@gmail.com> wrote: > I tested this all the way up to 1s and am still able to replicate the timeout. > > Out of curiosity I collected how long the calibration usually takes: > avg 825.829us, min 620us, max 830us (16k+ samples) > > On Wed, Feb 6, 2013 at 7:53 AM, Robert Shade <robert.shade@gmail.com> wrote: >> The "1ms" in the message is hard coded. The actual timeout on the >> register poll is 100ms. >> >> On Tue, Feb 5, 2013 at 10:08 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>> Try bumping that up to 10ms. >>> >>> >>> >>> adrian >>> >>> On 5 February 2013 18:51, Robert Shade <robert.shade@gmail.com> wrote: >>>> I was finally able to do some additional testing on this. I disabled >>>> the one and only block that calls ath9k_hw_do_fastcc. The issue is >>>> still reproducible[1], starting with a timeout on AR_PHY_AGC_CONTROL >>>> >>>> kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & >>>> 0x00000001 != 0x00000000 >>>> kernel: ath: phy1: offset calibration failed to complete in 1ms; noisy >>>> environment? >>>> kernel: ath: phy1: Unable to reset channel, reset status -5 >>>> kernel: ath: phy1: Unable to set channel >>>> >>>> It fails to change channel a number of times as it tries to scan, then >>>> auth. After it gives up on the auth it goes through a AWAKE -> >>>> FULL-SLEEP, FULL-SLEEP -> AWAKE, AWAKE -> FULL-SLEEP, FULL-SLEEP -> >>>> AWAKE cycle. Afterward, it's able to change channel to the channel >>>> the SSID is on and xmit the auth requests, however by that time it's >>>> too late. >>>> >>>> It continues to scan and re-auth, however the auth packets are not >>>> sent until it gives up and goes through another AWAKE/FULL-SLEEP cycle >>>> after the auth times out. >>>> >>>> The radio seems to actually be transmitting because I see the SSID >>>> probe requests going out and I see my non-broadcasted SSID in the scan >>>> logs. >>>> >>>> [1] It happens randomly on my devices in the field, but I'm able to >>>> make it happen pretty quickly if I start a flood ping to my wireless >>>> gw and do continuous scans with iw. >>>> >>>> On Wed, Jan 16, 2013 at 10:12 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>>> Find where the fast channel change code is (maybe) called, and just >>>>> disable it so it always calls the full channel change? >>>>> >>>>> >>>>> >>>>> Adrian >>>>> >>>>> >>>>> On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: >>>>>> I was able to grab a log with debugging on when the issue started all >>>>>> the way to when it started timing out association due to TX delay: >>>>>> https://dl.dropbox.com/u/12121487/delay-messages.gz >>>>>> >>>>>> On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>>>>> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >>>>>>> fast channel change. >>>>>>> >>>>>>> Maybe ath9k's fast channel change code isn't working right, and it's >>>>>>> not trying a full channel change afterwards? >>>>>>> >>>>>>> >>>>>>> >>>>>>> Adrian >>>>>>> >>>>>>> >>>>>>> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>>>>>>> I'm seeing a periodic issue where the device seems to get stuck in a >>>>>>>> state where the TX of authentication packets is delayed so that >>>>>>>> authentication fails. The log snippet below shows the auth packets >>>>>>>> getting queued after each "wlan0: send auth to XX", but they're not >>>>>>>> actually sent until after it gives up and restarts scanning. Once the >>>>>>>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>>>>>>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>>>>>>> down, the device usually recovers and works correctly for a few minutes to >>>>>>>> hours. >>>>>>>> >>>>>>>> This is with the latest compat-drivers. The authentication is EAP-TLS >>>>>>>> and it's in an environment where it periodically roams using >>>>>>>> wpa_supplicant's bgscan. >>>>>>>> >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>>>>>>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>>>>>>> rssi=67[lo=7 hi=40] >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>> 2=>6[def:2] firstep[level]=10 ini=2 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>>>>>>> rssi=67[lo=7 hi=40] >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>>>>>>> associated..skipping beacon config >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>>>>>>> for a station interface >>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>>> ffff880137846a80 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>>>> supplicant interface state: scanning -> authenticating >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>>>>>>> ifi_flags=0x1003 ([UP]) >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>>>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>>>>>>> already cleared - ignore event >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>>>>>>> 00:24:6c:74:0a:40 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>>> ffff8801265cc2c0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>>>> (ffff8800378480c8)=37847568 (ffff880037847568) >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>>> ffff8801261aac80 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>>>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>>>>>>> 00:24:6c:74:0a:40 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>>>>>>> timeout with 00:24:6c:74:0a:40 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>>>>>>> AUTH_TIMED_OUT (14) received >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>>>>>>> Authentication timed out >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>>>>>>> 00:24:6c:74:0a:40 into blacklist >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>>>>>>> this ESS has been seen; try it next >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>>>>>>> blacklist count incremented to 2 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>>>>>>> request: 0 sec 100000 usec >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>>>> AUTHENTICATING -> DISCONNECTED >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>>>>>>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>>>>>>> linkmode=-1, operstate=5 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>>>> notification - portEnabled=0 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>>>> status: Unauthorized >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>>>> notification - portValid=0 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>>>> status: Unauthorized >>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>>>>>>> 00:24:6c:74:0a:40 timed out >>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>>>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>>>> supplicant interface state: authenticating -> disconnected >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>>>> DISCONNECTED -> SCANNING >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>>>>>>> for wildcard SSID >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>>>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>>>>>>> correcting to MAX >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>>>>>>> correcting to MAX >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>>>>>>> correcting to MAX >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>>>>>>> >>>>>>>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>>>>>>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>>>>>>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>>>>>>> Mini PCI Adapter >>>>>>>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>>>>>>> Stepping- SERR- FastB2B- DisINTx- >>>>>>>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>>>>>>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>>> Latency: 168, Cache Line Size: 32 bytes >>>>>>>> Interrupt: pin A routed to IRQ 18 >>>>>>>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>>>>>>> Capabilities: [44] Power Management version 2 >>>>>>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>>>>>>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>>>>>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>>>>>>> Kernel driver in use: ath9k >>>>>>>> Kernel modules: ath9k >>>>>>>> >>>>>>>> The last time I saw this on a device that I could debug with, I saw >>>>>>>> the following in the log just before it entered this state: >>>>>>>> >>>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>>>>>>> results available >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>>>>>>> SCAN_RESULTS (3) received >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>>>>>>> 00:17:59:2c:c3:20 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>>>>>>> results (45 BSSes) >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>>>>>>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>>>>>>> result notification >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>>>>>>> from priority group 0 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>>>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>>>>>>> caps=0xc31 level=-56 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>>>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>>>>>>> other virtual interfaces sharing same radio (phy1) in >>>>>>>> event_scan_results >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>>>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>>>>>>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>>>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>>>>>>> already cleared - ignore event >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>> reset status -5 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>>>>>>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>>>>>>> 00:17:59:2c:c3:20 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>>>>>>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>>>>>>> 14 00 17 59 2c c3 20 00 00 04 00 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>>>>>>> notification >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>>>>>>> (locally generated) >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>>>>>>> 00:17:59:2c:c3:20 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>>>>>>> IE(s) - hexdump(len=0): [NULL] >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>>>>>>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>>>>>>> locally_generated=1 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>>>>>>> enabled: try to reconnect (wps=0 wpa_state=9) >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>>>>>>> request: 0 sec 100000 usec >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>>>>>>> 00:17:59:2c:c3:20 into blacklist >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>>>>>>> this ESS has been seen; try it next >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>>>>>>> blacklist count incremented to 2 >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>>>>>>> scan to ensure that specific SSID scans occur >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>>>>>>> - remove keys >>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>>>>>>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>>>>>>> set_tx=0 seq_len=0 key_len=0 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>>>>>>> (goes into associate timeout loop) >>>>>>>> >>>>>>>> Please let me know if you need any additional information or testing >>>>>>>> done. Thanks. >>>>>>>> -- >>>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>>>> the body of a message to majordomo@vger.kernel.org >>>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>>> -- >>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>> the body of a message to majordomo@vger.kernel.org >>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* RE: [ath9k-devel] Auth Packet TX Delay 2013-02-07 5:06 ` Adrian Chadd @ 2013-02-07 16:25 ` David Littell 2013-02-07 19:43 ` Robert Shade 1 sibling, 0 replies; 36+ messages in thread From: David Littell @ 2013-02-07 16:25 UTC (permalink / raw) To: ath9k-devel, linux-wireless > -----Original Message----- > From: ath9k-devel-bounces@lists.ath9k.org [mailto:ath9k-devel- > bounces@lists.ath9k.org] On Behalf Of Adrian Chadd > Sent: Wednesday, February 06, 2013 11:06 PM > To: Robert Shade > Cc: ath9k-devel@lists.ath9k.org; linux-wireless@vger.kernel.org > Subject: Re: [ath9k-devel] Auth Packet TX Delay > > Okay. Then the radio is truely confused. :-( > > Which chipset is this again? > > I'm getting similar behavior using hostapd and an AR5BHB116. The driver identifies this as an AR9300 but I've seen "AR9382" associated with "AR5BHB116" online. (The PCI ID is 168c:0030, for what it's worth.) Thanks, Dave This message is confidential to Prodea Systems, Inc unless otherwise indicated or apparent from its nature. This message is directed to the intended recipient only, who may be readily determined by the sender of this message and its contents. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient:(a)any dissemination or copying of this message is strictly prohibited; and(b)immediately notify the sender by return message and destroy any copies of this message in any form(electronic, paper or otherwise) that you have.The delivery of this message and its information is neither intended to be nor constitutes a disclosure or waiver of any trade secrets, intellectual property, attorney work product, or attorney-client communications. The authority of the individual sending this message to legally bind Prodea Systems is neither apparent nor implied,and must be independently verified. ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-07 5:06 ` Adrian Chadd 2013-02-07 16:25 ` [ath9k-devel] " David Littell @ 2013-02-07 19:43 ` Robert Shade 2013-02-07 21:40 ` Adrian Chadd 1 sibling, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-02-07 19:43 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel AR9160 / AR9106 On Thu, Feb 7, 2013 at 12:06 AM, Adrian Chadd <adrian@freebsd.org> wrote: > Okay. Then the radio is truely confused. :-( > > Which chipset is this again? > > > > Adrian > > > On 6 February 2013 14:58, Robert Shade <robert.shade@gmail.com> wrote: >> I tested this all the way up to 1s and am still able to replicate the timeout. >> >> Out of curiosity I collected how long the calibration usually takes: >> avg 825.829us, min 620us, max 830us (16k+ samples) >> >> On Wed, Feb 6, 2013 at 7:53 AM, Robert Shade <robert.shade@gmail.com> wrote: >>> The "1ms" in the message is hard coded. The actual timeout on the >>> register poll is 100ms. >>> >>> On Tue, Feb 5, 2013 at 10:08 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>> Try bumping that up to 10ms. >>>> >>>> >>>> >>>> adrian >>>> >>>> On 5 February 2013 18:51, Robert Shade <robert.shade@gmail.com> wrote: >>>>> I was finally able to do some additional testing on this. I disabled >>>>> the one and only block that calls ath9k_hw_do_fastcc. The issue is >>>>> still reproducible[1], starting with a timeout on AR_PHY_AGC_CONTROL >>>>> >>>>> kernel: ath: phy1: timeout (100000 us) on reg 0x9860: 0x00048d21 & >>>>> 0x00000001 != 0x00000000 >>>>> kernel: ath: phy1: offset calibration failed to complete in 1ms; noisy >>>>> environment? >>>>> kernel: ath: phy1: Unable to reset channel, reset status -5 >>>>> kernel: ath: phy1: Unable to set channel >>>>> >>>>> It fails to change channel a number of times as it tries to scan, then >>>>> auth. After it gives up on the auth it goes through a AWAKE -> >>>>> FULL-SLEEP, FULL-SLEEP -> AWAKE, AWAKE -> FULL-SLEEP, FULL-SLEEP -> >>>>> AWAKE cycle. Afterward, it's able to change channel to the channel >>>>> the SSID is on and xmit the auth requests, however by that time it's >>>>> too late. >>>>> >>>>> It continues to scan and re-auth, however the auth packets are not >>>>> sent until it gives up and goes through another AWAKE/FULL-SLEEP cycle >>>>> after the auth times out. >>>>> >>>>> The radio seems to actually be transmitting because I see the SSID >>>>> probe requests going out and I see my non-broadcasted SSID in the scan >>>>> logs. >>>>> >>>>> [1] It happens randomly on my devices in the field, but I'm able to >>>>> make it happen pretty quickly if I start a flood ping to my wireless >>>>> gw and do continuous scans with iw. >>>>> >>>>> On Wed, Jan 16, 2013 at 10:12 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>>>> Find where the fast channel change code is (maybe) called, and just >>>>>> disable it so it always calls the full channel change? >>>>>> >>>>>> >>>>>> >>>>>> Adrian >>>>>> >>>>>> >>>>>> On 16 January 2013 17:00, Robert Shade <robert.shade@gmail.com> wrote: >>>>>>> I was able to grab a log with debugging on when the issue started all >>>>>>> the way to when it started timing out association due to TX delay: >>>>>>> https://dl.dropbox.com/u/12121487/delay-messages.gz >>>>>>> >>>>>>> On Wed, Jan 16, 2013 at 6:09 PM, Adrian Chadd <adrian@freebsd.org> wrote: >>>>>>>> Hm, that register is AR_PHY_RFBUS_GNT, which iirc is only involved in >>>>>>>> fast channel change. >>>>>>>> >>>>>>>> Maybe ath9k's fast channel change code isn't working right, and it's >>>>>>>> not trying a full channel change afterwards? >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Adrian >>>>>>>> >>>>>>>> >>>>>>>> On 15 January 2013 14:06, Robert Shade <robert.shade@gmail.com> wrote: >>>>>>>>> I'm seeing a periodic issue where the device seems to get stuck in a >>>>>>>>> state where the TX of authentication packets is delayed so that >>>>>>>>> authentication fails. The log snippet below shows the auth packets >>>>>>>>> getting queued after each "wlan0: send auth to XX", but they're not >>>>>>>>> actually sent until after it gives up and restarts scanning. Once the >>>>>>>>> device gets into this state, it stays in a SCAN->AUTH->AUTH >>>>>>>>> FAILED->SCAN cycle indefinitely. However, if I do a ifconfig wlan0 >>>>>>>>> down, the device usually recovers and works correctly for a few minutes to >>>>>>>>> hours. >>>>>>>>> >>>>>>>>> This is with the latest compat-drivers. The authentication is EAP-TLS >>>>>>>>> and it's in an environment where it periodically roams using >>>>>>>>> wpa_supplicant's bgscan. >>>>>>>>> >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 1 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 2 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 3 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 4 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 5 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 6 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TXQ, inactive queue: 7 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 8 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Reset TX queue: 9 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: tx ok 0x0 err 0x0 desc >>>>>>>>> 0x10f eol 0x10f urn 0x0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ver 64.1 opmode 2 chan 2437 Mhz/0xc0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ah->misc_mode 0x4 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC Gain Calibration >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling ADC DC Calibration >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: enabling IQ Calibration >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: starting ADC Gain Calibration >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable MIB counters >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Restore history: opmode 2 >>>>>>>>> chan 2437 Mhz/0xc0 is_scanning=0 ofdm:8 cck:6 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ofdmlevel 8=>8, >>>>>>>>> rssi=67[lo=7 hi=40] >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>>> 3=>7[def:3] cycpwrThr1[level]=14 ini=6 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>>> 3=>7[def:3] cycpwrThr1Ext[level]=14 ini=6 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>>>> ofdmWS=on FS=2 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>>> 2=>6[def:2] firstep[level]=10 ini=2 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: level >>>>>>>>> 2=>6[def:2] firstep_low[level]=14 ini=6 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>>>> ofdmWS=on FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ** ch 2437: ofdm weak signal: on=>off >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: ANI parameters: SI=7, >>>>>>>>> ofdmWS=off FS=6 MRCcck=off listenTime=0 ofdmErrs=0 cckErrs=0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: **** ccklevel 6=>6, >>>>>>>>> rssi=67[lo=7 hi=40] >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: New interrupt mask 0xf4040071 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: new IMR 0x918404b0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Do not enable IER ref count -1 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: STA is not yet >>>>>>>>> associated..skipping beacon config >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Beacon already configured >>>>>>>>> for a station interface >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Inserted STA 00:24:6c:74:0a:40 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 1/3) >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>>>> ffff880137846a80 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: TXDP[0] = 378480c8 (ffff8800378480c8) >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>>>>> supplicant interface state: scanning -> authenticating >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK: operstate=0 >>>>>>>>> ifi_flags=0x1003 ([UP]) >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: RTM_NEWLINK, >>>>>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: if_removed >>>>>>>>> already cleared - ignore event >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: New station >>>>>>>>> 00:24:6c:74:0a:40 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 2/3) >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>>>> ffff8801265cc2c0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 1 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>>>>> (ffff8800378480c8)=37847568 (ffff880037847568) >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: send auth to 00:24:6c:74:0a:40 (try 3/3) >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: transmitting packet, skb: >>>>>>>>> ffff8801261aac80 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: qnum: 0, txq depth: 2 >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: link[0] >>>>>>>>> (ffff880037847568)=378465f8 (ffff8800378465f8) >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: ath: phy0: Enable TXE on queue: 0 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Delete station >>>>>>>>> 00:24:6c:74:0a:40 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Event message available >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: MLME event 37; >>>>>>>>> timeout with 00:24:6c:74:0a:40 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Event >>>>>>>>> AUTH_TIMED_OUT (14) received >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: SME: >>>>>>>>> Authentication timed out >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: Added BSSID >>>>>>>>> 00:24:6c:74:0a:40 into blacklist >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Another BSS in >>>>>>>>> this ESS has been seen; try it next >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: BSSID 00:24:6c:74:0a:40 >>>>>>>>> blacklist count incremented to 2 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Setting scan >>>>>>>>> request: 0 sec 100000 usec >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>>>>> AUTHENTICATING -> DISCONNECTED >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: >>>>>>>>> wpa_driver_nl80211_set_operstate: operstate 0->0 (DORMANT) >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: netlink: Operstate: >>>>>>>>> linkmode=-1, operstate=5 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>>>>> notification - portEnabled=0 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>>>>> status: Unauthorized >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: External >>>>>>>>> notification - portValid=0 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: EAPOL: Supplicant port >>>>>>>>> status: Unauthorized >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: authentication with >>>>>>>>> 00:24:6c:74:0a:40 timed out >>>>>>>>> Nov 20 11:24:33 MR89253 kernel: wlan0: Removed STA 00:24:6c:74:0a:40 >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: dbus: >>>>>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>>>>> Nov 20 11:24:33 MR89253 NetworkManager[1821]: <info> (wlan0): >>>>>>>>> supplicant interface state: authenticating -> disconnected >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: State: >>>>>>>>> DISCONNECTED -> SCANNING >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: wlan0: Starting AP scan >>>>>>>>> for wildcard SSID >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2412 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2417 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2422 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2427 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2432 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2437 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2442 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2447 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2452 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2457 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2462 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2467 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2472 MHz >>>>>>>>> Nov 20 11:24:33 MR89253 wpa_supplicant[1841]: nl80211: Scan frequency 2484 MHz >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: wlan0: Destroyed STA 00:24:6c:74:0a:40 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: AWAKE -> FULL-SLEEP >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: FULL-SLEEP -> AWAKE >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Set channel: 2437 MHz type: 0 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 0] is -50 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[0] (-50) > MAX (-80), >>>>>>>>> correcting to MAX >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 1] is -50 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[1] (-50) > MAX (-80), >>>>>>>>> correcting to MAX >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF calibrated [ctl] [chain 2] is -50 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: NF[2] (-50) > MAX (-80), >>>>>>>>> correcting to MAX >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Stopping ANI >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: disable IER >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: Disable MIB counters >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff880137846a80 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801265cc2c0 >>>>>>>>> Nov 20 11:24:34 MR89253 kernel: ath: phy0: TX complete: skb: ffff8801261aac80 >>>>>>>>> >>>>>>>>> 17:00.0 Network controller: Atheros Communications Inc. AR9160 >>>>>>>>> Wireless Network Adapter [AR9001 802.11(a)bgn] (rev 01) >>>>>>>>> Subsystem: Ubiquiti Networks, Inc. SR71-A 802.11abgn Wireless >>>>>>>>> Mini PCI Adapter >>>>>>>>> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- >>>>>>>>> Stepping- SERR- FastB2B- DisINTx- >>>>>>>>> Status: Cap+ 66MHz+ UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- >>>>>>>>> <TAbort- <MAbort- >SERR- <PERR- INTx- >>>>>>>>> Latency: 168, Cache Line Size: 32 bytes >>>>>>>>> Interrupt: pin A routed to IRQ 18 >>>>>>>>> Region 0: Memory at fd5f0000 (32-bit, non-prefetchable) [size=64K] >>>>>>>>> Capabilities: [44] Power Management version 2 >>>>>>>>> Flags: PMEClk- DSI- D1- D2- AuxCurrent=100mA >>>>>>>>> PME(D0+,D1-,D2-,D3hot+,D3cold-) >>>>>>>>> Status: D0 NoSoftRst- PME-Enable- DSel=0 DScale=0 PME- >>>>>>>>> Kernel driver in use: ath9k >>>>>>>>> Kernel modules: ath9k >>>>>>>>> >>>>>>>>> The last time I saw this on a device that I could debug with, I saw >>>>>>>>> the following in the log just before it entered this state: >>>>>>>>> >>>>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:53 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:54 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:55 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9c20: 0x00000000 & 0x00000001 != 0x00000001 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Could not kill baseband RX >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: New scan >>>>>>>>> results available >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event >>>>>>>>> SCAN_RESULTS (3) received >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated on 2412 MHz >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Associated with >>>>>>>>> 00:17:59:2c:c3:20 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Received scan >>>>>>>>> results (45 BSSes) >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Scan results >>>>>>>>> indicate BSS status with 00:17:59:2c:c3:20 as associated >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: New scan results available >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: bgscan simple: scan >>>>>>>>> result notification >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Selecting BSS >>>>>>>>> from priority group 0 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: 0: >>>>>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' wpa_ie_len=24 rsn_ie_len=0 >>>>>>>>> caps=0xc31 level=-56 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected based on WPA IE >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: selected BSS >>>>>>>>> 00:17:59:2c:c3:20 ssid='l0c0m0t1v3' >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Checking for >>>>>>>>> other virtual interfaces sharing same radio (phy1) in >>>>>>>>> event_scan_results >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: dbus: >>>>>>>>> flush_object_timeout_handler: Timeout - sending changed properties of >>>>>>>>> object /fi/w1/wpa_supplicant1/Interfaces/1 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK: operstate=1 >>>>>>>>> ifi_flags=0x11043 ([UP][RUNNING][LOWER_UP]) >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: RTM_NEWLINK, >>>>>>>>> IFLA_IFNAME: Interface 'wlan0' added >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: if_removed >>>>>>>>> already cleared - ignore event >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: timeout (100000 us) on reg >>>>>>>>> 0x9860: 0x00048d21 & 0x00000001 != 0x00000000 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to reset channel, >>>>>>>>> reset status -5 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: ath: phy1: Unable to set channel >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Failed to send nullfunc to AP >>>>>>>>> 00:17:59:2c:c3:20 after 500ms, disconnecting >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Delete station >>>>>>>>> 00:17:59:2c:c3:20 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Event message available >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event 39 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: MLME event >>>>>>>>> frame - hexdump(len=26): c0 00 00 00 00 17 59 2c c3 20 00 15 6d 84 d7 >>>>>>>>> 14 00 17 59 2c c3 20 00 00 04 00 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: nl80211: Deauthenticate event >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Event DEAUTH (12) received >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Deauthentication >>>>>>>>> notification >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * reason 4 >>>>>>>>> (locally generated) >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: * address >>>>>>>>> 00:17:59:2c:c3:20 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Deauthentication frame >>>>>>>>> IE(s) - hexdump(len=0): [NULL] >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: >>>>>>>>> CTRL-EVENT-DISCONNECTED bssid=00:17:59:2c:c3:20 reason=4 >>>>>>>>> locally_generated=1 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Auto connect >>>>>>>>> enabled: try to reconnect (wps=0 wpa_state=9) >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Setting scan >>>>>>>>> request: 0 sec 100000 usec >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: Added BSSID >>>>>>>>> 00:17:59:2c:c3:20 into blacklist >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Another BSS in >>>>>>>>> this ESS has been seen; try it next >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: BSSID 00:17:59:2c:c3:20 >>>>>>>>> blacklist count incremented to 2 >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Not rescheduling >>>>>>>>> scan to ensure that specific SSID scans occur >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: wlan0: Disconnect event >>>>>>>>> - remove keys >>>>>>>>> Jan 15 16:36:56 MR89251 wpa_supplicant[1964]: >>>>>>>>> wpa_driver_nl80211_set_key: ifindex=13 alg=0 addr=(nil) key_idx=0 >>>>>>>>> set_tx=0 seq_len=0 key_len=0 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 3 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 2 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: moving STA 00:17:59:2c:c3:20 to state 1 >>>>>>>>> Jan 15 16:36:56 MR89251 kernel: wlan0: Removed STA 00:17:59:2c:c3:20 >>>>>>>>> (goes into associate timeout loop) >>>>>>>>> >>>>>>>>> Please let me know if you need any additional information or testing >>>>>>>>> done. Thanks. >>>>>>>>> -- >>>>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>>>>> the body of a message to majordomo@vger.kernel.org >>>>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html >>>>>>> -- >>>>>>> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in >>>>>>> the body of a message to majordomo@vger.kernel.org >>>>>>> More majordomo info at http://vger.kernel.org/majordomo-info.html ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-07 19:43 ` Robert Shade @ 2013-02-07 21:40 ` Adrian Chadd 2013-02-08 18:48 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-02-07 21:40 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel On 7 February 2013 11:43, Robert Shade <robert.shade@gmail.com> wrote: > AR9160 / AR9106 Things are getting into a really odd state if that particular initial calibration isn't finishing... Things I can think of: * There's some kind of noise going on that's angering the PHY (eg a spur); * We should be doing a cold reset instead of a warm reset, upon a channel change; (That fixes some issues I've seen on the AR9280 in some environments); * Bad/incorrectly hooked up antenans. >From a software side, nothing much can be going wrong. as long as the driver isn't doing something stupid like running multiple copies of the reset / setup path on different CPUs/threads, it should be reliable. HTH, Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-07 21:40 ` Adrian Chadd @ 2013-02-08 18:48 ` Robert Shade 2013-02-09 7:39 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-02-08 18:48 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel Maybe I have the terminology wrong, but I thought a cold reset meant toggling the PCI reset line. On Thu, Feb 7, 2013 at 4:40 PM, Adrian Chadd <adrian@freebsd.org> wrote: > On 7 February 2013 11:43, Robert Shade <robert.shade@gmail.com> wrote: >> AR9160 / AR9106 > > Things are getting into a really odd state if that particular initial > calibration isn't finishing... > > Things I can think of: > > * There's some kind of noise going on that's angering the PHY (eg a spur); > * We should be doing a cold reset instead of a warm reset, upon a > channel change; (That fixes some issues I've seen on the AR9280 in > some environments); > * Bad/incorrectly hooked up antenans. > > From a software side, nothing much can be going wrong. as long as the > driver isn't doing something stupid like running multiple copies of > the reset / setup path on different CPUs/threads, it should be > reliable. > > HTH, > > > > Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-08 18:48 ` Robert Shade @ 2013-02-09 7:39 ` Adrian Chadd 2013-03-24 18:55 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-02-09 7:39 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel On 8 February 2013 10:48, Robert Shade <robert.shade@gmail.com> wrote: > Maybe I have the terminology wrong, but I thought a cold reset meant > toggling the PCI reset line. That's a very very cold reset line, that resets the PCI bus glue inside the chip. There's a bunch of different reset lines; most of the device can be reset without resetting the PCI/PCIe host interface. So a "cold" reset here is resetting almost everything inside the chip by pulling down those reset lines and stopping/restarting clocks. Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-02-09 7:39 ` Adrian Chadd @ 2013-03-24 18:55 ` Robert Shade 2013-03-24 21:52 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-03-24 18:55 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel I've done some more testing on this and it looks like the auth packets aren't delayed, they're never sent. The "TX Complete" messages are from the queue being purged before a reset due to channel change. It only gets in this state when it's unable to change the channel due to the timeout on setting the AR_PHY_AGC_CONTROL register. One thing that does look interesting is that, when we fail to change the channel, ath_complete_reset is never called and therefore ieee80211_wake_queues is never called either. Are stop/wake queues calls supposed to be balanced? Felix's "ath9k_hw: improve reset reliability after errors" did help a bit, but I still get the DMA errors periodically and it eventually got into the state where the calibration fails leading to not sending any auth packets. Based on your suggestions, I've been testing a few days with the following patch and I have yet to see any DMA messages or the auth stuck state. I had to check for SC_OP_INVALID because the initial reset in ath9k_start would cause a kernel panic when the system was being initialized from a powered off state. I don't know enough about the internals to know if I should expect that, but I'll need to set up a serial console in order to capture the panic. diff --git a/drivers/net/wireless/ath/ath9k/hw.c b/drivers/net/wireless/ath/ath9k/hw.c index 07e2526..05eebdb 100644 --- a/drivers/net/wireless/ath/ath9k/hw.c +++ b/drivers/net/wireless/ath/ath9k/hw.c @@ -1456,6 +1456,7 @@ static bool ath9k_hw_set_reset_reg(struct ath_hw *ah, u32 type) static bool ath9k_hw_chip_reset(struct ath_hw *ah, struct ath9k_channel *chan) { + struct ath_softc *sc = ah->hw->priv; int reset_type = ATH9K_RESET_WARM; if (AR_SREV_9280(ah)) { @@ -1463,9 +1464,12 @@ static bool ath9k_hw_chip_reset(struct ath_hw *ah, reset_type = ATH9K_RESET_POWER_ON; else reset_type = ATH9K_RESET_COLD; - } else if (ah->chip_fullsleep || REG_READ(ah, AR_Q_TXE) || - (REG_READ(ah, AR_CR) & AR_CR_RXE)) + } else if (AR_SREV_9160(ah) && !test_bit(SC_OP_INVALID, &sc->sc_flags)) { + reset_type = ATH9K_RESET_COLD; + } else if (ah->chip_fullsleep || REG_READ(ah, AR_Q_TXE) || + (REG_READ(ah, AR_CR) & AR_CR_RXE)) { reset_type = ATH9K_RESET_COLD; + } if (!ath9k_hw_set_reset_reg(ah, reset_type)) return false; diff --git a/drivers/net/wireless/ath/ath9k/main.c b/drivers/net/wireless/ath/ath9k/main.c index 6e66f9c..09b4699 100644 --- a/drivers/net/wireless/ath/ath9k/main.c +++ b/drivers/net/wireless/ath/ath9k/main.c @@ -252,7 +252,7 @@ static int ath_reset_internal(struct ath_softc *sc, struct ath9k_channel *hchan) struct ath_hw *ah = sc->sc_ah; struct ath_common *common = ath9k_hw_common(ah); struct ath9k_hw_cal_data *caldata = NULL; - bool fastcc = true; + bool fastcc = !AR_SREV_9160(ah); int r; __ath_cancel_work(sc); -- On Sat, Feb 9, 2013 at 2:39 AM, Adrian Chadd <adrian@freebsd.org> wrote: > > On 8 February 2013 10:48, Robert Shade <robert.shade@gmail.com> wrote: > > Maybe I have the terminology wrong, but I thought a cold reset meant > > toggling the PCI reset line. > > That's a very very cold reset line, that resets the PCI bus glue > inside the chip. > > There's a bunch of different reset lines; most of the device can be > reset without resetting the PCI/PCIe host interface. > > So a "cold" reset here is resetting almost everything inside the chip > by pulling down those reset lines and stopping/restarting clocks. > > > Adrian ^ permalink raw reply related [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-24 18:55 ` Robert Shade @ 2013-03-24 21:52 ` Adrian Chadd 2013-03-24 22:40 ` Robert Shade 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-03-24 21:52 UTC (permalink / raw) To: Robert Shade; +Cc: linux-wireless, ath9k-devel On 24 March 2013 11:55, Robert Shade <robert.shade@gmail.com> wrote: > I've done some more testing on this and it looks like the auth packets > aren't delayed, they're never sent. The "TX Complete" messages are > from the queue being purged before a reset due to channel change. Ew, ok. > It only gets in this state when it's unable to change the channel due > to the timeout on setting the AR_PHY_AGC_CONTROL register. One thing > that does look interesting is that, when we fail to change the > channel, ath_complete_reset is never called and therefore > ieee80211_wake_queues is never called either. Are stop/wake queues > calls supposed to be balanced? I'll leave that up to Felix. > Based on your suggestions, I've been testing a few days with the > following patch and I have yet to see any DMA messages or the auth > stuck state. I had to check for SC_OP_INVALID because the initial > reset in ath9k_start would cause a kernel panic when the system was > being initialized from a powered off state. I don't know enough about > the internals to know if I should expect that, but I'll need to set up > a serial console in order to capture the panic. Hm, so it's doing some fast channel changes? Just disable fast channel change entirely and re-test? And why not just force a cold reset always? Why bother checking for the queue to be stopped? Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-24 21:52 ` Adrian Chadd @ 2013-03-24 22:40 ` Robert Shade 2013-03-24 22:58 ` Christian Lamparter 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-03-24 22:40 UTC (permalink / raw) To: Adrian Chadd; +Cc: linux-wireless, ath9k-devel > Hm, so it's doing some fast channel changes? Yes, the fastcc does seem to work, it's just that sometimes the chip can get in a bad state when it's not cold reset. > Just disable fast channel change entirely and re-test? And why not > just force a cold reset always? Why bother checking for the queue to > be stopped? Just disabling fastcc was not enough, the cold resets are what seemed to have made the difference. I was actually thinking about re-enabling fastcc and testing again. The TXE/RXE checking path is from felix's "ath9k_hw: improve reset reliability after errors" patch. I've just got the exception in there for 9160, since I don't have other hardware to test with. What do the hardware engineers say about warm vs. cold reset? I did notice that your latest ar9300 HAL has a note stating that "Warm reset is optimistic." ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-24 22:40 ` Robert Shade @ 2013-03-24 22:58 ` Christian Lamparter 2013-03-25 0:03 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Christian Lamparter @ 2013-03-24 22:58 UTC (permalink / raw) To: Robert Shade; +Cc: Adrian Chadd, linux-wireless, ath9k-devel, Marco Fonseca (Added Marco and me in the CC - please keep it) On Sunday, March 24, 2013 11:40:27 PM Robert Shade wrote: > > Hm, so it's doing some fast channel changes? > > Yes, the fastcc does seem to work, it's just that sometimes the chip > can get in a bad state when it's not cold reset. > > Just disable fast channel change entirely and re-test? And why not > > just force a cold reset always? Why bother checking for the queue to > > be stopped? > > Just disabling fastcc was not enough, the cold resets are what seemed > to have made the difference. I was actually thinking about > re-enabling fastcc and testing again. > > The TXE/RXE checking path is from felix's "ath9k_hw: improve reset > reliability after errors" patch. I've just got the exception in there > for 9160, since I don't have other hardware to test with. What do the > hardware engineers say about warm vs. cold reset? I did notice that > your latest ar9300 HAL has a note stating that "Warm reset is > optimistic." Marco reported in "carl9170: monitor mode hangs due to channel changes" <http://www.spinics.net/lists/linux-wireless/msg105100.html> that carl9170 would stop receiving frames after some time. I looked a bit closer look and it seems that the fast channel change for AR9170 also seems to be the culprit in this case. (It seems that the AGC_CONTROL register is suddenly (re-)set by something to "0x20" (default is 0x0004dd20) and then everything stops.) Regards, Christian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-24 22:58 ` Christian Lamparter @ 2013-03-25 0:03 ` Adrian Chadd 2013-03-25 2:23 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-03-25 0:03 UTC (permalink / raw) To: Christian Lamparter Cc: Robert Shade, linux-wireless, ath9k-devel, Marco Fonseca Let me just be really clear. Fast channel change is notoriously unreliable and really only fully debugged on some very later chips. The correct thing to do is something like this: * if you meet the fast cc requirements (same channel width, same frequency band, etc) then change channel; * if you fail the initial cal, or you hit some traffic stop condition, or you start failing NF cals - do a cold reset. Now, unless you're doing some kind of very latency sensitive applications (eg doing channel scans whilst in hostap mode) and you debug this very very thoroughly, fast-cc is not guaranteed to work. So I'd just ignore fast channel change in its entirety. Now, warm versus cold reset. Cold reset resets everything. Warm reset apparently doesn't fully reset everything in the MAC/PHY. Although I -thought- the initval arrays would initialise things, apparently there are some things that don't get fully cleared. Hence why I suggest doing a cold reset if things are going a bit awry. Felix's catch was good - if the queues weren't fully stopped, just do a cold reset. But I'd just give up on fast-cc for now. Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-25 0:03 ` Adrian Chadd @ 2013-03-25 2:23 ` Adrian Chadd 2013-03-25 16:12 ` Christian Lamparter 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-03-25 2:23 UTC (permalink / raw) To: Christian Lamparter Cc: Robert Shade, linux-wireless, ath9k-devel, Marco Fonseca Also, would you please make sure you file a bugzilla.kernel.org ticket so this gets tracked? It's good to know that some combination of fast channel change and warm versus cold reset is making things better/worse. And although a cold reset is likely a good thing to _fix_ the problem, it still leaves the underlying DMA/PHY hangs unresolved. But yes, please file a bugzilla ticket so this gets tracked right! Thanks, Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-25 2:23 ` Adrian Chadd @ 2013-03-25 16:12 ` Christian Lamparter 2013-03-25 16:45 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Christian Lamparter @ 2013-03-25 16:12 UTC (permalink / raw) To: Adrian Chadd; +Cc: Robert Shade, linux-wireless, ath9k-devel, Marco Fonseca On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote: > Also, would you please make sure you file a bugzilla.kernel.org ticket > so this gets tracked? > > It's good to know that some combination of fast channel change and > warm versus cold reset is making things better/worse. > > And although a cold reset is likely a good thing to _fix_ the problem, > it still leaves the underlying DMA/PHY hangs unresolved. > > But yes, please file a bugzilla ticket so this gets tracked right! Um, do you want a bugreport for ath9k or carl9170 or for both? Regards, Christian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-25 16:12 ` Christian Lamparter @ 2013-03-25 16:45 ` Adrian Chadd 2013-03-26 12:21 ` Robert Shade 2013-03-26 14:13 ` Marco Fonseca 0 siblings, 2 replies; 36+ messages in thread From: Adrian Chadd @ 2013-03-25 16:45 UTC (permalink / raw) To: Christian Lamparter Cc: Robert Shade, linux-wireless, ath9k-devel, Marco Fonseca One for each please. Adrian On 25 March 2013 09:12, Christian Lamparter <chunkeey@googlemail.com> wrote: > On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote: >> Also, would you please make sure you file a bugzilla.kernel.org ticket >> so this gets tracked? >> >> It's good to know that some combination of fast channel change and >> warm versus cold reset is making things better/worse. >> >> And although a cold reset is likely a good thing to _fix_ the problem, >> it still leaves the underlying DMA/PHY hangs unresolved. >> >> But yes, please file a bugzilla ticket so this gets tracked right! > Um, do you want a bugreport for ath9k or carl9170 or for both? > > Regards, > Christian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-25 16:45 ` Adrian Chadd @ 2013-03-26 12:21 ` Robert Shade 2013-03-26 13:23 ` Robert Shade 2013-03-26 16:28 ` Adrian Chadd 2013-03-26 14:13 ` Marco Fonseca 1 sibling, 2 replies; 36+ messages in thread From: Robert Shade @ 2013-03-26 12:21 UTC (permalink / raw) To: Adrian Chadd Cc: Christian Lamparter, linux-wireless, ath9k-devel, Marco Fonseca I'll get a bug together, but I wanted to report that even with the patch above (fastcc disabled/cold reset always), it still eventually was unable to change the channel. As soon as that failed, it's back into the state where it never seems to xmit anything in the data queues and can't associate. On Mon, Mar 25, 2013 at 12:45 PM, Adrian Chadd <adrian@freebsd.org> wrote: > One for each please. > > > > > Adrian > > > On 25 March 2013 09:12, Christian Lamparter <chunkeey@googlemail.com> wrote: >> On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote: >>> Also, would you please make sure you file a bugzilla.kernel.org ticket >>> so this gets tracked? >>> >>> It's good to know that some combination of fast channel change and >>> warm versus cold reset is making things better/worse. >>> >>> And although a cold reset is likely a good thing to _fix_ the problem, >>> it still leaves the underlying DMA/PHY hangs unresolved. >>> >>> But yes, please file a bugzilla ticket so this gets tracked right! >> Um, do you want a bugreport for ath9k or carl9170 or for both? >> >> Regards, >> Christian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-26 12:21 ` Robert Shade @ 2013-03-26 13:23 ` Robert Shade 2013-03-26 16:28 ` Adrian Chadd 1 sibling, 0 replies; 36+ messages in thread From: Robert Shade @ 2013-03-26 13:23 UTC (permalink / raw) To: Adrian Chadd Cc: Christian Lamparter, linux-wireless, ath9k-devel, Marco Fonseca ath9k bug created: https://bugzilla.kernel.org/show_bug.cgi?id=55771 On Tue, Mar 26, 2013 at 8:21 AM, Robert Shade <robert.shade@gmail.com> wrote: > I'll get a bug together, but I wanted to report that even with the > patch above (fastcc disabled/cold reset always), it still eventually > was unable to change the channel. As soon as that failed, it's back > into the state where it never seems to xmit anything in the data > queues and can't associate. > > On Mon, Mar 25, 2013 at 12:45 PM, Adrian Chadd <adrian@freebsd.org> wrote: >> One for each please. >> >> >> >> >> Adrian >> >> >> On 25 March 2013 09:12, Christian Lamparter <chunkeey@googlemail.com> wrote: >>> On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote: >>>> Also, would you please make sure you file a bugzilla.kernel.org ticket >>>> so this gets tracked? >>>> >>>> It's good to know that some combination of fast channel change and >>>> warm versus cold reset is making things better/worse. >>>> >>>> And although a cold reset is likely a good thing to _fix_ the problem, >>>> it still leaves the underlying DMA/PHY hangs unresolved. >>>> >>>> But yes, please file a bugzilla ticket so this gets tracked right! >>> Um, do you want a bugreport for ath9k or carl9170 or for both? >>> >>> Regards, >>> Christian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-26 12:21 ` Robert Shade 2013-03-26 13:23 ` Robert Shade @ 2013-03-26 16:28 ` Adrian Chadd 2013-03-26 16:29 ` Robert Shade 1 sibling, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-03-26 16:28 UTC (permalink / raw) To: Robert Shade Cc: Christian Lamparter, linux-wireless, ath9k-devel, Marco Fonseca On 26 March 2013 05:21, Robert Shade <robert.shade@gmail.com> wrote: > I'll get a bug together, but I wanted to report that even with the > patch above (fastcc disabled/cold reset always), it still eventually > was unable to change the channel. As soon as that failed, it's back > into the state where it never seems to xmit anything in the data > queues and can't associate. Even after a cold reset? adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-26 16:28 ` Adrian Chadd @ 2013-03-26 16:29 ` Robert Shade 2013-03-26 17:13 ` [ath9k-devel] " Ben Greear 2013-03-26 17:14 ` Adrian Chadd 0 siblings, 2 replies; 36+ messages in thread From: Robert Shade @ 2013-03-26 16:29 UTC (permalink / raw) To: Adrian Chadd Cc: Christian Lamparter, linux-wireless, ath9k-devel, Marco Fonseca On Tue, Mar 26, 2013 at 12:28 PM, Adrian Chadd <adrian@freebsd.org> wrote: > On 26 March 2013 05:21, Robert Shade <robert.shade@gmail.com> wrote: >> I'll get a bug together, but I wanted to report that even with the >> patch above (fastcc disabled/cold reset always), it still eventually >> was unable to change the channel. As soon as that failed, it's back >> into the state where it never seems to xmit anything in the data >> queues and can't associate. > > Even after a cold reset? Yes, which is why I'm curious about the start/stop queues calls. It looks to my (untrained) eye that it's simply not processing the data queue. ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-26 16:29 ` Robert Shade @ 2013-03-26 17:13 ` Ben Greear 2013-03-26 17:16 ` Adrian Chadd 2013-03-27 0:55 ` Robert Shade 2013-03-26 17:14 ` Adrian Chadd 1 sibling, 2 replies; 36+ messages in thread From: Ben Greear @ 2013-03-26 17:13 UTC (permalink / raw) To: Robert Shade Cc: Adrian Chadd, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca On 03/26/2013 09:29 AM, Robert Shade wrote: > On Tue, Mar 26, 2013 at 12:28 PM, Adrian Chadd <adrian@freebsd.org> wrote: >> On 26 March 2013 05:21, Robert Shade <robert.shade@gmail.com> wrote: >>> I'll get a bug together, but I wanted to report that even with the >>> patch above (fastcc disabled/cold reset always), it still eventually >>> was unable to change the channel. As soon as that failed, it's back >>> into the state where it never seems to xmit anything in the data >>> queues and can't associate. >> >> Even after a cold reset? > > Yes, which is why I'm curious about the start/stop queues calls. It > looks to my (untrained) eye that it's simply not processing the data > queue. Can you cat out the /debug/ieee80211/wiphy0/ath9k/xmit file when it gets in this hung state? I saw issues where the xmit queues got hung in our AR9380 NIC systems and ended up adding an ugly bit of cleanup/reset logic to get them working again... Here's the related email thread. https://patchwork.kernel.org/patch/2174221/ My work-around was too ugly for upstream, but if you decide you want to try it out, I'm curious to know if it fixes your problems. You can find my tree here: http://dmz2.candelatech.com/git/gitweb.cgi?p=linux-3.7.dev.y/.git;a=summary Thanks, Ben -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-26 17:13 ` [ath9k-devel] " Ben Greear @ 2013-03-26 17:16 ` Adrian Chadd 2013-03-26 17:27 ` Ben Greear 2013-03-27 0:55 ` Robert Shade 1 sibling, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-03-26 17:16 UTC (permalink / raw) To: Ben Greear Cc: Robert Shade, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca ... and the odd thing here is that during scanning, it should be flushing the queues entirely so any new frame being transmitted _SHOULD_ result in: * TxDP for that queue being written (either FIFO or otherwise); * TxE for that queue being set. So unless the queue is "full" already and isn't being drained, I'm kinda curious as to why TX isn't starting. Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-26 17:16 ` Adrian Chadd @ 2013-03-26 17:27 ` Ben Greear 2013-03-26 17:33 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Ben Greear @ 2013-03-26 17:27 UTC (permalink / raw) To: Adrian Chadd Cc: Robert Shade, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca On 03/26/2013 10:16 AM, Adrian Chadd wrote: > ... and the odd thing here is that during scanning, it should be > flushing the queues entirely so any new frame being transmitted > _SHOULD_ result in: > > * TxDP for that queue being written (either FIFO or otherwise); > * TxE for that queue being set. > > So unless the queue is "full" already and isn't being drained, I'm > kinda curious as to why TX isn't starting. At least for the problems I saw, it was fairly easy to spot the problem once you looked at the xmit debugfs file. There would be 127 pending-frames, axq-depth and ampdu-depth were zero, queue is stopped, and it stays like that for many seconds or minutes. Just resetting the NIC didn't help...I had to also tell the reset to not retry any packets and to set the pending-frames to zero. After that, packets started transmitting again, and often after several seconds I'd see at least most of the old stuck packets be processed to one degree or another (pending frames would go negative since I had forced it to zero earlier). I still do not know the root cause of this, nor have I had time to look at it in any more detail..the work-around is good enough for me for now and I have higher priority issues currently... I only saw the problem in the data queue (BE), but maybe it can happen in other queues as well. Or of course it could be completely un-related to the problem in this email thread.... Thanks, Ben -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-26 17:27 ` Ben Greear @ 2013-03-26 17:33 ` Adrian Chadd 2013-03-26 17:45 ` Ben Greear 0 siblings, 1 reply; 36+ messages in thread From: Adrian Chadd @ 2013-03-26 17:33 UTC (permalink / raw) To: Ben Greear Cc: Robert Shade, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca Right. Well, when you reset the FIFO chances are you should walk said FIFO queue in the TXQ (not the pending frames, the "hw" frames) and requeue each to the hardware. What I am doing in my EDMA restart routine in FreeBSD: * (assume TX is stopped, chip is reset, the completed frames are already removed from the FIFO queue in the TXQ); * save the old FIFO count * blank the FIFO count * walk the FIFO list (NOT the pending list), pushing head pointers back into the FIFO - and this will bump the FIFO counter by one each time; * when I've finished that, compare the FIFO count to the old FIFO count - they should match. I've not looked at the ath9k code in too much depth lately as I've been more interested in getting FreeBSD's EDMA code finished (and I think it is, woo!); so if you give me an hour or two I'll go do another code review and see what pops up. Adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-26 17:33 ` Adrian Chadd @ 2013-03-26 17:45 ` Ben Greear 0 siblings, 0 replies; 36+ messages in thread From: Ben Greear @ 2013-03-26 17:45 UTC (permalink / raw) To: Adrian Chadd Cc: Robert Shade, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca On 03/26/2013 10:33 AM, Adrian Chadd wrote: > Right. Well, when you reset the FIFO chances are you should walk said > FIFO queue in the TXQ (not the pending frames, the "hw" frames) and > requeue each to the hardware. > > What I am doing in my EDMA restart routine in FreeBSD: > > * (assume TX is stopped, chip is reset, the completed frames are > already removed from the FIFO queue in the TXQ); > > * save the old FIFO count > * blank the FIFO count > * walk the FIFO list (NOT the pending list), pushing head pointers > back into the FIFO - and this will bump the FIFO counter by one each > time; > * when I've finished that, compare the FIFO count to the old FIFO > count - they should match. > > I've not looked at the ath9k code in too much depth lately as I've > been more interested in getting FreeBSD's EDMA code finished (and I > think it is, woo!); so if you give me an hour or two I'll go do > another code review and see what pops up. Ok, I'm happy to test patches. Last we tried, we could reproduce the problem very often using lots of stations (32, I think) sending 64kbps or so UDP traffic through an attenuator as we ramp up the attenuation in 10db steps... Thanks, Ben -- Ben Greear <greearb@candelatech.com> Candela Technologies Inc http://www.candelatech.com ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-26 17:13 ` [ath9k-devel] " Ben Greear 2013-03-26 17:16 ` Adrian Chadd @ 2013-03-27 0:55 ` Robert Shade 2013-03-27 3:11 ` Robert Shade 1 sibling, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-03-27 0:55 UTC (permalink / raw) To: Ben Greear Cc: Adrian Chadd, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca On Tue, Mar 26, 2013 at 1:13 PM, Ben Greear <greearb@candelatech.com> wrote: > Can you cat out the /debug/ieee80211/wiphy0/ath9k/xmit > file when it gets in this hung state? I saw issues where > the xmit queues got hung in our AR9380 NIC systems and > ended up adding an ugly bit of cleanup/reset logic to > get them working again... Dumps are attached on to the bug. I remember being hopeful when reading your thread that we stumbled on the same issue, but the symptoms don't look the same to me because pending-frames goes back to 0 in my case. ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-27 0:55 ` Robert Shade @ 2013-03-27 3:11 ` Robert Shade 2013-03-27 16:33 ` Adrian Chadd 0 siblings, 1 reply; 36+ messages in thread From: Robert Shade @ 2013-03-27 3:11 UTC (permalink / raw) To: Ben Greear, Adrian Chadd Cc: Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca Think I found it: In ath_reset_internal, before we reset, we call ath_prepare_reset, which calls ath9k_hw_disable_interrupts. If the channel change fails, we never call ath_complete_reset, which calls ath9k_hw_enable_interrupts. ath9k_hw_{enable|disable}_interrupts calls definitely needs to be balanced. Looking at an old log, IER never gets re-enabled after the channel set failure. Any suggestions on the proper cleanup? Could we just call ath_complete_reset anyway? Some sort of special handling? On Tue, Mar 26, 2013 at 8:55 PM, Robert Shade <robert.shade@gmail.com> wrote: > On Tue, Mar 26, 2013 at 1:13 PM, Ben Greear <greearb@candelatech.com> wrote: >> Can you cat out the /debug/ieee80211/wiphy0/ath9k/xmit >> file when it gets in this hung state? I saw issues where >> the xmit queues got hung in our AR9380 NIC systems and >> ended up adding an ugly bit of cleanup/reset logic to >> get them working again... > > Dumps are attached on to the bug. I remember being hopeful when > reading your thread that we stumbled on the same issue, but the > symptoms don't look the same to me because pending-frames goes back to > 0 in my case. ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: [ath9k-devel] Auth Packet TX Delay 2013-03-27 3:11 ` Robert Shade @ 2013-03-27 16:33 ` Adrian Chadd 0 siblings, 0 replies; 36+ messages in thread From: Adrian Chadd @ 2013-03-27 16:33 UTC (permalink / raw) To: Robert Shade Cc: Ben Greear, Christian Lamparter, ath9k-devel, linux-wireless, Marco Fonseca Good catch! Can you add that to the bugzilla bug please? Adrian On 26 March 2013 20:11, Robert Shade <robert.shade@gmail.com> wrote: > Think I found it: In ath_reset_internal, before we reset, we call > ath_prepare_reset, which calls ath9k_hw_disable_interrupts. If the > channel change fails, we never call ath_complete_reset, which calls > ath9k_hw_enable_interrupts. > > ath9k_hw_{enable|disable}_interrupts calls definitely needs to be > balanced. Looking at an old log, IER never gets re-enabled after the > channel set failure. > > Any suggestions on the proper cleanup? Could we just call > ath_complete_reset anyway? Some sort of special handling? > > On Tue, Mar 26, 2013 at 8:55 PM, Robert Shade <robert.shade@gmail.com> wrote: >> On Tue, Mar 26, 2013 at 1:13 PM, Ben Greear <greearb@candelatech.com> wrote: >>> Can you cat out the /debug/ieee80211/wiphy0/ath9k/xmit >>> file when it gets in this hung state? I saw issues where >>> the xmit queues got hung in our AR9380 NIC systems and >>> ended up adding an ugly bit of cleanup/reset logic to >>> get them working again... >> >> Dumps are attached on to the bug. I remember being hopeful when >> reading your thread that we stumbled on the same issue, but the >> symptoms don't look the same to me because pending-frames goes back to >> 0 in my case. ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-26 16:29 ` Robert Shade 2013-03-26 17:13 ` [ath9k-devel] " Ben Greear @ 2013-03-26 17:14 ` Adrian Chadd 1 sibling, 0 replies; 36+ messages in thread From: Adrian Chadd @ 2013-03-26 17:14 UTC (permalink / raw) To: Robert Shade Cc: Christian Lamparter, linux-wireless, ath9k-devel, Marco Fonseca On 26 March 2013 09:29, Robert Shade <robert.shade@gmail.com> wrote: >> Even after a cold reset? > > Yes, which is why I'm curious about the start/stop queues calls. It > looks to my (untrained) eye that it's simply not processing the data > queue. Well if there's anything in the data queue once you've reset the chip (ie, the whole "no loss" reset path for doing resets when you're doing a scan or recovering from a hung chip) you need to re-program the queue. For the pre-AR9380 chips its easy - for each TXQ: * update axq_link to the be the link field in the last descriptor in the last frame; * push the first descriptor in the first frame into the QCU TxDP address; * set TxE for that queue. For the AR9380 and later chips its a little more complicated because of how the FIFO management works. Felix knows more about this in ath9k; I'm doing something different in FreeBSD. But the basics are the same - you need to walk the FIFO frame list and push the head of each FIFO entry back into the FIFO, then start TX. adrian ^ permalink raw reply [flat|nested] 36+ messages in thread
* Re: Auth Packet TX Delay 2013-03-25 16:45 ` Adrian Chadd 2013-03-26 12:21 ` Robert Shade @ 2013-03-26 14:13 ` Marco Fonseca 1 sibling, 0 replies; 36+ messages in thread From: Marco Fonseca @ 2013-03-26 14:13 UTC (permalink / raw) To: Adrian Chadd Cc: Christian Lamparter, Robert Shade, linux-wireless, ath9k-devel carl9170 bug created here: https://bugzilla.kernel.org/show_bug.cgi?id=55751 On Mon, Mar 25, 2013 at 09:45:48AM -0700, Adrian Chadd wrote: > One for each please. > > > > > Adrian > > > On 25 March 2013 09:12, Christian Lamparter <chunkeey@googlemail.com> wrote: > > On Monday, March 25, 2013 03:23:53 AM Adrian Chadd wrote: > >> Also, would you please make sure you file a bugzilla.kernel.org ticket > >> so this gets tracked? > >> > >> It's good to know that some combination of fast channel change and > >> warm versus cold reset is making things better/worse. > >> > >> And although a cold reset is likely a good thing to _fix_ the problem, > >> it still leaves the underlying DMA/PHY hangs unresolved. > >> > >> But yes, please file a bugzilla ticket so this gets tracked right! > > Um, do you want a bugreport for ath9k or carl9170 or for both? > > > > Regards, > > Christian ^ permalink raw reply [flat|nested] 36+ messages in thread
end of thread, other threads:[~2013-03-27 16:33 UTC | newest]
Thread overview: 36+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
[not found] <CAMgrJ3Y9=K4umoLD=htrrW-Wn4Hgi7qfaKDpY55_GKd=KgD==A@mail.gmail.com>
2013-01-15 22:06 ` Auth Packet TX Delay Robert Shade
2013-01-16 23:09 ` Adrian Chadd
2013-01-17 1:00 ` Robert Shade
2013-01-17 3:12 ` Adrian Chadd
2013-02-06 2:51 ` Robert Shade
2013-02-06 3:08 ` Adrian Chadd
2013-02-06 12:53 ` Robert Shade
2013-02-06 22:58 ` Robert Shade
2013-02-07 5:06 ` Adrian Chadd
2013-02-07 16:25 ` [ath9k-devel] " David Littell
2013-02-07 19:43 ` Robert Shade
2013-02-07 21:40 ` Adrian Chadd
2013-02-08 18:48 ` Robert Shade
2013-02-09 7:39 ` Adrian Chadd
2013-03-24 18:55 ` Robert Shade
2013-03-24 21:52 ` Adrian Chadd
2013-03-24 22:40 ` Robert Shade
2013-03-24 22:58 ` Christian Lamparter
2013-03-25 0:03 ` Adrian Chadd
2013-03-25 2:23 ` Adrian Chadd
2013-03-25 16:12 ` Christian Lamparter
2013-03-25 16:45 ` Adrian Chadd
2013-03-26 12:21 ` Robert Shade
2013-03-26 13:23 ` Robert Shade
2013-03-26 16:28 ` Adrian Chadd
2013-03-26 16:29 ` Robert Shade
2013-03-26 17:13 ` [ath9k-devel] " Ben Greear
2013-03-26 17:16 ` Adrian Chadd
2013-03-26 17:27 ` Ben Greear
2013-03-26 17:33 ` Adrian Chadd
2013-03-26 17:45 ` Ben Greear
2013-03-27 0:55 ` Robert Shade
2013-03-27 3:11 ` Robert Shade
2013-03-27 16:33 ` Adrian Chadd
2013-03-26 17:14 ` Adrian Chadd
2013-03-26 14:13 ` Marco Fonseca
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).