On Thu, Jan 11, 2018 at 05:00:14PM +0100, Tom Psyborg wrote: > does not help as expected. there was even a crash: You mean the kernel hangs ? There is a WARNING at the end of the logs but it's from ath9k not from rt2800. > [ 92.559018] ieee80211 phy1: rt2800mmio_txstatus_is_spurious: Warning - 4 > spurious TX_FIFO_STATUS interrupt(s) This is suspicious, we should not get spurious interrupts. Perhaps there is something wrong on platform lever, maybe with pinmux ? > for an empty queue 2, dropping > [ 176.019555] ieee80211 phy1: rt2x00lib_rxdone_read_signal: Warning - > Frame received with unrecognized signal, mode=0x0001, signal=0x010f, type=4 > [ 176.025456] ieee80211 phy1: rt2x00lib_rxdone_read_signal: Warning - and this indicate that HW/FW do not provide correct frames to the driver any longer. Again - I think we do something that make device no longer possible to function normally. Changing queue stop/start thresholds will not help with that. Cheers Stanislaw
