Bug 821173 - [ath9k] ath: Failed to stop TX DMA, queues=0x005!
Summary: [ath9k] ath: Failed to stop TX DMA, queues=0x005!
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 17
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: John Greene
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-05-12 18:47 UTC by James
Modified: 2013-01-02 13:58 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2013-01-02 13:15:59 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
dmesg (76.66 KB, text/x-log)
2012-05-12 18:47 UTC, James
no flags Details
lspci -vvvv output (27.27 KB, text/plain)
2012-05-12 18:47 UTC, James
no flags Details

Description James 2012-05-12 18:47:20 UTC
Created attachment 584060 [details]
dmesg

Description of problem:
Typically under heavy load using the wireless network, the message

   ath: Failed to stop TX DMA, queues=0x005!

sometimes appears. The interface seems to stop working for a few seconds, then resumes. An example of this was provoked using scp to transfer an ISO image (ar atound 5 MB/s). The transfer itself completed with no data corruption.

Machine is using an AR9285 wireless chip.

dmesg and lspci output attached.

Version-Release number of selected component (if applicable):
kernel-3.3.5-2.fc17.x86_64
linux-firmware-20120206-0.3.git06c8f81.fc17.noarch

Comment 1 James 2012-05-12 18:47:53 UTC
Created attachment 584061 [details]
lspci -vvvv output

Comment 2 James 2012-05-12 18:52:37 UTC
iwconfig output:


lo        no wireless extensions.

p5p1      no wireless extensions.

virbr0    no wireless extensions.

wlan0     IEEE 802.11bgn  ESSID:"<REDACTED>"  
          Mode:Managed  Frequency:2.437 GHz  Access Point: <REDACTED>   
          Bit Rate=65 Mb/s   Tx-Power=27 dBm   
          Retry  long limit:7   RTS thr:off   Fragment thr:off
          Power Management:on
          Link Quality=70/70  Signal level=-40 dBm  
          Rx invalid nwid:0  Rx invalid crypt:0  Rx invalid frag:0
          Tx excessive retries:48  Invalid misc:1296   Missed beacon:0

Comment 3 Justin M. Forbes 2012-09-11 15:13:44 UTC
Is this still happening with 3.5.3 from updates testing?

Comment 4 James 2013-01-02 13:57:26 UTC
Sorry for dropping out on this one. I've not seen this one anywhere in recent logs (3.6 series kernels), currently running 3.6.11 so I think it can be marked fixed.


Note You need to log in before you can comment on or make changes to this bug.