rt2x00usb_vendor_request: Error - vendor request * failed for offset * with error -110

Bug #1388416 reported by Adam Hallgat
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

Using Ubuntu 14.10 (64bit) the following error happens in every few days:

Suddenly the network connection disconnects and locks up every process which is connected to networking. The only way is to reset the whole computer.

If i log in to tty i get the following error in every half minutes or so:

ieee80211 phy0: rt2x00usb_vendor_request: Error - vendor request 0x07 failed for offset 0x3090 with error -110

Also i get some other messages about some application being blocked for more than 120 seconds. The applications are the following:

- network manager,
- wpa_supplicant,
- dropbox,
- dns res~ver, dns resolver (for some this is mentioned twice like this)
- kworker

I use Ubuntu on a Nec Versa One (M370) laptop since Ubuntu 9.10. I have always had similar driver issues with my built-in wireless card. The module which throws the error changed though.

From 9.10 to 13.* i got the same error from the rt73usb module.
Now I'm using Ubuntu 14.10 (64bit) and now i get this error from the rt2x00usb module. (this is used by the rt73usb mod).

This bug affects me as long as i have been using Ubuntu. I guess this driver issue might depend on the manufacturer, and hard to fix, but at least I would like to see a workaround to somehow solve this issue without rebooting.

ProblemType: Bug
DistroRelease: Ubuntu 14.10
Package: linux-firmware 1.138
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Uname: Linux 3.16.0-24-generic x86_64
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Date: Sat Nov 1 18:41:22 2014
Dependencies:

InstallationDate: Installed on 2014-06-29 (124 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to utopic on 2014-10-19 (13 days ago)
---
ApportVersion: 2.14.7-0ubuntu8
Architecture: amd64
Dependencies:

DistroRelease: Ubuntu 14.10
InstallationDate: Installed on 2014-06-29 (124 days ago)
InstallationMedia: Xubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140416.2)
Package: linux-firmware 1.138
PackageArchitecture: all
ProcVersionSignature: Ubuntu 3.16.0-24.32-generic 3.16.4
Tags: utopic
Uname: Linux 3.16.0-24-generic x86_64
UpgradeStatus: Upgraded to utopic on 2014-10-19 (13 days ago)
UserGroups: adm cdrom dip lpadmin netdev plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Adam Hallgat (hallgat) wrote :
tags: added: apport-collected
description: updated
Revision history for this message
Adam Hallgat (hallgat) wrote : ProcEnviron.txt

apport information

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.18 kernel[0].

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.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v3.18-rc3-vivid/

affects: linux-firmware (Ubuntu) → linux (Ubuntu)
Changed in linux (Ubuntu):
status: New → Incomplete
importance: Undecided → Medium
Revision history for this message
Adam Hallgat (hallgat) wrote :

Ok, I install the following:

linux-headers-3.18.0-031800rc3_3.18.0-031800rc3.201411022335_all.deb
linux-headers-3.18.0-031800rc3-generic_3.18.0-031800rc3.201411022335_amd64.deb
linux-image-3.18.0-031800rc3-generic_3.18.0-031800rc3.201411022335_amd64.deb

Since I cannot reproduce this bug every single day, it might take a week to experience it again.

Revision history for this message
Adam Hallgat (hallgat) wrote :

I didn't even had to wait for 1 hour. All I did was just to start transmission with one single Xubuntu torrent.

uname -a
Linux hallgat-NEC-VERSA-ONE 3.18.0-031800rc3-generic #201411022335 SMP Sun Nov 2 23:36:52 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

I attach the first dmesg. It's until the occurence of the bug.

Revision history for this message
Adam Hallgat (hallgat) wrote :

I actually managed to restart the network with

sudo rmmod rt73usb
sudo modprobe rt73usb
(as the rt2x00usb is used by this module)

dmesg2 shows the occurence of the bug, and the system messages after the mod was removed and added again.

Revision history for this message
Adam Hallgat (hallgat) wrote :
Revision history for this message
Adam Hallgat (hallgat) wrote :
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
Adam Hallgat (hallgat) wrote :

Still happening on
3.16.0-31-generic #41-Ubuntu SMP Tue Feb 10 15:24:04 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

Happens very often if torrent is running. After logout the lightdm is not responsible.
This dmesg log shows the error. I tried to disconnect from the network several times, then pressed the wifi switch on my laptop. They did nothing, I only got the usual "Disconnecting the device was unsuccesful (4) Didn't receive a reply" which I always get when the wifi locks up.

Yngve Halmø (yhalmoe)
Changed in linux (Ubuntu):
status: Expired → Confirmed
Revision history for this message
Yngve Halmø (yhalmoe) wrote :

I am on 14.04 LTS and have exactly the same problem. Works fine for some undetermined amount of time, but then several processes seem to freeze and the message ieee80211 phy0: rt2x00usb_vendor_request: Error - vendor request 0x07 failed for offset 0x308c with error -110 (the offset is slightly different than the reporter's, but otherwise identical). The message seems to be printed every 50 seconds.

I am using an old 54Mbit USB wifi dongle.

In between these requests, when the error has occured, I also sometimes get:

ieee80211 phy0: rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x0000308c, value=0xffff8800.

If I use bittorrent, the problem seems to occur much faster after a reboot, as the reporter suggested.

Revision history for this message
Adam Hallgat (hallgat) wrote :

Lucky you. In my computer, wifi is built in. :)

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.