#11862: ath: Failed to stop TX DMA, queues=0x004
------------------------------+---------------------------------------
Reporter: igor@… | Owner: nbd
Type: defect | Status: assigned
Priority: response-needed | Milestone: Attitude Adjustment 12.09
Component: kernel | Version: Trunk
Resolution: | Keywords:
------------------------------+---------------------------------------
Comment (by cchhat01@…):
Dangit!!!
I am using the WD MyNet N750 routers (2 of them) in WDS mode. Recently, I
switched from r39555 to trunk (r41181) and noticed that clients connecting
to the router were unable to connect at a full 300mbps anymore. I login to
the LuCI frontend and noticed that the 2.4GHz network has its TX Leg
bandwidth halved (from 40MHz to 20MHz) just shortly after the wireless
comes up.
Kernel log shows this particular error about failed to stop TX DM ,
queues=0x004). I have noscan option enabled on both bands (2.4GHz and
5GHz) and on both routers.
Surprisingly this only affects phy0 (only 2.4GHz ?)
Here is my kernel log (from Main router):
[ 221.790000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 221.840000] ath: phy0: Failed to stop TX DMA, queues=0x005!
[ 631.090000] ath: phy0: Failed to stop TX DMA, queues=0x001!
[ 631.590000] ath: phy0: Failed to stop TX DMA, queues=0x001!
[ 632.600000] ath: phy0: Failed to stop TX DMA, queues=0x005!
[ 633.590000] ath: phy0: Failed to stop TX DMA, queues=0x001!
and from the WDS Client+AP (secondary router):
[ 731.670000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 731.720000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 731.760000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 731.800000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 731.850000] ath: phy0: Failed to stop TX DMA, queues=0x004!
[ 731.890000] ath: phy0: Failed to stop TX DMA, queues=0x005!
Also looking at the system log, I think this problem is caused when one of
my WiFi devices (HP-Notebook with AR9285 WiFi Card) tries to connect to
the routers, up until this point everything works fine in 40MHz mode.
Here is the log from the Main router:
Sun Jun 15 19:19:37 2014 daemon.info hostapd: wlan0: STA
4c:xx:xx:xx:xx:xx IEEE 802.11: Switching to 20 MHz operation
Sun Jun 15 19:19:38 2014 kern.err kernel: [ 216.720000] ath: phy0:
Failed to stop TX DMA, queues=0x004!
Sun Jun 15 19:19:38 2014 kern.err kernel: [ 216.770000] ath: phy0:
Failed to stop TX DMA, queues=0x004!
And from the WDS AP+Client router:
Sun Jun 15 19:28:12 2014 daemon.info hostapd: wlan0: STA
4c:xx:xx:xx:xx:xx IEEE 802.11: Switching to 20 MHz operation
Sun Jun 15 19:28:15 2014 kern.err kernel: [ 724.900000] ath: phy0:
Failed to stop TX DMA, queues=0x004!
Sun Jun 15 19:28:15 2014 kern.err kernel: [ 724.940000] ath: phy0:
Failed to stop TX DMA, queues=0x004!
Not sure what this means
This didn't happen with r39555 so something has changed. Probably kernel
related assuming i went from 3.10.28 to 3.10.36.
Hope this helps figuring out what is causing this problem.
In the meantime, is there a particular trunk build in the r4xxxx range
that I can build that won't exhibit this issue? I need trunk because
support for my routers is only enabled trunk (I think?).
Thanks,
Chirag C.
--
Ticket URL: <https://dev.openwrt.org/ticket/11862#comment:239>
OpenWrt <http://openwrt.org>
Opensource Wireless Router Technology
_______________________________________________
openwrt-tickets mailing list
[email protected]
https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-tickets
