This definitely affects me on maverick and natty, having this hardware:
bkero@Prosper:~$ uname -a
Linux Prosper 2.6.38-02063802-generic #201103281246 SMP Mon Mar 28 12:50:24 UTC 2011 x86_64 GNU/Linux
bkero@Prosper:~$ dmesg|tail -10
[31775.258391] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31775.258428] ath: Failed to stop TX DMA!
[31777.268397] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31777.268434] ath: Failed to stop TX DMA!
[31814.278388] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31814.278426] ath: Failed to stop TX DMA!
[31819.288366] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31819.288404] ath: Failed to stop TX DMA!
[31822.298415] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31822.298453] ath: Failed to stop TX DMA!
This definitely affects me on maverick and natty, having this hardware:
bkero@Prosper:~$ uname -a 02063802- generic #201103281246 SMP Mon Mar 28 12:50:24 UTC 2011 x86_64 GNU/Linux
Linux Prosper 2.6.38-
bkero@Prosper:~$ dmesg|tail -10
[31775.258391] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31775.258428] ath: Failed to stop TX DMA!
[31777.268397] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31777.268434] ath: Failed to stop TX DMA!
[31814.278388] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31814.278426] ath: Failed to stop TX DMA!
[31819.288366] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31819.288404] ath: Failed to stop TX DMA!
[31822.298415] ath: Failed to stop TX DMA in 100 msec after killing last frame
[31822.298453] ath: Failed to stop TX DMA!
bkero@Prosper:~$ lspci|grep Atheros
r01:08.0 Network controller: Atheros Communications Inc. AR5008 Wireless Network Adapter (rev 01)
It seems that there was a fix in 2.6.39-rc1 as evidenced in commit d78f4b3e2c4dfb9 487624f7157af04 ab4260e189
Here's a link to the changelog: http:// www.kernel. org/pub/ linux/kernel/ v2.6/testing/ ChangeLog- 2.6.39- rc1
Additionally, the fix was ported to compat-wireless, so hopefully we can get a fix backported to 2.6.38 for natty.