All of lore.kernel.org
 help / color / mirror / Atom feed
From: Enrico Mioso <mrkiko.rs@gmail.com>
To: Stanislaw Gruszka <sgruszka@redhat.com>
Cc: linux-wireless@vger.kernel.org,
	Johannes Berg <johannes.berg@intel.com>,
	Daniel Golle <daniel@makrotopia.org>,
	Arnd Bergmann <arnd@arndb.de>, John Crispin <john@phrozen.org>,
	nbd@nbd.name
Subject: Re: ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue...?
Date: Sat, 16 Dec 2017 19:33:47 +0100 (CET)	[thread overview]
Message-ID: <alpine.LNX.2.21.99.1712161924030.11214@localhost.localdomain> (raw)
In-Reply-To: <20171213152017.GA3554@redhat.com>

Hello!
I tested the Archer MR200 device removing the patch as you suggested:
package/kernel/mac80211/patches/600-23-rt2x00-rt2800mmio-add-a-workaround-for-spurious-TX_F.patch
... the error still appears, but the driver is still working as of now.
Here - reporting my dmesg
[  819.060392] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.069900] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.079369] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.088823] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.098277] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.107729] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.117174] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.126627] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.136080] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.145533] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.154987] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.164441] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.173890] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.183336] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.192782] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.202200] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.211644] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.221090] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.230537] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.239983] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
[  819.249430] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2

To cause it, it seems a good technique to use a device as far as possible from the AP, but not enough to disconnect / stop working.
A reauthentication may be required to use the AP again,

Sat Dec 16 17:59:01 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Sat Dec 16 17:59:01 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Sat Dec 16 17:59:01 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Sat Dec 16 17:59:01 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.060392] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.069900] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.079369] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.088823] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.098277] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.107729] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.117174] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.126627] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.136080] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.145533] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.154987] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.164441] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.173890] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.183336] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.192782] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.202200] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.211644] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.221090] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.230537] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.239983] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:04:20 2017 kern.err kernel: [  819.249430] ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 2
Sat Dec 16 18:11:11 2017 daemon.info hostapd: wlan0: STA x2:x2:x2:x2:x2:x2 IEEE 802.11: authenticated
Sat Dec 16 18:11:11 2017 daemon.info hostapd: wlan0: STA x2:x2:x2:x2:x2:x2 IEEE 802.11: associated (aid 2)
Sat Dec 16 18:11:11 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED x2:x2:x2:x2:x2:x2
Sat Dec 16 18:11:11 2017 daemon.info hostapd: wlan0: STA x2:x2:x2:x2:x2:x2 WPA: pairwise key handshake completed (RSN)
Sat Dec 16 18:18:43 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED x2:x2:x2:x2:x2:x2
Sat Dec 16 18:18:43 2017 daemon.info hostapd: wlan0: STA x2:x2:x2:x2:x2:x2 IEEE 802.11: disassociated due to inactivity
Sat Dec 16 18:18:44 2017 daemon.info hostapd: wlan0: STA x2:x2:x2:x2:x2:x2 IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Dec 16 18:19:03 2017 daemon.notice hostapd: wlan0: AP-STA-DISCONNECTED xx:xx:xx:xx:xx:xx
Sat Dec 16 18:19:03 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: disassociated due to inactivity
Sat Dec 16 18:19:04 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: deauthenticated due to inactivity (timer DEAUTH/REMOVE)
Sat Dec 16 19:16:03 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: authenticated
Sat Dec 16 19:16:03 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx IEEE 802.11: associated (aid 1)
Sat Dec 16 19:16:03 2017 daemon.notice hostapd: wlan0: AP-STA-CONNECTED xx:xx:xx:xx:xx:xx
Sat Dec 16 19:16:03 2017 daemon.info hostapd: wlan0: STA xx:xx:xx:xx:xx:xx WPA: pairwise key handshake completed (RSN)

where the xx:xx... mac is an iPhone SE, the x2:x2... is an Android device.

thank you very much for the help and all.
For the moment I am not sure about the situation still, so I think further testing would be needed. Hoping someone experiencing this problem can come up and give some more hints / tests on different hw.
Thank you to all,
Enrico

On Wed, 13 Dec 2017, Stanislaw Gruszka wrote:

> Date: Wed, 13 Dec 2017 16:20:18
> From: Stanislaw Gruszka <sgruszka@redhat.com>
> To: Enrico Mioso <mrkiko.rs@gmail.com>
> Cc: linux-wireless@vger.kernel.org, Johannes Berg <johannes.berg@intel.com>,
>     Daniel Golle <daniel@makrotopia.org>, Arnd Bergmann <arnd@arndb.de>,
>     John Crispin <john@phrozen.org>, nbd@nbd.name
> Subject: Re: ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping
>     frame due to full tx queue...?
> 
> On Mon, Dec 11, 2017 at 09:51:29PM +0100, Enrico Mioso wrote:
>> Hello guys, and sorry for the big CC list.
>> I would like to point out about a bug who survived for years - at least from 2015 until now, regarding the Ralink driver getting stuck, and in some cases not being able to recover.
>> The problem manifested with an MT7620A chip, and the wireless card inside the WL-330N3G device.
>> The error message is in rt2x00/rt2x00queue.c .
>>
>> This bug was discussed, and a patch proposed, in this thread:
>> https://lists.openwrt.org/pipermail/openwrt-devel/2015-September/thread.html#35778
>>
>> I would like to help if possible - I have the have both an Archer MR200, and the WL330n3G hardware.
>> BTW, the Archer MR200 is a nice MT7610 device, and the problem manifests itself, see:
>> https://forum.openwrt.org/viewtopic.php?id=64293&p=6
>>
>> Any help, hint, anything would be apreciated.
>> thank you to all.
>
> First I would try to remove this patch:
> http://git.lede-project.org/?p=source.git;a=blob;f=package/kernel/mac80211/patches/600-23-rt2x00-rt2800mmio-add-a-workaround-for-spurious-TX_F.patch
> and see if it makes things better. However I think for the stuck problem
> we need tx status timeout mechanism similar like for rt2800usb.
>
> Attached patch can mitigate "Dropping frame due to full tx queue"
> errors. I did not test it, so it can be totally broken.
>
> Regards
> Stanislaw
>

  reply	other threads:[~2017-12-16 18:33 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-11 20:51 ieee80211 phy0: rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue...? Enrico Mioso
2017-12-13 15:20 ` Stanislaw Gruszka
2017-12-16 18:33   ` Enrico Mioso [this message]
2017-12-18 15:21     ` Stanislaw Gruszka
2017-12-19 12:27       ` Stanislaw Gruszka
2017-12-19 12:39         ` Enrico Mioso
2017-12-19 12:43         ` Enrico Mioso
2017-12-19 12:54           ` Stanislaw Gruszka
2017-12-19 13:25             ` Enrico Mioso
2017-12-20 17:49             ` Enrico Mioso
2017-12-21 14:25               ` Stanislaw Gruszka
2017-12-24 12:19                 ` Enrico Mioso
2018-01-03 11:35                   ` Stanislaw Gruszka
2018-01-03 14:04                     ` Enrico Mioso
     [not found]                       ` <CAKR_QVLRwAA0NJSarX46J4A8XSp8h5SuTEtSBQ4ydpEPh_-aUw@mail.gmail.com>
2018-01-22  5:45                         ` Enrico Mioso
2018-01-23 13:22                           ` Stanislaw Gruszka
2018-01-24  5:14                             ` Enrico Mioso
2018-01-24  8:18                             ` Enrico Mioso
2018-01-24 10:03                               ` Stanislaw Gruszka
2018-03-01 15:30                                 ` Daniel Golle
2018-03-02 19:13                                   ` Enrico Mioso
2018-03-07 12:27                                   ` Stanislaw Gruszka
2018-03-07 12:29                                     ` Stanislaw Gruszka
2018-03-23  7:51                                       ` Mathias Kresin
2018-03-26 10:35                                         ` Stanislaw Gruszka
2018-03-27  7:46                                           ` Mathias Kresin
2018-03-27 17:18                                             ` Stanislaw Gruszka
2018-03-27 17:43                                               ` Daniel Golle
2018-03-28  4:14                                                 ` Enrico Mioso
     [not found]                                                   ` <CAOt++SeSQ2j1KuVkbqt77LfznXN7JV0Lx5O8d7-m2VBrz8=85g@mail.gmail.com>
2018-03-29  5:13                                                     ` Enrico Mioso
2018-03-30 14:41                                                     ` Enrico Mioso
2018-03-30 14:44                                                     ` Enrico Mioso
     [not found]                                                       ` <MWHPR02MB3326233159B021143D7278F5D4A10@MWHPR02MB3326.namprd02.prod.outlook.com>
2018-03-30 17:33                                                         ` Enrico Mioso
     [not found]                                                           ` <CAOt++SeLh_NxcmM=YEMQSv4y9PabS_dT7k4yTxUiqXbac-=iUQ@mail.gmail.com>
2018-04-17 13:55                                                             ` Enrico Mioso
2018-04-17 13:56                                                               ` Jamie Stuart
2018-04-17 13:57                                                             ` Enrico Mioso
2018-04-17 19:42                                                             ` Stanislaw Gruszka
     [not found]                                                               ` <CAOt++SeNt=4RUTvAR1y_WjC=a-YyYa3YBSmoAmv+7uK71U+3+A@mail.gmail.com>
2018-05-28 12:50                                                                 ` Stanislaw Gruszka
2018-05-28 13:54                                                                   ` Daniel Golle
2018-08-15 11:40                                                                   ` Stanislaw Gruszka
2018-08-15 22:35                                                                     ` Daniel Golle
2018-08-16 11:01                                                                       ` Stanislaw Gruszka
     [not found]                                                                         ` <DM5PR02MB365669D5E9F2DE20DAE4CB7AD43E0@DM5PR02MB3656.namprd02.prod.outlook.com>
2018-08-18 16:08                                                                           ` Daniel Golle
2018-08-20 12:20                                                                             ` Stanislaw Gruszka
2018-08-24 13:02                                                                               ` Stanislaw Gruszka
2018-03-28 18:13                                                 ` Stanislaw Gruszka
2018-03-07 15:47                                     ` Jamie Stuart
2018-03-07 23:30                                       ` Enrico Mioso
2018-03-07 23:31                                       ` Enrico Mioso
2018-03-08  9:39                                       ` Stanislaw Gruszka
2018-03-08 14:28                                         ` Enrico Mioso
2018-01-23 13:20                         ` Stanislaw Gruszka
2017-12-26 17:20   ` Enrico Mioso
2018-01-03 11:45     ` Stanislaw Gruszka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LNX.2.21.99.1712161924030.11214@localhost.localdomain \
    --to=mrkiko.rs@gmail.com \
    --cc=arnd@arndb.de \
    --cc=daniel@makrotopia.org \
    --cc=johannes.berg@intel.com \
    --cc=john@phrozen.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=nbd@nbd.name \
    --cc=sgruszka@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.