rt2x00.serialmonkey.com

That is impossible! Ive got this error








What should i post to help you guys debug problem?
Cheers

I get this error on 2.6.32 as of today.

This is a Debian/Squeeze installation with the kernel version:


Module version(s):



The hardware is a USB dongle, and the machine acts as an Access Point via hostapd. I also notice that sometimes the driver dies completely, taking the card with it, and the only solution is to take it out and reinsert, modprobe doesn't do anything in that case. Maybe the issues are related...

I can supply more information if needed.

Just to confirm:

Ubuntu 10.04, 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 19:31:57 UTC 2010 x86_64 GNU/Linux
I have the same, still:

$ dmesg | grep rt
[ 11.562565] ppdev: user-space parallel port driver
[ 11.638008] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
[ 11.638348] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
[ 11.638684] usbcore: registered new interface driver rt2500usb
[ 11.798731] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[ 11.915122] Registered led device: rt73usb-phy1::radio
[ 11.915144] Registered led device: rt73usb-phy1::assoc
[ 11.915169] Registered led device: rt73usb-phy1::quality
[ 11.915689] usbcore: registered new interface driver rt73usb
[ 13.887613] rt73usb 2-2:1.0: firmware: requesting rt73.bin
[ 1252.586950] phy1 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
[ 1252.586956] Please file bug report to http://rt2x00.serialmonkey.com.
[21262.061986] phy1 -> rt2x00queue_write_tx_frame: Error - Arrived at non-free entry in the non-full queue 2.
[21262.061991] Please file bug report to http://rt2x00.serialmonkey.com.
[97518.602204] (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)

what I have is a TP-Link TL-WN321G.

So what it does, are frequently disconnects, and mostly some crap visible in ping:
4.5 ms
121 ms
1247 ms
6442 ms
5873 ms
5227 ms
1174 ms
... and so forth; with a signal strength of 88%, while just another box does pretty well.

If there is anything I can do to help getting this bug out of the kernel, please, rope in my help!

Uwe

Unfortunately, this is still happening in my 2.6.38-2-amd64 kernel. The same card was working fine with an earlier 32-bit kernel. Is rt2x00 support dead? Could anyone point to the original fix for the earlier kernels so we can have a look at it?

Thanks for your work anyway, rt2x00 has been very useful to me personally..

_________________
--Cengiz

This bug was fixed again for kernels >2.6.38-12.51 and >3.0.0-12.19 with patch: http://rt2x00.serialmonkey.com/pipermai ... 03947.html

rt2x00 git tree no longer exists because it has been merged into the official wireless-testing development.

_________________
--Cengiz