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

Selim T. Erdogan selim at alumni.cs.utexas.edu
Thu Jan 19 12:02:38 AEDT 2012


Hello,

I'm getting many messages saying I should file a bug report at 
the project website:
---------------------------
(these keep repeating:)

[143534.884738] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full 
queue 0.
[143534.884750] Please file bug report to http://rt2x00.serialmonkey.com.
[143534.884815] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full 
queue 1.
[143534.884827] Please file bug report to http://rt2x00.serialmonkey.com.
----------------------------

I couldn't find a bug page right away so I thought I would write
to this list.  (Is there a better place to file the bug?)

There are two rt2x00 devices in this Averatec 3250 laptop.  

One is an rt2500 mini-pci card that came with the computer, 
recognized as wlan0.  lspci shows:
00:09.0 Network controller: Ralink corp. RT2500 Wireless 802.11bg (rev 01)

I suspect the error is from this first device, but I don't know for sure.
Would phy0 and wlan0 be related?.  Right now I am still connected, 
using the other device, according to Network Manager.

The second is a tiny usb "button-sized" rt2800-type device that I somebody 
on this list wrote about a couple of months ago:
http://www.dealextreme.com/p/ultra-mini-nano-usb-2-0-150mbps-802-11b-g-n-wifi-wlan-wireless-network-adapter-white-67532
lsusb shows:
Bus 001 Device 002: 148f:5370 Ralink Technology, Corp. RT5370 Wireless Adapter

(I got the second device recently, hoping it might have better range than 
the first.)

I am using debian sid.  uname -a shows:
Linux bodrum 3.1.0-1-686-pae #1 SMP Tue Jan 10 05:42:54 UTC 2012 i686 GNU/Linux

The modules I have loaded are: (lsmod|grep rt2)
rt2800usb              17546  0 
rt2800lib              39000  1 rt2800usb
rt2x00usb              13384  1 rt2800usb
rt2500pci              17973  0 
rt2x00pci              12768  1 rt2500pci
rt2x00lib              29063  5 rt2800usb,rt2800lib,rt2x00usb,rt2500pci,rt2x00pci
mac80211              166082  4 rt2800lib,rt2x00usb,rt2x00pci,rt2x00lib
cfg80211              113073  2 rt2x00lib,mac80211
eeprom_93cx6           12423  1 rt2500pci
crc_ccitt              12331  2 rt2800lib,irda
usbcore               100005  5 rt2800usb,rt2x00usb,uhci_hcd,ehci_hcd

I don't know how relevant this may be, but dmesg has some other errors
before the above errors started:
----------------------------
(actually, there were many more lines of the frame dropping error below) 

[120745.364145] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[120803.316218] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 0.
[121991.875466] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 1.
[125591.888542] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 1.
[129191.930331] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 1.
[132791.974817] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 1.
[136392.018552] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 1.
[139992.064522] phy0 -> rt2x00queue_write_tx_frame: Error - Dropping frame due to full tx queue 1.
[142830.707637] agpgart-via 0000:00:00.0: AGP 3.5 bridge
[142830.707691] agpgart: BIOS bug. AGP bridge claims to only support x4 rateFixing up support for x2 & x1
[142830.707717] agpgart-via 0000:00:00.0: bridge is in legacy mode, falling back to 2.x
[142830.707746] agpgart-via 0000:00:00.0: putting AGP V2 device into 4x mode
[142830.707889] pci 0000:01:00.0: putting AGP V2 device into 4x mode
[143182.269874] ADDRCONF(NETDEV_UP): wlan0: link is not ready
[143182.725947] ADDRCONF(NETDEV_UP): wlan1: link is not ready
[143182.903990] via-rhine 0000:00:12.0: eth0: link down
[143182.905745] ADDRCONF(NETDEV_UP): eth0: link is not ready
[143185.124115] wlan0: Selected IBSS BSSID fa:e8:16:97:1c:0c based on configured SSID
[143185.128249] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 1.
[143185.128262] Please file bug report to http://rt2x00.serialmonkey.com.
[143185.167243] wlan0: No active IBSS STAs - trying to scan for other IBSS networks with same SSID (merge)
[143185.220184] phy0 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 0.
[143185.220198] Please file bug report to http://rt2x00.serialmonkey.com.
----------------------------

Just before noticing the errors that said "file a bug report," I logged 
out of Gnome and then went to one of the virtual consoles to update my 
system.  After updating, I saw the errors in the virtual console.
I don't know if logging out caused Network Manager to do something
to the network connection but I don't think the connection was dropped.
(I had actually downloaded the updates earlier but it still tries to
connect to the servers to check for bugs/changes right before installing
and it should give an error if it can't connect.)  The agpart messages 
above might be from switching to the virtual console.  I don't know.

Let me know if I can provide any more info, or if I should file this
bug somewhere else.

Thanks,
Selim 




More information about the users mailing list