FS#22412 - Ralink RT2501/RT2573 USB Wireless Adapter crashes kernel 2.6.37
Attached to Project:
Arch Linux
Opened by Eric (zebulon) - Thursday, 13 January 2011, 11:13 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 May 2011, 20:08 GMT
Opened by Eric (zebulon) - Thursday, 13 January 2011, 11:13 GMT
Last edited by Andrea Scarpino (BaSh) - Wednesday, 04 May 2011, 20:08 GMT
|
Details
Description:
I experience very frequent but unexpected (difficult to reproduce) lockups with kernel 2.6.37 and a USB Wifi adapter Ralink RT2501/RT2573. The computer freezes with no possible recovery other than hard reset. This happens especially when navigating on a video stream on Youtube in Firefox, but may happen any time. This was difficult to diagnose, since no message was left in the logs, but am now pretty sure to have identified the issue because: - the crashes do not happen if I let the video load entirely, then remove the Wifi adapter, then watch it and navigate through it - system has been stable for long period of time without the wifi adapter - this issue starts to be reported for other distributions (see https://bugs.launchpad.net/ubuntu/+source/linux/+bug/673682 Strangely, this user reports a call trace, which I do not get) lsusb returns: Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter System is a i7 870 with Gigabyte GA-P55M-UB2 motherboard, Nvidia GTX260. Kernel 2.6.37-1 and nvidia proprietary drivers are installed. This occurs with both binary kernel in testing or compiled kernel from AUR. Suggestion: This could require newer compat-wireless drivers in kernel 2.6.37 to be fixed. I will see with rt2x00 developers if they are aware of the problem. |
This task depends upon
Closed by Andrea Scarpino (BaSh)
Wednesday, 04 May 2011, 20:08 GMT
Reason for closing: Fixed
Additional comments about closing: kernel26 2.6.38.5-1
Wednesday, 04 May 2011, 20:08 GMT
Reason for closing: Fixed
Additional comments about closing: kernel26 2.6.38.5-1
Other threads about rt73usb crashes are also reported http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2011-February/003109.html
I have also tried the kernel 2.6.37.2-1 but the problem remains :(
I lost connection after a few minutes and got this in dmesg :
Mar 29 18:34:39 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -110.
Mar 29 18:35:29 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -110.
Mar 29 18:36:19 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
Mar 29 18:37:09 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -110.
Mar 29 18:37:59 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x040c with error -110.
Mar 29 18:38:22 localhost kernel: phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x040c with error -19.
I have blacklisted rt2500usb module and rebooted. This seems working.
I will post a new comment if I get another problem or crash.
It's made worse by the fact that I can't connect at all on the LTS kernel, but that's not relevant here.
same problem. I'll try kernel 2.6.38
It just fixes the "phy0 -> rt2x00usb_vendor_request" error. I get no crash/freeze but I get disconnected after a few minutes.
wlan0 disappears from up interfaces (with "ifconfig") and if I try to re-up the interface then scan with "iwlist scan", it shows no result. No error in "dmesg".
I will try the kernel 2.6.38.2 next monday.
But it seems there is no change between 2.6.38.1 and 2.6.38.2 for rt2x00 driver : http://goo.gl/U50D3 http://goo.gl/9yJgx
I would say there is still an issue, but severity should be now downgraded.
It seems OK : no crash or deconnection.
I have only blacklisted rt2500usb module to avoid the "phy0 -> rt2x00usb_vendor_request: Error".
I will continue to use this kernel (or upgrade to 2.6.38-3 when it go to core repo) and report any problem, disconnection or crash.