On Wed, Jan 29, 2014 at 06:45:31PM +0100, Sergei Antonov wrote: > > 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. I will move those annoying messages back to debug level, they are printed by default by mistake anyway. > 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? It can be that AP does not ACK some frames for some reason and we see those warnings. Could you please provide me details about that AP (what H/W and driver is used and hostapd config file), I will see if I could reproduce those messages locally. Stanislaw -- 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
