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

Stanislaw Gruszka sgruszka at redhat.com
Fri Jan 20 19:51:55 AEDT 2012


On Wed, Jan 18, 2012 at 07:02:38PM -0600, Selim T. Erdogan wrote:
> 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 think these messages come from rt2500. I have one similar fedora
bug report: https://bugzilla.redhat.com/show_bug.cgi?id=753648

Problem seems to be related with rt2x00pci driver transition to using
tasklets, i.e. it is 2.6.38 -> 2.6.39 regression. It could be workaround
by disabling power save:

iw dev wlan0 set power_save off

See

iw dev

output to check if wlan0 corresponds to phy0. You then can check if
by ethtool wlan0 if phy0 is really rt2500pci.

Stanislaw





More information about the users mailing list