[ath9k-devel] Failed to stop TX DMA on kernel 3.0 and wireless dies...

[ath9k-devel] Failed to stop TX DMA on kernel 3.0 and wireless dies...

[F.Sluiter]

Hi list.
There are some problems with the ath9 driver for wireless cards in
ubuntu oneric.
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/736171?comments=all

But I looked at this list and found a similar problemm reported for kernel 3.1

Could you take a look and let me know what i can do to fix this
(please e-mail me directly on fsluiter at gmail.com, or reply to the bug
on launchpad)?
If you need any additional info or testing, please feel free to ask.

I'll add the output of uname, lspci, ping, dmesg below.

I did try "options nohwcrypt=1", but that did not work at all (the
error was actually getting worse, i.e. almost immediately after having
connected to the router).

What might be significantin the bugtrack on launchpad is that some of
the errors mention 100ms and oguzy and mine mention 10ms. Also when my
wireless does work, the speed (8mb/s down) and ping (2ms to router) is
normal and the indicator lighton the laptop is on. This changes to
off, the errors appear in the logs and the network manager tries to
reconnect, claiming that the connection needs a password, which it
does already have.
With a powerdown and start, the connection comes back up, a simple
restart is not enough. After a simple restart, the kernel does not
recognize the network card anymore, lspci does not show it to be
present on bus 3:0.0 where it previously was. With a simple restart to
Windows it does not recognize the card sometimes also. I read
somewhere that this type of card needs/gets a firmware
reinitialisation every time a reboot occurs, so that might be
important.

The all or nothing behaviour of the bug I see seems to me more
consistent with a race condition than an encryption problem. Maybe
this race condition changes when encryption is on/off.
I think the above patchby Christian Aravena, which (I think) adds a
call to a semaphore in the ath9 driver, is not present in the 3.0
kernel driver and therefore the bug was reintroduced. Is there someone
who can verify it not being present in this kernel? That would explain
a lot.

kind regards,

Floris

root at v-laptop:~# uname -a
Linux v-laptop 3.0.0-14-generic-pae #23-Ubuntu SMP Mon Nov 21 22:07:10
UTC 2011 i686 i686 i386 GNU/Linux

root at v-laptop:~# lspci
00:00.0 Host bridge: Intel Corporation 2nd Generation Core Processor
Family DRAM Controller (rev 09)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200/2nd Generation Core
Processor Family PCI Express Root Port (rev 09)
00:02.0 VGA compatible controller: Intel Corporation 2nd Generation
Core Processor Family Integrated Graphics Controller (rev 09)
00:16.0 Communication controller: Intel Corporation 6 Series/C200
Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 6 Series/C200 Series Chipset
Family High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 1 (rev b4)
00:1c.1 PCI bridge: Intel Corporation 6 Series/C200 Series Chipset
Family PCI Express Root Port 2 (rev b4)
00:1d.0 USB Controller: Intel Corporation 6 Series/C200 Series Chipset
Family USB Enhanced Host Controller #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM65 Express Chipset Family LPC
Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 6 Series/C200 Series
Chipset Family 6 port SATA AHCI Controller (rev 04)
00:1f.3 SMBus: Intel Corporation 6 Series/C200 Series Chipset Family
SMBus Controller (rev 04)
01:00.0 VGA compatible controller: nVidia Corporation Device 1050 (rev a1)
02:00.0 Ethernet controller: Broadcom Corporation NetLink BCM57785
Gigabit Ethernet PCIe (rev 10)
02:00.1 SD Host controller: Broadcom Corporation NetXtreme BCM57765
Memory Card Reader (rev 10)
02:00.2 System peripheral: Broadcom Corporation Device 16be (rev 10)
02:00.3 System peripheral: Broadcom Corporation Device 16bf (rev 10)
03:00.0 Network controller: Atheros Communications Inc. AR9287
Wireless Network Adapter (PCI-Express) (rev 01)
root at v-laptop:~# ping 192.168.2.1
PING 192.168.2.1 (192.168.2.1) 56(84) bytes of data.
64 bytes from 192.168.2.1: icmp_req=1 ttl=64 time=2.12 ms
64 bytes from 192.168.2.1: icmp_req=2 ttl=64 time=3.15 ms
64 bytes from 192.168.2.1: icmp_req=3 ttl=64 time=2.13 ms
64 bytes from 192.168.2.1: icmp_req=4 ttl=64 time=2.17 ms
64 bytes from 192.168.2.1: icmp_req=5 ttl=64 time=2.01 ms
64 bytes from 192.168.2.1: icmp_req=6 ttl=64 time=2.15 ms
64 bytes from 192.168.2.1: icmp_req=7 ttl=64 time=2.85 ms
64 bytes from 192.168.2.1: icmp_req=8 ttl=64 time=40.5 ms
64 bytes from 192.168.2.1: icmp_req=9 ttl=64 time=2.32 ms
64 bytes from 192.168.2.1: icmp_req=10 ttl=64 time=2.09 ms
64 bytes from 192.168.2.1: icmp_req=11 ttl=64 time=4.33 ms
64 bytes from 192.168.2.1: icmp_req=12 ttl=64 time=2.53 ms
64 bytes from 192.168.2.1: icmp_req=13 ttl=64 time=2.02 ms
64 bytes from 192.168.2.1: icmp_req=14 ttl=64 time=65.9 ms
64 bytes from 192.168.2.1: icmp_req=15 ttl=64 time=17.1 ms
64 bytes from 192.168.2.1: icmp_req=16 ttl=64 time=1.79 ms
64 bytes from 192.168.2.1: icmp_req=17 ttl=64 time=2.46 ms
^C
--- 192.168.2.1 ping statistics ---
17 packets transmitted, 17 received, 0% packet loss, time 16017ms
rtt min/avg/max/mdev = 1.793/9.286/65.921/16.995 ms


root at v-laptop:~# dmesg | grep ath
[   20.065004] ath9k 0000:03:00.0: PCI INT A -> GSI 17 (level, low) -> IRQ 17
[   20.065019] ath9k 0000:03:00.0: setting latency timer to 64
[   20.152960] ath: EEPROM regdomain: 0x65
[   20.152962] ath: EEPROM indicates we should expect a direct regpair map
[   20.152965] ath: Country alpha2 being used: 00
[   20.152966] ath: Regpair used: 0x65
[   20.204916] ieee80211 phy0: Selected rate control algorithm
'ath9k_rate_control'
[   20.205585] Registered led device: ath9k-phy0
[   20.766339] type=1400 audit(1325436363.391:9): apparmor="STATUS"
operation="profile_load" name="/usr/lib/telepathy/mission-control-5"
pid=922 comm="apparmor_parser"
[   20.766891] type=1400 audit(1325436363.391:10): apparmor="STATUS"
operation="profile_load" name="/usr/lib/telepathy/telepathy-*" pid=922
comm="apparmor_parser"

[ 2030.479445] ath: Failed to stop TX DMA!
[ 2030.544822] ath: Failed to stop TX DMA!
[ 2030.557780] ath: DMA failed to stop in 10 ms AR_CR=0xffffffff
AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
[ 2030.557787] ath: Could not stop RX, we could be confusing the DMA
engine when we start RX up
[ 2030.673138] ath: Chip reset failed
[ 2030.673143] ath: Unable to reset hardware; reset status -22
[ 2030.738733] ath: Failed to stop TX DMA!
[ 2030.751711] ath: DMA failed to stop in 10 ms AR_CR=0xffffffff
AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
[ 2030.751718] ath: Could not stop RX, we could be confusing the DMA
engine when we start RX up
[ 2030.867161] ath: Chip reset failed
[ 2030.867169] ath: Unable to reset channel (2462 MHz), reset status -22
[ 2031.025852] ath: Failed to wakeup in 500us
[ 2031.093434] ath: Failed to wakeup in 500us
[ 2031.104088] ath: Failed to wakeup in 500us
[ 2031.219479] ath: Chip reset failed
[ 2031.219487] ath: Unable to reset channel (2462 MHz), reset status -22
[ 2031.709624] ath: Failed to stop TX DMA!
[ 2031.775014] ath: Failed to stop TX DMA!
[ 2031.787995] ath: DMA failed to stop in 10 ms AR_CR=0xffffffff
AR_DIAG_SW=0xffffffff DMADBG_7=0xffffffff
[ 2031.788003] ath: Could not stop RX, we could be confusing the DMA
engine when we start RX up
[ 2031.903366] ath: Chip reset failed
[ 2031.903373] ath: Unable to reset hardware; reset status -22
[ 2031.968891] ath: Failed to stop TX DMA!