<div dir="ltr"><div class="gmail_default" style="font-size:small">Yes, those are the error messages I saw in my log.</div><div class="gmail_default" style="font-size:small"><br></div><div class="gmail_default" style="font-size:small">
It is wonderful you seem to be able to trigger them at will.</div><div class="gmail_default" style="font-size:small"> - Jim</div><div class="gmail_default" style="font-size:small"><br></div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Dec 11, 2013 at 3:41 PM, Sebastian Moeller <span dir="ltr"><<a href="mailto:moeller0@gmx.de" target="_blank">moeller0@gmx.de</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi List, hi Dave,<br>
<div class="im"><br>
<br>
On Dec 11, 2013, at 19:41 , Dave Taht <<a href="mailto:dave.taht@gmail.com">dave.taht@gmail.com</a>> wrote:<br>
<br>
> I have the regrettable problem of mostly testing the 5ghz channel due<br>
> to interference issues on the 2ghz band.<br>
><br>
> What I am seeing in the last several releases of the 3.8.x and 3.10<br>
> series is after tons of traffic and multiple days of uptime a DMA tx<br>
> error which you can see via the logread or dmesg tool, and once it<br>
> happens, at least sometimes, that radio can "go away" and not be<br>
> resettable. "cannot stop tx dma" is the error.<br>
<br>
</div> I think I can make tho error appear "at will" by running netperf-wrapper against my wndr3700v2, just tested under 3.10.21-1:<br>
/netperf-wrapper -l 300 -H gw.home.lan rrul -p all -t hms-beagle_cerowrt3.10.21-1_2_nacktmulle<br>
<br>
dmesg on the router:<br>
[ 53.007812] IPv6: ADDRCONF(NETDEV_CHANGE): gw11: link becomes ready<br>
[28792.039062] ath: phy1: Failed to stop TX DMA, queues=0x00e!<br>
[28794.078125] ath: phy1: Failed to stop TX DMA, queues=0x00e!<br>
[28807.164062] ath: phy1: Failed to stop TX DMA, queues=0x00e!<br>
[28809.191406] ath: phy1: Failed to stop TX DMA, queues=0x002!<br>
[28823.269531] ath: phy1: Failed to stop TX DMA, queues=0x00e!<br>
<br>
dmesg was clean before so these 5 failures are from the rrul test over the 5GHz radio<br>
<br>
running the same over the 2.4GHz radio adds the following:<br>
<br>
[29200.921875] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29206.980468] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29209.019531] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29211.066406] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29215.109375] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29227.195312] ath: phy0: Failed to stop TX DMA, queues=0x006!<br>
[29233.257812] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29238.308593] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29240.351562] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29247.417968] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29251.480468] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29253.515625] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29256.558593] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29262.617187] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29264.652343] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29269.699218] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29273.750000] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29278.804687] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29281.859375] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29291.933593] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29294.972656] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29304.050781] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29312.117187] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29315.167968] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29322.246093] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29325.292968] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29330.355468] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29332.390625] ath: phy0: Failed to stop TX DMA, queues=0x00a!<br>
[29334.445312] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29336.484375] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29337.527343] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29343.617187] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29349.679687] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29358.757812] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29361.816406] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29363.851562] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29364.882812] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29370.937500] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29371.976562] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29376.031250] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29378.062500] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29381.105468] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29388.175781] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29393.230468] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29401.292968] ath: phy0: Failed to stop TX DMA, queues=0x003!<br>
[29403.332031] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29413.429687] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29417.480468] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29422.542968] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29424.582031] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29427.636718] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29429.671875] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29431.718750] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29433.765625] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29445.835937] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29449.898437] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29454.960937] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
[29461.023437] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29463.062500] ath: phy0: Failed to stop TX DMA, queues=0x00e!<br>
[29466.117187] ath: phy0: Failed to stop TX DMA, queues=0x00f!<br>
<br>
I have to admit before today I never tested with 2.4GHz and only say the 4 to 5 messages in the 5GHz band.<br>
<br>
Running the same over the wired interface does not cause these messages…<br>
<br>
And running from a 5GHz client through the router to a wired client (both on the internal side) just adds:<br>
[30643.500000] ath: phy1: Failed to stop TX DMA, queues=0x00c!<br>
[30736.898437] ath: phy1: Failed to stop TX DMA, queues=0x00e!<br>
<br>
It does not immediately lead to a drop of the radio though...<br>
<br>
Maybe this can be helpful in the hands of a real expert?<br>
<div class="im"><br>
<br>
> I have seen this error<br>
> many, many times in cerowrt releases for the last 2 years, but this<br>
> time it seems more severe than usual.<br>
><br>
> There was also a bug in dnsmasq or somewhere in the lower level of the<br>
> stack where it stops responding to multicast dhcp packets.<br>
><br>
> The upcoming 3.10.23-1 development release has a refresh of mac80211,<br>
> and a bug fix related to multicast, so I have some hope for it.<br>
><br>
> It has also the latest dnsmasq 2.68 (which fixes a bug in cname<br>
> handling in particular), and also pie v3 but I am (as usual) not in a<br>
> position to test it right now.<br>
><br>
> It is my hope that now that the bug happens a lot we can track it<br>
> down. Or, that it's fixed. :)<br>
><br>
> I just put that release up at:<br>
><br>
> <a href="http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.23-1/" target="_blank">http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.23-1/</a><br>
><br>
> It does not have the updated aqm-scripts code and gui (sorry<br>
> sebastian),<br>
<br>
</div> Ah, even better, I finished the discussed cosmetic changes and tested them, I will try to send them before Sunday, so they might end up in the next cero release. That means you will have to integrate with your changes to avoid HTB for high bandwidths… (or you just put your version in and I will do the integration after the next release :) )<br>
Also, I still need to figure out how to make mutually exclusive with the default QOS system...<br>
<div class="HOEnZb"><div class="h5"><br>
<br>
> nor the pie v4 drop that just got rejected for kernel<br>
> mainline. I'll try to do a respin this weekend with those, and poke<br>
> harder at the dma tx issue after I get back in the lab. Thoughts<br>
> towards being able to isolate the cause and minimize the effect are<br>
> welcomed - it's one of the biggest barriers to declaring a stable<br>
> release at this point!<br>
><br>
><br>
> On Wed, Dec 11, 2013 at 8:58 AM, Stephen Hemminger<br>
> <<a href="mailto:stephen@networkplumber.org">stephen@networkplumber.org</a>> wrote:<br>
>> Has anyone seen wireless failing after several days with 3.10.17-3?<br>
>><br>
>> The symptoms are devices fall off the net several days (or a week) after<br>
>> router has been running. I saw the bg AP go away, but the 5 Ghz AP still<br>
>> working. Wired attachment works.<br>
>> _______________________________________________<br>
>> Cerowrt-devel mailing list<br>
>> <a href="mailto:Cerowrt-devel@lists.bufferbloat.net">Cerowrt-devel@lists.bufferbloat.net</a><br>
>> <a href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
><br>
><br>
><br>
> --<br>
> Dave Täht<br>
><br>
> Fixing bufferbloat with cerowrt: <a href="http://www.teklibre.com/cerowrt/subscribe.html" target="_blank">http://www.teklibre.com/cerowrt/subscribe.html</a><br>
> _______________________________________________<br>
> Cerowrt-devel mailing list<br>
> <a href="mailto:Cerowrt-devel@lists.bufferbloat.net">Cerowrt-devel@lists.bufferbloat.net</a><br>
> <a href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
<br>
_______________________________________________<br>
Cerowrt-devel mailing list<br>
<a href="mailto:Cerowrt-devel@lists.bufferbloat.net">Cerowrt-devel@lists.bufferbloat.net</a><br>
<a href="https://lists.bufferbloat.net/listinfo/cerowrt-devel" target="_blank">https://lists.bufferbloat.net/listinfo/cerowrt-devel</a><br>
</div></div></blockquote></div><br></div>