Page 1 of 1

Error - Dropping frame due to full tx queue

Posted: Thu Oct 11, 2018 8:28 am
by butyl
I have TP-Link TL-WDR4300 running Gargoyle 1.10.0. It is working continuously and flawlessly few months. :D .
So I decided to upgrade my La Fonera 2.0N router from original FW to the newest Gargoyle too.
Everything has seemed to be OK, but after few hours of running, wireless AP stopped communicate with all the clients.
Switching wireless off/on does not help.
I have noticed some dmesg error messages:

Code: Select all

[468242.230000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[468242.250000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[468242.270000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[468242.290000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[468242.310000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Switching the wireless off produce additional errors like this:

Code: Select all

[473276.090000] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[473276.310000] ieee80211 phy0: rt2x00queue_flush_queue: Warning - Queue 2 failed to flush
[534426.300000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
[545421.010000] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2
Can someone help me to solve this, please? Thanx

Re: Error - Dropping frame due to full tx queue

Posted: Thu Oct 11, 2018 2:05 pm
by ispyisail
Try an older firmware

That router is so old that you lucky it works at all

Re: Error - Dropping frame due to full tx queue

Posted: Fri Oct 12, 2018 9:00 am
by butyl
Even though this router is a bit older, it still has enough performance (384 MHz CPU) and enough resources to run the current Gargoyle (64 MB RAM, 8MB Flash).
I do not plan to just throw it in the trash.
I'll see if the downgrade solves the problem. I think older FW uses the same if not older drivers.