07d1:3c07 rt73 usb wireless locks up

Bug #999129 reported by Stuart Bishop
28
This bug affects 5 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Occasionally, normally under heavy network load, my wireless network connection locks up (DLink DWA-110 wireless usb stick, rt73 chipset based). Network manager indicator shows no problem, but I'm unable to ping my router. If I ask Network Manager to disconnect, the icon changes but nothing else does and it will not reconnect. At this point, shutdown will fail to complete requiring a power cycle.

kern.log contains the following, common to similar problems with this chipset over the last few years. This bug may well be a duplicate, but the existing bugs have become a mess and unhelpful so opening a fresh bug.

May 14 19:29:17 aargh kernel: [16220.856062] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -110.
May 14 19:30:07 aargh kernel: [16270.856163] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -110.
May 14 19:30:57 aargh kernel: [16320.856141] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x302c with error -110.
May 14 19:31:47 aargh kernel: [16370.856123] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x302c with error -110.
May 14 19:32:37 aargh kernel: [16420.856101] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x302c with error -110.
May 14 19:33:27 aargh kernel: [16470.856086] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x01 failed for offset 0x0000 with error -110.
May 14 19:34:17 aargh kernel: [16520.856065] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
May 14 19:35:07 aargh kernel: [16570.856051] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
May 14 19:35:57 aargh kernel: [16620.856165] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
May 14 19:36:47 aargh kernel: [16670.856148] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
May 14 19:36:56 aargh kernel: [16680.284020] INFO: task kworker/u:3:46 blocked for more than 120 seconds.
May 14 19:36:56 aargh kernel: [16680.284023] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 14 19:36:56 aargh kernel: [16680.284026] kworker/u:3 D ffffffff81806240 0 46 2 0x00000000
May 14 19:36:56 aargh kernel: [16680.284032] ffff880123c4dc20 0000000000000046 ffffffff00000000 0000000000000001
May 14 19:36:56 aargh kernel: [16680.284037] ffff880123c4dfd8 ffff880123c4dfd8 ffff880123c4dfd8 0000000000013780
May 14 19:36:56 aargh kernel: [16680.284041] ffffffff81c0d020 ffff880125ddc4d0 00000000000003fc ffff880108d12190
May 14 19:36:56 aargh kernel: [16680.284046] Call Trace:
May 14 19:36:56 aargh kernel: [16680.284054] [<ffffffff8165a55f>] schedule+0x3f/0x60
May 14 19:36:56 aargh kernel: [16680.284058] [<ffffffff8165b367>] __mutex_lock_slowpath+0xd7/0x150
May 14 19:36:56 aargh kernel: [16680.284061] [<ffffffff8165af7a>] mutex_lock+0x2a/0x50
May 14 19:36:56 aargh kernel: [16680.284074] [<ffffffffa0c91f23>] rt2x00usb_vendor_request_buff+0x43/0xd0 [rt2x00usb]
May 14 19:36:56 aargh kernel: [16680.284081] [<ffffffffa0ccc760>] ? rt2x00lib_suspend+0x50/0x50 [rt2x00lib]
May 14 19:36:56 aargh kernel: [16680.284087] [<ffffffffa0c9f2e0>] rt73usb_set_state+0x50/0x150 [rt73usb]
May 14 19:36:56 aargh kernel: [16680.284092] [<ffffffffa0ca0a5d>] rt73usb_set_device_state+0x12d/0x160 [rt73usb]
May 14 19:36:56 aargh kernel: [16680.284097] [<ffffffff8105617a>] ? finish_task_switch+0x4a/0xf0
May 14 19:36:56 aargh kernel: [16680.284103] [<ffffffffa0ccc7a2>] rt2x00lib_autowakeup+0x42/0xa0 [rt2x00lib]
May 14 19:36:56 aargh kernel: [16680.284107] [<ffffffff81084e2a>] process_one_work+0x11a/0x480
May 14 19:36:56 aargh kernel: [16680.284111] [<ffffffff81085bd4>] worker_thread+0x164/0x370
May 14 19:36:56 aargh kernel: [16680.284114] [<ffffffff81085a70>] ? manage_workers.isra.29+0x130/0x130
May 14 19:36:56 aargh kernel: [16680.284118] [<ffffffff8108a42c>] kthread+0x8c/0xa0
May 14 19:36:56 aargh kernel: [16680.284122] [<ffffffff81666bf4>] kernel_thread_helper+0x4/0x10
May 14 19:36:56 aargh kernel: [16680.284126] [<ffffffff8108a3a0>] ? flush_kthread_worker+0xa0/0xa0
May 14 19:36:56 aargh kernel: [16680.284129] [<ffffffff81666bf0>] ? gs_change+0x13/0x13
May 14 19:37:37 aargh kernel: [16720.856135] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
May 14 19:38:27 aargh kernel: [16770.856129] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.
May 14 19:38:56 aargh kernel: [16800.284055] INFO: task kworker/u:3:46 blocked for more than 120 seconds.
May 14 19:38:56 aargh kernel: [16800.284058] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs" disables this message.
May 14 19:38:56 aargh kernel: [16800.284061] kworker/u:3 D ffffffff81806240 0 46 2 0x00000000
May 14 19:38:56 aargh kernel: [16800.284067] ffff880123c4dc20 0000000000000046 ffffffff00000000 0000000000000001
May 14 19:38:56 aargh kernel: [16800.284072] ffff880123c4dfd8 ffff880123c4dfd8 ffff880123c4dfd8 0000000000013780
May 14 19:38:56 aargh kernel: [16800.284077] ffffffff81c0d020 ffff880125ddc4d0 00000000000003fc ffff880108d12190
May 14 19:38:56 aargh kernel: [16800.284081] Call Trace:
May 14 19:38:56 aargh kernel: [16800.284090] [<ffffffff8165a55f>] schedule+0x3f/0x60
May 14 19:38:56 aargh kernel: [16800.284093] [<ffffffff8165b367>] __mutex_lock_slowpath+0xd7/0x150
May 14 19:38:56 aargh kernel: [16800.284097] [<ffffffff8165af7a>] mutex_lock+0x2a/0x50
May 14 19:38:56 aargh kernel: [16800.284111] [<ffffffffa0c91f23>] rt2x00usb_vendor_request_buff+0x43/0xd0 [rt2x00usb]
May 14 19:38:56 aargh kernel: [16800.284119] [<ffffffffa0ccc760>] ? rt2x00lib_suspend+0x50/0x50 [rt2x00lib]
May 14 19:38:56 aargh kernel: [16800.284125] [<ffffffffa0c9f2e0>] rt73usb_set_state+0x50/0x150 [rt73usb]
May 14 19:38:56 aargh kernel: [16800.284131] [<ffffffffa0ca0a5d>] rt73usb_set_device_state+0x12d/0x160 [rt73usb]
May 14 19:38:56 aargh kernel: [16800.284136] [<ffffffff8105617a>] ? finish_task_switch+0x4a/0xf0
May 14 19:38:56 aargh kernel: [16800.284141] [<ffffffffa0ccc7a2>] rt2x00lib_autowakeup+0x42/0xa0 [rt2x00lib]
May 14 19:38:56 aargh kernel: [16800.284146] [<ffffffff81084e2a>] process_one_work+0x11a/0x480
May 14 19:38:56 aargh kernel: [16800.284149] [<ffffffff81085bd4>] worker_thread+0x164/0x370
May 14 19:38:56 aargh kernel: [16800.284153] [<ffffffff81085a70>] ? manage_workers.isra.29+0x130/0x130
May 14 19:38:56 aargh kernel: [16800.284157] [<ffffffff8108a42c>] kthread+0x8c/0xa0
May 14 19:38:56 aargh kernel: [16800.284161] [<ffffffff81666bf4>] kernel_thread_helper+0x4/0x10
May 14 19:38:56 aargh kernel: [16800.284165] [<ffffffff8108a3a0>] ? flush_kthread_worker+0xa0/0xa0
May 14 19:38:56 aargh kernel: [16800.284168] [<ffffffff81666bf0>] ? gs_change+0x13/0x13

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: linux-image-3.2.0-24-generic 3.2.0-24.37
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: stub 2227 F.... pulseaudio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 44'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043829f,00100002'
   Controls : 45
   Simple ctrls : 21
Date: Mon May 14 20:30:49 2012
HibernationDevice: RESUME=UUID=7896cb2f-32d5-4d77-9989-909f17a169ad
MachineType: System manufacturer P5K SE
ProcEnviron:
 LANGUAGE=en_AU:en
 TERM=xterm
 PATH=(custom, user)
 LANG=en_AU.UTF-8
 SHELL=/bin/bash
ProcFB:

ProcKernelCmdLine: root=UUID=f60f3407-1ba0-4ffd-a6a7-b734d943b3c5 ro quiet splash
RelatedPackageVersions:
 linux-restricted-modules-3.2.0-24-generic N/A
 linux-backports-modules-3.2.0-24-generic N/A
 linux-firmware 1.79
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
SourcePackage: linux
UpgradeStatus: Upgraded to precise on 2012-04-27 (17 days ago)
WpaSupplicantLog:

dmi.bios.date: 01/02/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0901
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K SE
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr0901:bd01/02/2008:svnSystemmanufacturer:pnP5KSE:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5KSE:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K SE
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Stuart Bishop (stub) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Stuart Bishop (stub) wrote :

To avoid power cycling, a work around is to unplug the usb stick and plug it in again. Without disconnecting and reconnecting the device, attempts to reconnect just seem to make the situation worse.

Revision history for this message
Joseph Salisbury (jsalisbury) wrote :

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v3.4kernel[1] (Not a kernel in the daily directory). Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag(Only that one tag, please leave the other tags). This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text.

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.4-rc7-precise/

Changed in linux (Ubuntu):
importance: Undecided → Medium
tags: added: needs-upstream-testing
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marcelo Guedes (marcelo-guedes) wrote :

This issue came since Ubuntu 11.04 when the Linux stable kernel stopped to support ndiswrapper for dwa-110 Windows drivers and started to make use of a new rt73usb driver version. This new driver never worked as it should. No one solved it properly for years. It's important to say that it is not related to the hardware or ISP. In my case, I have dual boot and the DWA-110 works perfectly on Windows.

Some links:
* http://askubuntu.com/questions/95331/how-to-troubleshoot-my-unstable-wireless-connection/138135#138135
* https://help.ubuntu.com/community/HardwareSupportComponentsWirelessNetworkCardsDlink (search for "DWA-110")
* Google not help too much. You only see solutions working in old Ubuntu versions: http://bit.ly/JUcmCw

I would be glad to have a solution here.

Revision history for this message
Marcelo Guedes (marcelo-guedes) wrote :

Hi.

The v3.4-rc7-precise is incomplete (there are only the linux-headers_XXX_all_XXX.deb, missing linux-header_XXX_generic_XXX.deb and linux-image_XXX_generic_XXX.deb files). I will do the suggested test using v3.4-rc6-precise.

Joseph Salisbury, do you think it's a problem?

Revision history for this message
Marcelo Guedes (marcelo-guedes) wrote :

Hi again.

I'm just installed v3.4-rc6-precise. I need to test it for some day but it seems pretty more stable for me. I can notice that a common delay on the beginning of the webpage load was gone. It's a good sign the upstream kernel changed something for good. HOWEVER, I need more time until a final conclusion. Give me some days in this new setup. I going to report again after.

One tip: I have a nvidia board and the driver stopped to work with v3.4-rc6-precise . To put it up again I did it:
$ sudo add-apt-repository ppa:ubuntu-x-swat/x-updates
$ sudo apt-get update
$ sudo apt-get install nvidia-current
After installed it, you need to reactive it on: Up-Right Engine Icon > System Settings... > Hardware (tab) > Additional Drivers. Select "NVIDIA accelerated graphics driver (version current) [Recommended]". Click in "Active". Wait and then, reboot your computer.

Everything seems fine here and I'm happy now.

Revision history for this message
Marcelo Guedes (marcelo-guedes) wrote :

...
Forget it. The behavior is a little bit different but the main issue remains. The DWA-110 just frozen here. I read it in /var/log/kern.log :

May 17 20:12:10 capella kernel: [ 1214.052166] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -110.
May 17 20:13:00 capella kernel: [ 1264.052056] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -110.
May 17 20:13:50 capella kernel: [ 1314.052198] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110.

Ideas?

tags: added: kernel-bug-exists-upstream
removed: needs-upstream-testing
Revision history for this message
Marcelo Guedes (marcelo-guedes) wrote :

$ uname -ra
Linux capella 3.4.0-030400rc6-generic #201205061835 SMP Sun May 6 22:36:08 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Marcelo Guedes, if you are having a problem in Ubuntu, please file a new report by executing the following via the Terminal and feel free to subscribe me to it:
ubuntu-bug linux

Thanks!

summary: - rt73 usb wireless locks up
+ 07d1:3c07 rt73 usb wireless locks up
tags: added: needs-upstream-testing
removed: kernel-bug-exists-upstream
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
Revision history for this message
falko (falko.lab) wrote :

Still relevant for me:

Distributor ID: Ubuntu
Description: Ubuntu 12.04.2 LTS
Release: 12.04
Codename: precise

uname -ra
Linux falko-home 3.2.0-48-generic #74-Ubuntu SMP Thu Jun 6 19:43:26 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux

dmesg
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x040c with error -110.

Freezes gui until unplug the usb stick and plug it in again

Revision history for this message
penalvch (penalvch) wrote :

falko, if you have a bug in Ubuntu, the Ubuntu Kernel team, Ubuntu Bug Control team, and Ubuntu Bug Squad would like you to please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Kernel team article:
https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports

the Ubuntu Bug Control team and Ubuntu Bug Squad team article:
https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue

and Ubuntu Community article:
https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Please note, not filing a new report would delay your problem being addressed as quickly as possible.

Thank you for your understanding.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.