On 22 January 2014 17:25, Stanislaw Gruszka <sgruszka@xxxxxxxxxx> wrote: > On Wed, Jan 22, 2014 at 12:27:44PM +0100, Sergei Antonov wrote: >> The only problem I have now is that when connected to a particular >> access point I get a lot of warnings like this: >> [ 327.309858] ieee80211 phy0: rt2800usb_entry_txstatus_timeout: >> Warning - TX status timeout for entry 13 in queue 2 >> and this: >> [ 327.332847] ieee80211 phy0: rt2800usb_txdone: Warning - Got TX >> status for an empty queue 2, dropping >> I didn't have this problem before (with older kernels and old firmware). > > Does it mean that after you remove new rt2800_mcu_request() and use 0.22 > firmware with 3.13 kernel you do not have those TX status timeout > warnings with this particular AP ? I tried it and the warnings remained. > On older kernels "TX status timeout" messages were only enabled if > kernel was compiled with CONFIG_RT2X00_DEBUG option , so perhaps > that is the reason why you did not see them on older kernel with > older firmware. But if really TX status timeouts start to happen after > firmware update, we should fix our driver to better talk to the > firmware, though I do not have idea how. If not, we should probably > disable those messages in non-debug mode as it was on old kernels. Yes, it could have been due to CONFIG_RT2X00_DEBUG=n that I didn't have warnings. The warnings are printed at least since 3.9. Unfortunately, I could not go back beyond 3.9 because of some compatibility issues between the kernel and the rest of the system. The AP with which I have the warnings is another Linux computer with hostapd-2.0. Can it be the cause of this "TX status" thing? -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
