ath9k - crashes and unable to reinsert module. Hardware won't reset.

The problem seems to occur when authentication is lost.

1249200593.380775: wlan0 (phy #0): deauth 00:17:c4:75:56:0c -> 00:01:38:8e:0d:6a
 reason 2: Previous authentication no longer valid
1249200599.828700: wlan0 (phy #0): scan finished
1249200611.159049: wlan0 (phy #0): scan finished
1249200626.038172: wlan0 (phy #0): scan finished
1249200637.371171: wlan0 (phy #0): scan finished

Hi Neil,

Can you try installing linux-backports-modules-karmic first and let us know if this issue remains? It contains an updated compat-wireless stack. Thanks.

Tried that and it is now worse. The machine now noticeably pauses each time there is a DMA failure.

[ 245.190471] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
[ 245.190475] ath9k: Chip reset failed
[ 245.190476] ath9k: Unable to reset channel (2457 Mhz) reset status -22
[ 245.190480] ath9k: Unable to set channel
[ 245.379304] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
[ 245.379318] ath9k: Chip reset failed
[ 245.379323] ath9k: Unable to reset hardware; reset status -22
[ 245.390319] ath9k: DMA failed to stop in 10 ms AR_CR=0xffffffff AR_DIAG_SW=0xffffffff
[ 245.500379] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
[ 245.608631] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
[ 245.649520] ath9k 0000:06:00.0: PCI INT A disabled
[ 245.649597] ath9k: Driver unloaded
[ 258.115308] ath9k 0000:06:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[ 258.225773] ath9k: timeout (100000 us) on reg 0x7044: 0xffffffff & 0x0000000f != 0x00000002
[ 258.225783] ath9k: Couldn't reset chip
[ 258.225795] ath9k: Unable to attach hardware; HAL status -5
[ 258.226861] ath9k 0000:06:00.0: PCI INT A disabled

I brought the kernel up to 2.6.31-5 and the driver version in there has less problems than the one in the backports module.

I see this particularly after a resume

Linux chickenhawk 2.6.31-5-generic #24-Ubuntu SMP Sat Aug 1 12:48:18 UTC 2009 i686 GNU/Linux

From watching /var/log/daemon.log and dmesg I'd say something cause it to lose several beacons, wpa supplicant disassociates, and this problem happens, which prolongs or prevents reassociation. happens the same whether I'm on an autheticated ap or an open one.

Disabling network manager and connecting to an ap manually appears to preclude this though I would also observe that once this happens I generally remove the kernel module and reinsert it.

card is:

01:00.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)

part of dmesg follows:

[103236.024083] wlan2: no probe response from AP 00:16:01:7f:6a:b5 - disassociating
[103236.246538] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.317678] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.389625] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.466469] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.538587] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.665620] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.737529] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.809542] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.882510] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103236.953685] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103237.170480] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103237.386542] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103242.205854] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103242.209760] wlan2: authenticate with AP 00:16:01:7f:6a:b5
[103242.212694] wlan2: authenticated
[103242.212710] wlan2: associate with AP 00:16:01:7f:6a:b5
[103242.215408] wlan2: RX ReassocResp from 00:16:01:7f:6a:b5 (capab=0x401 status=0 aid=1)
[103242.215425] wlan2: associated
[103255.960090] wlan2: no probe response from AP 00:16:01:7f:6a:b5 - disassociating
[103256.294427] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.366410] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.438599] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.509554] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.582581] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.653632] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.726640] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.797575] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103256.869651] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[103257.086683] ath9k: DMA failed to stop in 10 ms...

probably this is related to the bug that I opened several days ago which is here:

#404433

https://bugs.launchpad.net/ubuntu/+source/wpasupplicant/+bug/404433

Hi Neil,

Could you attach and updated dmesg output for 2.6.31-5 which shows the latest error messages? Thanks.

Will do.

BTW have you any idea why karmic stops syslogging. Many of the log files state 'rsyslogd has been HUPed, type="lightweight"' and then you get no further logging during the session.

Do you know if that is by design, or is that another bug. It certainly makes pulling faults out a great deal harder than it used to be.

The rsyslogd problem is a fault. It would appear and a bug has been filed.

DMESG attached as requested.

Architecture: amd64
ArecordDevices:
 **** List of CAPTURE Hardware Devices ****
 card 0: Intel [HDA Intel], device 0: STAC92xx Analog [STAC92xx Analog]
   Subdevices: 2/2
   Subdevice #0: subdevice #0
   Subdevice #1: subdevice #1
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: joe 3507 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xd8500000 irq 31'
   Mixer name : 'Intel G45 DEVCTG'
   Components : 'HDA:111d7608,103c306e,00100202 HDA:80862802,80860101,00100000'
   Controls : 32
   Simple ctrls : 19
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=1b57482a-e816-4e8d-b1a5-c0aab7b7dc3e
MachineType: Hewlett-Packard HP Pavilion dv3 Notebook PC
Package: linux (not installed)
ProcCmdLine: root=UUID=f75dcdb0-f0dc-4c1f-90fa-b608bbf12c65 ro single
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-5.24-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-5-generic 2.6.31-5.6
 linux-firmware 1.15
RfKill:
 6: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-5-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
WpaSupplicantLog:

dmi.bios.date: 04/21/2009
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.06
dmi.board.asset.tag: Base Board Asset Tag
dmi.board.name: 306E
dmi.board.vendor: Compal
dmi.board.version: 22.23
dmi.chassis.type: 10
dmi.chassis.vendor: Compal
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnHewlett-Packard:bvrF.06:bd04/21/2009:svnHewlett-Packard:pnHPPaviliondv3NotebookPC:pvrF.06:rvnCompal:rn306E:rvr22.23:cvnCompal:ct10:cvrN/A:
dmi.product.name: HP Pavilion dv3 Notebook PC
dmi.product.version: F.06
dmi.sys.vendor: Hewlett-Packard

I am seeing similar results on a Atheros Communications Inc. AR9285 Wireless Network Adapter (PCI-Express) (rev 01). Intermittent slowdown of speed and dropping the connection often (definitely less than 5 minutes) requiring modprobe -r -f ath9k to continue.

I observed this before and after loading the backports on 2.6.31-5. I'm attaching a bunch of data w/ ath9k debug=0xffffffff turned on.

I've been looking into this bug and notice several similar bugs but all seem to be AMD64.

Would you guys say #414560 is related? I'm getting a lot less dmesg activity than the rest of you are, though, *and* it does generally perform OK.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/414560

Detailed debug of failure.

I've switched to wicd instead of network manager and now have only had the problem once after a suspend. It is apparently related to network manager constantly doing a scan in the background even when connected to a network (to support roaming.

I have the same problem with ubuntu 9.10 alpha5 with all patches:

Linux netbook 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:23 UTC 2009 i686 GNU/Linux

Confirmed on latest alpha-5 on x86_64

Linux binky 2.6.31-9-generic #29-Ubuntu SMP Sun Aug 30 17:39:26 UTC 2009 x86_64 GNU/Linux

I think I've finally found the exact bug that matches my issue. There are a number floating in LP related to ath9k and disconnects. I posted my details in this bug: https://bugs.launchpad.net/bugs/378156 - I believe they are the same problem.

After switching to wicd, the connection is much more stable. I haven't had a dropout in the past 30 minutes, where I would have been dropped 20-30 times using NetworkManager.

@Christopher.

This bug is about ath9k completely lunching itself, so much that it can't reset the chip when you remove the module and reinsert it. That is most certainly a fault with the driver.

Network manager might trigger the fault, but the driver shouldn't misbehave so badly.

Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: neil 3212 F.... pulseaudio
CRDA:
 country 98:
  (2402 - 2482 @ 40), (N/A, 20)
Card0.Amixer.info:
 Card hw:0 'SB'/'HDA ATI SB at 0xf0000000 irq 16'
   Mixer name : 'Realtek ALC888'
   Components : 'HDA:10ec0888,10250206,00100202 HDA:14f12c06,10250093,00100000'
   Controls : 28
   Simple ctrls : 16
Card1.Amixer.info:
 Card hw:1 'HDMI'/'HDA ATI HDMI at 0xcfdec000 irq 19'
   Mixer name : 'ATI RS690/780 HDMI'
   Components : 'HDA:1002791a,00791a00,00100000'
   Controls : 4
   Simple ctrls : 1
Card1.Amixer.values:
 Simple mixer control 'IEC958',0
   Capabilities: pswitch pswitch-joined
   Playback channels: Mono
   Mono: Playback [on]
CheckboxSubmission: fff1b48640eeda6e5016227e703115de
CheckboxSystem: 08f17885f317464241752fbe5a8cd730
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=a1085570-586c-4eac-a7cb-52ca2f87881e
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.
Lsusb:
 Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
 Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Acer Aspire 5536
Package: linux (not installed)
PccardctlIdent:

PccardctlStatus:

ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-10-generic root=UUID=d408b188-d059-4e08-8d94-ee7307e90bd3 ro quiet splash
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-10.32-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-10-generic N/A
 linux-firmware 1.16
RfKill:
 0: acer-wireless: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Uname: Linux 2.6.31-10-generic x86_64
UserGroups:

dmi.bios.date: 02/27/2009
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: V1.03
dmi.board.name: JV50PU
dmi.board.vendor: Acer
dmi.board.version: Rev
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnPhoenixTechnologiesLTD:bvrV1.03:bd02/27/2009:svnAcer:pnAspire5536:pvr0100:rvnAcer:rnJV50PU:rvrRev:cvnAcer:ct10:cvrN/A:
dmi.product.name: Aspire 5536
dmi.product.version: 0100
dmi.sys.vendor: Acer

I've been informed that blacklisting `asus_laptop` module fixes somehow the problem.

Can somebody try this on an Asus laptop?

I have the same problem: Acer 4810TZ:
 02:00.0 Network controller: Atheros Communications Inc. AR928X Wireless Network Adapter (PCI-Express) (rev 01)

In dmesg, I can see:
Oct 10 08:43:26 gustavo-laptop kernel: [ 166.524219] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
Oct 10 08:44:26 gustavo-laptop wpa_supplicant[1190]: CTRL-EVENT-SCAN-RESULTS

Normaly, the problem apper after open transmission software, and download some file in same time, maybe just a coincidence :-)

Sorry, is a Ubuntu Karmic beta with all updates.

Same issues with the latest amd64 version of 9.10 on Toshiba satelite Pro P300-28L.

The connection drops out and it takes ages to reconnect
40000020
[ 1678.252614] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1679.262855] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1679.482676] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1798.255279] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1799.264662] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 1799.484103] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 2370.731588] wlan0: authenticate with AP 00:21:63:81:6d:3d
[ 2370.734534] wlan0: authenticated
[ 2370.734539] wlan0: associate with AP 00:21:63:81:6d:3d
[ 2370.738060] wlan0: RX ReassocResp from 00:21:63:81:6d:3d (capab=0x411 status=0 aid=1)
[ 2370.738065] wlan0: associated
[ 2392.070279] wlan0: no probe response from AP 00:21:63:81:6d:3d - disassociating
[ 2399.422626] wlan0: authenticate with AP 00:21:63:81:6d:3d

My router is just behind the door, but networkmanager thinks it has <25% signal, while the router in the neighbours house shows 100% strength. Could there be some mix up in the driver, and maybe it thinks there is no signal when there is plenty? I had no issues on my macbook pro (currently in service), or winXP on Toshiba (I need ubuntu for some things)

This is still present in Karmic RC. Note that this bug is different from the 'DMA failed to stop' error.

The differentiation is whether you are able to remove and reinsert the module.

If you do:

sudo rmmod ath9k
sudo modprobe ath9k

and you get

[ 900.135286] ath9k: Couldn't reset chip
[ 900.135298] ath9k: Unable to attach hardware; HAL status -5
[ 900.135449] ath9k 0000:06:00.0: PCI INT A disabled

in the dmesg output then you have this bug

If the wireless restarts correctly you probably have this bug

https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/460886

Note that you may have both...

The behaviour with ath9k and "unable to attach hardware; HAL status -5 is exactly what I am experiencing under any 2.6.31.x kernel (both with Arch linux and now also with Karmic RC)

Could anyone else experiencing this eventually provide feedback at http://bugzilla.kernel.org/show_bug.cgi?id=14402 since I though I was the only one seeing this....

I have the same problem in Ubuntu 9.10 final with 2.6.31-14-generic 64-bit a new HP dv7 laptop. After some random time (and especially after suspend to RAM), the ath9k driver dies, there are the same/similar messages in dmesg, and KDE keeps asking me for the WPA password. The only way to get the wireless working is to reboot, which is painful.

Neil: I tried rmmod/modprobe, and I did not see those errors.

Ok the patch mentioned on the upstream bug report linked above is applied to some test kernels for another bug, if those who are affected by this could test these kernels and report back here. Thanks! The kernels are at the URL below:

    http://people.canonical.com/~apw/lp418933-karmic/

I've been having this and similar problems with the ath9k module. Since installing the patched kernel, I've just had 6 hours of network stability. Will post if the problem reoccurs, but I think (fingers crossed) the patch might have done the trick.

This fix is showing good results on a number of bugs and is currently under review for SRU to karmic. Watch this bug for updates.

The lucid kernel already has the commit referenced applied. Therefore closing there.

Andy,

Thanks for putting this together. I've given it a go and the results are not as good as others, although better than the vanilla kernel.

On my system I lose the sound initially on boot, and in particular the inbuilt SPDIF is non-functional to start with despite selecting Digital output on the sound preferences. Instead I get a series of clicks from the machine and a bunch of messages in dmesg

[ 68.200275] hda-intel: spurious response 0x0:0x0, last cmd=0x670503
[ 68.200277] hda-intel: spurious response 0x0:0x0, last cmd=0x670503
[ 68.200280] hda-intel: spurious response 0x0:0x0, last cmd=0x870503
[ 68.200282] hda-intel: spurious response 0x0:0x0, last cmd=0x870503

This is a regression.

On the wireless side the driver is somewhat more stable than orginal. Unfortunately the rate selection algorithm leaves a little to be desired as it is selecting and sticking with rates that are not sustainable. I regularly lose IP throughput to the router despite the wireless showing as connected. When it stick like this and I force a reattachment I get the DMA stall message in the kernel log.

[ 206.241910] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 207.241841] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 207.451996] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 212.494469] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 213.481942] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 213.692490] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 218.724375] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 219.701934] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 219.912340] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 224.951915] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 225.941954] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 226.152381] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 231.201896] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 232.181888] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 232.391960] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 237.444419] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 238.431867] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 238.642009] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 243.694374] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 244.671917] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 244.882413] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 249.921873] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 250.901918] ath9k: DMA failed to stop in 10 ms AR_CR=0x00000024 AR_DIAG_SW=0x40000020
[ 251.114939] ath9k: DMA failed to sto...

@Neil -- ok so we are good on the ath9k fix in the sense its an improvement over not working at all. So I think thats a positive test result dispite ath9k not being wonderful for you. We should get a new bug filed for the performance issues. On the sound issues, could you test the kernel in Karmic -proposed, and if the behaviour is present there could you file a new bug and add the tag regression-proposed to it, and also report its number in this bug for me.

Andy,

I would say that's an over optimistic assessment. It doesn't fix this
bug because the driver still crashes the hardware and we still get the
DMA stalls. It doesn't fix
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/404972 - as
the upper layer throughput issues are still there. It may help with
https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/460886 as it
seems to have stopped the crashes due to network scanning.

So you still get to close a bug, just not this one ;-)

2009/11/12 Andy Whitcroft <email address hidden>:
> @Neil -- ok so we are good on the ath9k fix in the sense its an
> improvement over not working at all.  So I think thats a positive test
> result dispite ath9k not being wonderful for you.  We should get a new
> bug filed for the performance issues.  On the sound issues, could you
> test the kernel in Karmic -proposed, and if the behaviour is present
> there could you file a new bug and add the tag regression-proposed to
> it, and also report its number in this bug for me.
>
> --
> ath9k - crashes and unable to reinsert module. Hardware won't reset.
> https://bugs.launchpad.net/bugs/407040
> You received this bug notification because you are a direct subscriber
> of the bug.
>

--
Neil Wilson

I've had a lot more luck with the backport modules Stefan has put together over on https://bugs.launchpad.net/bugs/460886

That seems to stop the hardware crashes and the DMA stalls. I can rip that driver out in mid flow and then reinsert it with no problems. Unfortunately it generally syncs at super-slow speeds, but at least it works!

I still have a problem, please have a look at http://forum.ubuntu-fr.org/viewtopic.php?pid=3245293

If this is fixed, why are there still problems?

I think the problem is still active. I have a laptop Asus n61jv, with AR9285, wireless card. See kernel.log included

I have the same/a similar problem for quite a while on my eee1005HA. The problems startet after upgrading to 10.04 LTS.

Relevant dmesg:
**********************
[ 408.526742] ath9k: Chip reset failed
[ 408.526747] ath9k: Unable to reset channel (2447 Mhz) reset status -22
[ 408.527319] ath9k: Unable to set channel
[ 408.535568] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[ 408.543900] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[ 408.552142] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[ 408.560394] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[ 408.568604] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[ 408.576811] ath9k: Failed to stop TX DMA in 100 msec after killing last frame
[ 408.576824] ath9k: Unable to stop TxDMA. Reset HAL!
[ 408.693973] ath9k: timeout (100000 us) on reg 0x7000: 0xffffffff & 0x00000003 != 0x00000000
[ 408.693986] ath9k: Chip reset failed
[ 408.693991] ath9k: Unable to reset hardware; reset status -22

uname-a:
*************
Linux oby-eee 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux

lsb_release -rd
********************
Description: Ubuntu 10.04 LTS
Release: 10.04

I have the same problem describe in this bug. My laptop is a Toshiba-Satellite (Atheros Wireless LAN) running Ubuntu 10.4 LTS Lucid Lynx. I have to restart my laptop several time per day :(

[ 3029.873331] Restarting tasks ... done.
[ 3030.033352] r8169: eth0: link down
[ 3030.033588] ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 3030.140179] ath9k: timeout (100000 us) on reg 0x9860: 0x00049d19 & 0x00000001 != 0x00000000
[ 3030.140185] ath9k: Unable to reset hardware; reset status -5 (freq 2437 MHz)
[ 3030.157036] ath9k: Unable to set channel
[ 3030.157312] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 3030.285044] ath9k: Unable to set channel

@Daniel Dufour # 74

A couple of workarounds (covered elsewhere):
- Install packet called 'linux-backports-modules-wireless-luciud-generic'. It didn't completely fix the problem for me, but it happens a lot less anyway
- Instead of restarting, bring up a terminal and run the two commands:
  sudo modprobe -r ath9k
  sudo modprobe ath9k

/N

Feel free to test these patches out:

http://www.kernel.org/pub/linux/kernel/people/mcgrof/patches/ath9k/2010/09/PS-fixes-09-04/

They will be sent upstream and propagated upstream.

This bug was nominated against a series that is no longer supported, ie karmic. The bug task representing the karmic nomination is being closed as Won't Fix.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.