I can confirm this on Lucid. Here is a extract of /var/log/kern.log May 24 09:38:59 simon kernel: [24955.346856] ath9k: Two wiphys trying to scan at the same time May 24 09:38:59 simon kernel: [24955.346904] wlan0: deauthenticating from 00:18:39:c1:67:60 by local choice (reason=3) May 24 09:38:59 simon kernel: [24955.533873] wlan0: direct probe to AP 00:18:39:c1:67:60 (try 1) May 24 09:38:59 simon kernel: [24955.536753] wlan0: direct probe responded May 24 09:38:59 simon kernel: [24955.536761] wlan0: authenticate with AP 00:18:39:c1:67:60 (try 1) May 24 09:38:59 simon kernel: [24955.541878] wlan0: authenticated May 24 09:38:59 simon kernel: [24955.541918] wlan0: associate with AP 00:18:39:c1:67:60 (try 1) May 24 09:38:59 simon kernel: [24955.545020] wlan0: RX AssocResp from 00:18:39:c1:67:60 (capab=0x411 status=0 aid=1) May 24 09:38:59 simon kernel: [24955.545026] wlan0: associated May 24 09:38:59 simon kernel: [24955.546084] ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready May 24 09:39:10 simon kernel: [24966.000101] wlan0: no IPv6 routers present May 24 09:51:59 simon kernel: [25734.526053] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:51:59 simon kernel: [25734.526065] ath9k: Unable to reset channel (5280 Mhz) reset status -5 May 24 09:51:59 simon kernel: [25734.526077] ath9k: Unable to set channel May 24 09:51:59 simon kernel: [25734.650785] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:51:59 simon kernel: [25734.650789] ath9k: Unable to reset channel (2422 Mhz) reset status -5 May 24 09:51:59 simon kernel: [25734.650829] ath9k: Unable to set channel May 24 09:52:00 simon kernel: [25735.083274] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:52:00 simon kernel: [25735.083285] ath9k: Unable to reset channel (5300 Mhz) reset status -5 May 24 09:52:00 simon kernel: [25735.083301] ath9k: Unable to set channel May 24 09:52:00 simon kernel: [25735.207968] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:52:00 simon kernel: [25735.207973] ath9k: Unable to reset channel (2422 Mhz) reset status -5 May 24 09:52:00 simon kernel: [25735.207978] ath9k: Unable to set channel May 24 09:52:00 simon kernel: [25735.630661] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:52:00 simon kernel: [25735.630673] ath9k: Unable to reset channel (5320 Mhz) reset status -5 May 24 09:52:00 simon kernel: [25735.630727] ath9k: Unable to set channel May 24 09:52:00 simon kernel: [25735.755290] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:52:00 simon kernel: [25735.755294] ath9k: Unable to reset channel (2422 Mhz) reset status -5 May 24 09:52:00 simon kernel: [25735.755299] ath9k: Unable to set channel May 24 09:52:02 simon kernel: [25736.930112] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000 May 24 09:52:02 simon kernel: [25736.930124] ath9k: Unable to reset hardware; reset status -5 May 24 09:52:02 simon kernel: [25737.238410] ath9k: Failed to stop TX DMA in 100 msec after killing last frame May 24 09:52:02 simon kernel: [25737.238436] ath9k: Unable to stop TxDMA. Reset HAL!
$ uname -a Linux simon 2.6.32-22-generic #33-Ubuntu SMP Wed Apr 28 13:28:05 UTC 2010 x86_64 GNU/Linux $ lsb_release -rd Description: Ubuntu 10.04 LTS Release: 10.04 -- ath9k causes system lockup https://bugs.launchpad.net/bugs/289356 You received this bug notification because you are a member of Mactel Support, which is the registrant for Mactel Support. Status in Mactel Support: Fix Released Status in “linux” package in Ubuntu: Fix Released Bug description: I've had repeated trouble with ath9k causing my system to lock up. It's a macbook, late 2006 model, running 8.10. lspci -v shows the following info: 02:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01) Flags: bus master, fast devsel, latency 0, IRQ 17 Memory at 90100000 (64-bit, non-prefetchable) [size=64K] Capabilities: [40] Power Management version 2 Capabilities: [50] Message Signalled Interrupts: Mask- 64bit- Queue=0/0 Enable- Capabilities: [60] Express Legacy Endpoint, MSI 00 Capabilities: [90] MSI-X: Enable- Mask- TabSize=1 Capabilities: [100] Advanced Error Reporting <?> Capabilities: [140] Virtual Channel <?> Kernel driver in use: ath9k Kernel modules: ath9k Kernel: Linux uviol 2.6.27-7-generic #1 SMP Fri Oct 24 06:40:41 UTC 2008 x86_64 GNU/Linux Symptoms are the wireless network fails to respond and I am unable to reconnect. I get repeated popups asking for WPA2 password, and lots of messages like this in the log: [72782.981155] ath9k_config: Unable to set channel [72783.337281] ath_set_channel: unable to reset channel 60 (5300Mhz) flags 0x103 42 hal status 4294967277 [72783.337369] ath9k_config: Unable to set channel [72783.693048] ath_set_channel: unable to reset channel 64 (5320Mhz) flags 0x103 42 hal status 4294967277 [72783.693164] ath9k_config: Unable to set channel [72784.049049] ath_set_channel: unable to reset channel 149 (5745Mhz) flags 0x30 142 hal status 4294967277 [72784.049173] ath9k_config: Unable to set channel [72784.336993] ath_set_channel: unable to reset channel 153 (5765Mhz) flags 0x50 142 hal status 4294967277 First time this happens, I can clear the problem by unloading and reloading the ath9k module. It will occur again shortly afterward. Second or third time around the ath9k module will unload and reload fine, but following this any process that tries accessing the device will hang (NetworkManager, 'ifconfig', etc.) and the system becomes more and more unresponsive until I have to power off. This bug is a showstopper for me and rebooting twice daily has shot my workflow to bits, so I'm happy to help debug this in any way I can. _______________________________________________ Mailing list: https://launchpad.net/~mactel-support Post to : [email protected] Unsubscribe : https://launchpad.net/~mactel-support More help : https://help.launchpad.net/ListHelp
