[rt2x00-users] rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2

Hasan Rashid hrashad at avionica.com
Wed Apr 6 06:46:22 EST 2011


Helmut,

It seems to hold. Despite the following, I had continuous link to the
clients.


[  466.682905] phy0 -> rt2x00pci_regbusy_read: Error - Indirect register
access failed: off
set=0x00007010, value=0xffffff03
[  466.705371] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 0 -
CWmin: 3, CWmax: 4
, Aifs: 2, TXop: 102.
[  466.705391] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 1 -
CWmin: 4, CWmax: 5
, Aifs: 2, TXop: 188.
[  466.705408] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 2 -
CWmin: 5, CWmax: 1
0, Aifs: 3, TXop: 0.
[  466.705425] phy0 -> rt2x00mac_conf_tx: Info - Configured TX queue 3 -
CWmin: 5, CWmax: 1
0, Aifs: 7, TXop: 0.
[  477.368166] wlan0: no IPv6 routers present
[ 1174.042898] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at
non-free entry in the
 non-full queue 2.
[ 1174.042905] Please file bug report to http://rt2x00.serialmonkey.com.
[ 1471.752904] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at
non-free entry in the
 non-full queue 2.
[ 1471.752910] Please file bug report to http://rt2x00.serialmonkey.com.
qid     flags           count   limit   length  index   dma done
done
14      0x00000001      457843  128     0       115     115
115
0       0x00000001      3439    64      0       47      0
47
1       0x00000001      0       64      0       0       0
0
2       0x00000001      568368  64      43      27      0
48
3       0x00000001      0       64      0       0       0
0
16      0x00000001      0       8       0       0       0
0

Thank You!

Hasan R. 
 

-----Original Message-----
From: Helmut Schaa [mailto:helmut.schaa at googlemail.com] 
Sent: Tuesday, April 05, 2011 2:02 PM
To: Hasan Rashid
Cc: users at rt2x00.serialmonkey.com
Subject: Re: [rt2x00-users] rt2x00queue_write_tx_frame: Error - Arrived
at non-free entry in the non-full queue 2

Am Dienstag, 5. April 2011 schrieb Hasan Rashid:
> 
> It did it again, I was unable to ping any of the clients when this 
> happened. Disregard the time stamps the time on the host machine is 
> inaccurate.

Did you have the patch applied I sent a few days ago?

Helmut
This communication contains information that may be confidential or privileged. The information is solely intended for the use of the addressee. If you are not the intended recipient, be advised that any disclosure, copy, distribution, or use of the contents of this communication is prohibited. If you have received this communication in
error, please immediately notify the sender by telephone or by electronic mail.



More information about the users mailing list