← Back to team overview

kernel-packages team mailing list archive

[Bug 1388416] Re: rt2x00usb_vendor_request: Error - vendor request * failed for offset * with error -110

 

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.

** Attachment added: "dmesg2.txt"
   https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388416/+attachment/4252129/+files/dmesg2.txt

-- 
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1388416

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

Status in “linux” package in Ubuntu:
  Incomplete

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1388416/+subscriptions


References