Hi Daniel On Sat, Aug 18, 2018 at 06:08:40PM +0200, Daniel Golle wrote: > Still seeing a lot of those > > Sat Aug 18 16:05:51 2018 kern.err kernel: [ 8364.972151] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2 > Sat Aug 18 16:05:51 2018 kern.err kernel: [ 8364.981622] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2 > Sat Aug 18 16:05:51 2018 kern.err kernel: [ 8364.991070] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2 > Sat Aug 18 16:05:51 2018 kern.err kernel: [ 8365.000506] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2 > Sat Aug 18 16:05:51 2018 kern.err kernel: [ 8365.009935] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2 > > while wifi somehow keeps working at degraded level once the error > occured. I would like to know why we get those errors at all. Perhaps there is something wrong with queue pause/unpasue logic. Or with locking. Or maybe this is normal, we pausue queue in mac80211 but it still have some pending skbs which are scheduled to the driver. Let's check if pausing is correct. Please apply this patch: https://github.com/sgruszka/wireless-drivers-next/commit/525c50486e17446793b21ac7a8498cb48b3bb210.patch and provide dmesg output. Note that adding printk messages can make itself somehow AP unresponsive, as I pointed earlier in this thread. However at this point I would like to check if queue pause works as it should in the driver. Also, how do test? I can not reproduce those errors. Thanks Stanislaw
