rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset

Bug #362875 reported by Shahar Or on 2009-04-17
206
This bug affects 39 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned
rt2x00 (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: linux-firmware

Dear friends,

[24225.012753] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
[24225.017901] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71.
[24225.022279] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
[24226.005773] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71.
[24226.011307] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71.
[24226.015147] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
[24226.020486] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71.
[24226.024151] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
[24227.003532] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c0 with error -71.
[24227.007269] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x30c4 with error -71.
[24227.020153] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71.
[24227.023895] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -71.
[24227.027645] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -71.

This is an example of the message I'm continually getting.

ID 148f:2671 Ralink Technology, Corp. RT2601USB Wireless Adapter

Many blessings.

ProblemType: Bug
Architecture: i386
Dependencies:

DistroRelease: Ubuntu 8.10
Package: linux-restricted-modules None [modified: /var/lib/dpkg/info/linux-restricted-modules.list]
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/X11R6/bin
 LANG=en_US.UTF-8
SourcePackage: linux-meta
Uname: Linux 2.6.27-7-generic i686

crashsystems (crashsystems) wrote :

I am experiencing what I think is the same problem with a machine running 9.10 Alpha 5 i386. The wireless adapter is a Linksys WUSB54G version 4.

I'm seeing the following two lines repeating in my syslog:
phy0 -> rt2500usb_regbusy_readbusy_read: Error - Indirect register access failed: offset=0x000004d0, value=0x0000f5ed
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x04d0 with error - 110

I know nothing about doing kernel related debugging, so if someone could give me advice on how to gather useful information on this bug, I'd appreciate it.

I'm getting similar messages. They come at (seemingly) random times when I'm not using the computer. Here's a bit from my syslog:

Nov 9 21:50:22 AMD-Server kernel: [ 8121.930054] usb 1-3: USB disconnect, address 2
Nov 9 21:50:22 AMD-Server kernel: [ 8121.940247] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3040 with error -19.
Nov 9 21:50:22 AMD-Server kernel: [ 8121.940292] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -19.
Nov 9 21:50:22 AMD-Server kernel: [ 8121.940327] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3028 with error -19.
Nov 9 21:50:22 AMD-Server kernel: [ 8121.940361] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3064 with error -19.
Nov 9 21:50:22 AMD-Server kernel: [ 8121.940396] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.

My adapter is (lsusb):
ASUSTek Computer, Inc. WL-167G v2 802.11g Adapter [ralink]

I'm on Ubuntu (Server) 9.10. I believe I've had very similar problems on 9.04 as well.

From the looks of the first line shown, my system thinks that the USB adapter is being disconnected. I hadn't touched anything, but the connection was then lost, so I had to "ifdown" and "ifup" my wlan0.

Hello,

  I am using Ubuntu karmic with latest kernel updates (from karmic-proposed), I am also getting those errors, and the USB WiFi adapter doesn't show any access points to connect to.

Download full text (5.2 KiB)

Actually I get those errors when unplugging the USB adapter, here they are:

[28487.308636] usb 2-2: USB disconnect, address 6
[28487.309069] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1004 with error -19.
[28487.309082] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1004 with error -19.
[28487.309093] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[28487.309102] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x0208 with error -19.
[28487.309112] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1004 with error -19.
[28487.309121] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1204 with error -19.
[28487.309130] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x1328 with error -19.
[28487.309140] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[28487.316057] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[28487.324104] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[28487.332092] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[28487.340657] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0208 with error -19.
[28487.348066] phy1 -> rt2800usb_wait_wpdma_ready: Error - WPDMA TX/RX busy, aborting.
[28487.348085] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x0c failed for offset 0x0000 with error -19.
[28487.348112] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348221] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348329] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348438] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348546] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348653] phy1 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf713bd78
[28487.348665] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348773] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348881] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.348989] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.349098] phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x7010 with error -19.
[28487.349205] phy1 -> rt2x00usb_regbusy_read: Error - Indirect register access failed: offset=0x00007010, value=0xf713bd80
[28487.349441] phy1 -> r...

Read more...

The adapter (from lsusb output):
Bus 002 Device 007: ID 07d1:3c0d D-Link System

affects: linux-firmware (Ubuntu) → linux (Ubuntu)
Jeremy Foshee (jeremyfoshee) wrote :

Hi Shahar,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Luca Ferretti (elle.uca) wrote :

Jeremy, I'm experiencing similar issue in 10.04 (and never seen in 9.10). The wireless device is a D-Link DWA-111. Removing and re-pluggin again this USB adapter, it no longer works, requiring a reboot (while in 9.10 I was able to remove and replug again and again).

Do I've to try the mainline kernel too?

PS after re-plugging, dmesg says:
[ 1348.179246] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x09 failed for offset 0x0000 with error -108.
[ 1348.179256] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3000 with error -108.
[ 1348.179259] phy2 -> rt73usb_init_eeprom: Error - Invalid RT chipset detected.
[ 1348.179261] phy2 -> rt2x00lib_probe_dev: Error - Failed to allocate device.

Luca Ferretti (elle.uca) wrote :

Hmmm, it seems that bad messages and bad beahavior exist only using the kernel for 10.04 currently in proposed. Using the kernel in main everything goes fine. Should I report this? And how?

Ulf Bergkvist (ulf-bergkvist) wrote :

I am very new using Linux Ubuntu but I have a similar problem (at lest I think so...)getting the message below when loggin in:
May 5 19:59:41 ulf-desktop kernel: [ 146.264138] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x09 failed for offset 0x0000 with error -110.
May 5 19:59:44 ulf-desktop kernel: [ 148.764124] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x04d0 with error -110.
May 5 19:59:44 ulf-desktop kernel: [ 148.795873] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x04ce with error -32.
May 5 19:59:46 ulf-desktop kernel: [ 151.292114] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x04d0 with error -110.
May 5 19:59:49 ulf-desktop kernel: [ 153.792106] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x04ce with error -110.
May 5 19:59:51 ulf-desktop kernel: [ 156.292096] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x0400 with error -110.
May 5 19:59:51 ulf-desktop kernel: [ 156.292153] phy0 -> rt2500usb_init_eeprom: Error - Invalid RT chipset detected.
May 5 19:59:51 ulf-desktop kernel: [ 156.292207] phy0 -> rt2x00lib_probe_dev: Error - Failed to allocate device.
May 5 19:59:51 ulf-desktop kernel: [ 156.292841] rndis_wlan 1-4:1.0: rndis indication: 0xc0010015
May 5 19:59:52 ulf-desktop kernel: [ 156.316473] rndis_wlan 1-4:1.0: rndis indication: 0xc0010015
May 5 19:59:52 ulf-desktop kernel: [ 156.340469] rndis_wlan 1-4:1.0: rndis indication: 0xc0010015
May 5 19:59:52 ulf-desktop kernel: [ 156.364471] rndis_wlan 1-4:1.0: rndis indication: 0xc0010015
May 5 19:59:52 ulf-desktop kernel: [ 156.388467] rndis_wlan 1-4:1.0: rndis indication: 0xc0010015
May 5 19:59:52 ulf-desktop kernel: [ 156.645093] rndis_wlan 1-4:1.0: rndis media disconnect
May 5 19:59:52 ulf-desktop kernel: [ 156.781624] wlan0: register 'rndis_wlan' at usb-0000:00:1d.7-4, Wireless RNDIS device, 00:11:50:7d:af:4c
May 5 19:59:52 ulf-desktop kernel: [ 156.781662] usbcore: registered new interface driver rndis_wlan
May 5 19:59:52 ulf-desktop kernel: [ 156.782331] usbcore: registered new interface driver rt2500usb

Using:
UDEV [1273085621.752807] add /devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/net/wlan0 (net)
UDEV_LOG=3
ACTION=add
DEVPATH=/devices/pci0000:00/0000:00:1d.7/usb1/1-4/1-4:1.0/net/wlan0
SUBSYSTEM=net
INTERFACE=wlan0
IFINDEX=3
SEQNUM=1464
ID_VENDOR=Broadcom
ID_VENDOR_ENC=Broadcom
ID_VENDOR_ID=050d
ID_MODEL=Belkin_High-Speed_Mode_Wireless_G_USB_Network_Adapter
ID_MODEL_ENC=Belkin\x20High-Speed\x20Mode\x20Wireless\x20G\x20USB\x20Network\x20Adapter
ID_MODEL_ID=7051
ID_REVISION=0006
ID_SERIAL=Broadcom_Belkin_High-Speed_Mode_Wireless_G_USB_Network_Adapter_8057
ID_SERIAL_SHORT=8057
ID_TYPE=generic
ID_BUS=usb
ID_USB_INTERFACES=:0202ff:0a0000:
ID_USB_INTERFACE_NUM=00
ID_USB_DRIVER=rndis_wlan
ID_VENDOR_FROM_DATABASE=Belkin Components
ID_MODEL_FROM_DATABASE=F5D7051 54g USB Network Adapter

Help appreciated

Luca Ferretti (elle.uca) wrote :

This is strange. After 2.6.32-22 move from proposed to updates I've no more issues... :O

These bugs are probably related https://bugs.launchpad.net/ubuntu/+source/linux-backports-modules-2.6.28/+bug/372885 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/488909
I suffer from this bug, too. At some time connection is lost, NM icon continue displaying the last status, but I have to reboot
Attached is my whole dmesg (at line 830 the problem starts)
I'm on 10.04, kernel is 2.6.32-24-generic

It seems a firmeware (or kernel module) problem specific to this chip (my card is a dlink usb adapter)

zubin (zubinkavarana) wrote :

I am facing the same issue/similar, and can recreate this at will.

Hardware: Desktop PC on AMD Phenom II X4 940 with 4GB RAM. Network connection is through a USB Wifi dongle Linksys WUSB54GC using a Ralink chipset (RT2500? http://ralink.rapla.net/). Internet connection is a 1 Mbps plan giving about 120kbps download speed.
Kernel: 2.6.32-24-generic (x86_64)

Issue: The Internet connection works great but gets disconnected on using torrent, in which case the USB dongle light will go off, Internet connection will stop working (no dropbox, no browser activity) even though the network indicator is showing connected.
Some points -
   1. Removing the dongle and pluggingt it back restores the connection.
   2. Normal net usage does not kill the net (dropbox, browser, youtube in many tabs, gwibber,skype, updates etc)
   3. The connection is invariably lost between 5 mins to a few hours after a torrent program is used (transmission or deluge)
   4. I started trying to fix this by googling the right settings for torrent - have changed number of connections, max download upload speed and turning off DHT but the problem persists.
   5. The log file viewer indicates a problem with the USB dongle drivers (attached logs)
   6. I googled around and found some forums that suggest blacklising the kernel modules rt2x00usb and rt2x00lib
(http://translate.google.com/translate?hl=en&sl=de&u=http://forum.ubuntuusers.de/post/2373162/&ei=XQiHTJ_bOIP0tgPK78SrCg&sa=X&oi=translate&ct=result&resnum=3&ved=0CCgQ7gEwAg&prev=/search%3Fq%3Drt2x00usb%2Bvendor%2Brequest:%2BError%2B-%2BVendor%2BRequest%2B0x07%2Bfailed%2Bfor%2Boffset%2B0x308c%2Bwith%2Berror%2B-110%26hl%3Den%26sa%3DX%26prmd%3Ddf)

   7. Blacklisting the modules should have no effect, they are loaded by rt73usb anyway, however blacklisting them did alleviate the issue, even if it has not gone away
   8. Could not use ndiswrapper as it conflicted with rt73usb and I had no clue how to remove the driver, blacklisting it did not work. I'd like to avoid ndiswrapper anyway.

Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
Andrea Carpineti (acarpine) wrote :

I have the same issue and (like others) I can recreate it at will. When I connect my USB wireless card it seem to work properly (just some seconds). After that I can see the error in every tty console:

phy1 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x422 with error -71.

My system infos:
Release: Natty
Uname: 2.6.38-4-generic
Arch: i386

USB Wireless card: DWL-G122 Revision B1

Using this kernel I believe I can now re-open the bug and remove the needs-upstream-testing tag. Please let me know if I'm wrong.

Changed in linux (Ubuntu):
status: Expired → New
tags: removed: needs-upstream-testing
cdar (cdar07) wrote :

I experienced this bug too. I have WiFi adapter Edimax 7318USg, and in 10.04 everything was fine, but now in 10.10 it's not. This happens very often and causes disconnection. It's very annoying. How can I help?

[18752.870649] phy4 -> rt2x00usb_vendor_request: Error - Vendor Request 0x09 failed for offset 0x0000 with error -108.
[18752.870697] phy4 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3000 with error -108.
[18752.870705] phy4 -> rt73usb_init_eeprom: Error - Invalid RT chipset detected.
[18752.870711] phy4 -> rt2x00lib_probe_dev: Error - Failed to allocate device.

I attached some files to complete the report. I don't have any
/proc/signature_version file so I used my /proc/version.
The fields "Capabilities:" of the lspci-vvnn.log file change after the key
is connected (and the error messages become visible). They all assume the
value <access denied>.
I asked in #ubuntu-bugs to set the importance to Medium.

status confirmed
tag hw-specific

Changed in linux (Ubuntu):
status: New → Confirmed
tags: added: hw-specific
summary: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset
- 0x308c with error -71.
cdar (cdar07) wrote :

Hi, it's me again. Is there something going on with this bug? This is very annoying one. Usb modem hangs up couple times a day and I have to manually plug it in and plug it out, or execute "rmmod rt73usb && modprobe rt73usb" to restore the connection with the net. Why Unity is more important? What can I do to help.

Kees van den Broek (kvdb-kvdb) wrote :

Same issue here running 11.04.

Bus 002 Device 010: ID 148f:2570 Ralink Technology, Corp. RT2570 Wireless Adapter

[23265.079987] phy2 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x04d4 with error -71.
[23265.080095] phy2 -> rt2500usb_regbusy_read: Error - Indirect register access failed: offset=0x000004d4, value=0x0000ffff

cdar (cdar07) wrote :

I forgot to mention, that I'm on 11.04 now and the bug is still present.

lod (lod-huang) wrote :

I am suffering this bug, too. Any possible way to fix?

affects: linux (Ubuntu) → rt2x00 (Ubuntu)
affects: rt2x00 (Ubuntu) → linux (Ubuntu)
Adam Hallgat (hallgat) wrote :

Affects Ubuntu 11.10. I havent noticed this error on the previous distributions. My hardware is NEC Versa One.

phy0 -> RT2x00usb_vendor_request: Error - vendor request 0x07 failed for offset 0x308c with error -110

I'm using ndiswrapper. Can be that the cause?

Adam Hallgat (hallgat) wrote :

Also happens without ndiswrapper. When happens `ping google.com`,`sudo ifconfig wlan0 up`, `sudo lshw` tasks freezes too. The network icon also disappears from my tint2 panel. They do nothing, and I don't get the terminal back. Very annoying bug, didn't happen in the previous ubuntus.

stricjux (luka-birsa) wrote :

I can confirm the same bug in 11.10 - x86.
(Linux htpc 3.0.0-14-generic #23-Ubuntu SMP)

Adapter fails with:
phy0 -> RT2x00usb_vendor_request: Error - vendor request 0x07 failed for offset 0x308c with error -110

I can also confirm that it seems related to network load - I've always had the card fail during intense downloading, but haven't noticed it if no torrents were running.

stricjux (luka-birsa) wrote :

I would like to add that symptoms are consistent with previous posters - network icon shows previous state, I'm unable to reconnect the adapter and as far as I know only rebooting helps. Will try removing and reattaching the adapter.

flux (alexander-bergenstrale) wrote :

Is this error a debian-based error or just ubuntu? Getting really ennoying and it seems its not gonna get handled since it's been around for quite some time..

I notice a few things:

(1) The error messages reported by various people are not all exactly the same. Perhaps they are having different problmes related to the same firmware?

(2) I posted problems I had with one of these Ralink-based adapters years ago. I used that same adapter on an up-to-date Debian machine recently, and it has worked flawlessly under moderate use with Debian's separate "firmware-ralink" package. I have yet to try it again on Ubuntu.

(3) I understand that this driver is built in part from an open-source driver (part of the Linux kernel; should be mostly standard across Ubuntu and Debian), and in part from binary firmware images provided freely by Ralink. Maybe Ubuntu is using an old or incorrect version of the firmware? I will try to compare more sometime.

For information on the applicable Linux/Ralink project:
http://rt2x00.serialmonkey.com/wiki/index.php/Main_Page

Also, Wolfgang Kufner, why did you immediately change the "affects" away from rt2x00 a few months back? Did you have a particular reason to believe that it's not a problem with the rt2x00 driver? Maybe you knew that this is a problem with the firmware, not with the open-source rt2x00 code?

More notes:

Regarding my previous comment (1) above: the various reported messages are different. You can check the Linux kernel source for the meaning of "error -71" for instance. The ones mentioned so far by various observers on this thread are:

error -71: -EPROTO (Protocol error)
error -19: -ENODEV (No such device)
error -110: -ETIMEDOUT (Connection timed out)
error -108: -ESHUTDOWN (Cannot send after transport endpoint shutdown)

So these are not all the same issue and should be handled separately.

From my comment (2): I have retested my USB device on Debian and it is working fine. I only see one or two "firmware error" messages when unplugging, which is understandable.

From my comment (3): It looks like the firmware in Ubuntu 11.10, Debian sid, and the Linux firmware repository (found at http://git.kernel.org/?p=linux/kernel/git/dwmw2/linux-firmware.git) all match up. So there should be no descrepancy between different distributions. (i.e., what works on Debian Sid should work on Ubuntu and vice versa)

My lsusb output:
ID 0b05:1723 ASUSTek Computer, Inc. WL-167G v2 802.11g Adapter [Ralink RT73]

In summary of my last 2 comments: all people commenting on this report are not necessarily experiencing the same bug. They just all happen to be using Ralink-based USB devices which share a driver/firmware framework. The issues could be related but not necessarily.

I am marking this "Incomplete" until we have a set of good information regarding a related issue on the most recent Ubuntu distribution with proper logs, etc. That means something like the following:

1) Describe in detail how you reproduce your issue (i.e., step-by-step)
2) Describe your system, giving Ubuntu version, etc.
3) Provide the output from the following commands in your comment or as separate attachments:
dmesg
lsusb
uname -a
lsusb -vv
dkpg -l | grep linux-firmware

If we find more than one set of valid logs that represent distinct issues, then we should file new, separate bug reports.

(BTW, the logs attached by Andrea Carpineti are totally worthless; they are not related to this bug and seem to apply to a Broadcom chip, not Ralink)

Changed in linux (Ubuntu):
status: Confirmed → Incomplete

I'm also affected by this bug. I have to manually unplug and re-plug my TP-Link TL-WN321G with Ralink chip which sometimes also affects ACPI to the point where I have to restart the system.

Jan 26 07:10:36 radio-dev kernel: [ 422.840163] phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3040 with error -110.

Linux radio-dev 3.0.0-15-generic #26-Ubuntu SMP Fri Jan 20 17:23:00 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 1a40:0101 TERMINUS TECHNOLOGY INC. USB-2.0 4-Port HUB
Bus 001 Device 005: ID 148f:2573 Ralink Technology, Corp. RT2501/RT2573 Wireless Adapter
Bus 003 Device 002: ID 04d9:0499 Holtek Semiconductor, Inc. Optical Mouse

ii linux-firmware 1.60 Firmware for Linux kernel drivers
ii linux-firmware-nonfree 1.11 Non-free firmware for Linux kernel drivers

btw, here's the additional details:

1) I plug the USB Wifi (TP-Link TL-WN321G) and wait for it to disconnect. The nm-applet will still say it's connected so I'm using the Dropbox applet as an indicator. Syslog would then spit out the rt2x00usb_vendor_request error. It just happens without triggering it. Sometimes I'm doing something, sometimes I'm not, either way I'll have this error. Also, it's not time dependent, sometimes it'll go on for 5hours or more, sometimes for 5 mins.

2) I'm on Ubuntu Oneiric with 3.0.0-15 kernel. I've also tried the v2.6 and v3.2 kernels with the same result.

3) see attachments on previous post

Seems like downloading torrents triggers this bug

still an issue with kernel 3.2.2, attaching syslog and other hardware details

Hi Dax,

Sorry for the delay on this. I've noted these problems on the rt2x00-users mailing list, where development for the supported Ralink drivers takes place. For help in debugging, they've suggested you try the official Ralink driver (a.k.a. "legacy driver") found here:
http://www.ralinktech.com/en/04_support/support.php?sn=501

I believe you would need the "RT2501USB(RT73:RT2571W/RT2573/RT2671)" package. It's freely available, based on a simple usage agreement, but it is not really "maintained" (the in-kernel driver is the main support) and it is certainly a "use at your own risk" situation. It takes some work to properly extract, compile, and insert the driver into your system...if you want to proceed and have trouble, perhaps I can help.

Anyway, the driver maintainers would be interested in seeing if your problems still exist on the legacy driver.

BTW, sample pieces of the mailing list conversation are at the URLs below. There's not much progress on this issue, it seems:
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2012-January/004498.html
http://rt2x00.serialmonkey.com/pipermail/users_rt2x00.serialmonkey.com/2012-January/004532.html

Changed in linux (Ubuntu):
status: Incomplete → Confirmed

thanks for the reply Brian.
I guess I'll stick with v2.6.38 (which I'm currently using and enjoying) and most probably switch to v3 once this bug is fixed.

Dax,

So 2.6.38 has been working totally fine for you? Can you give the 'uname -r' output for your working system? That could be helpful for determining the cause.

Here's the uname output
2.6.38-02063808-generic

2.6.39 also works, but I don't have it installed due to a security bug.

I get similar messages (with "error -110") on Ubuntu 12.04 beta, with linux 3.2.0-18. Actually, I got this message since the alpha milestone, with all kernels I used. Never had this problem in previous releases. I have an RT73 device.

Lei Sun (leix-sun) wrote :

It seems like disable power management of wlan will solve this problem.

You can try to disable the power management of your wlan by running the following command.
sudo iwconfig wlan0 power off

Lei Sun (leix-sun) wrote :

Disabling power managaement of wlan doesn't work. After running aMule for a while, I still get error -110.

Shahar Or, thank you for reporting this and helping make Ubuntu better. This bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? Can you try with the latest development release of Ubuntu? ISO CD images are available from http://cdimage.ubuntu.com/releases/ .

If it remains an issue, could you run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux <replace-with-bug-number>

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. 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. Please let us know your results.

Thanks in advance.

Changed in linux (Ubuntu):
status: Confirmed → Incomplete

AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.24.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CRDA: Error: [Errno 2] File o directory non esistente
DistroRelease: Ubuntu 12.04
HibernationDevice: RESUME=UUID=0ec0d589-734c-4326-94d9-4b83c8a9dfbf
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120209.2)
MachineType: HP-Pavilion GS405AA-ABZ a6250.it
Package: linux (not installed)
ProcEnviron:
 TERM=xterm
 LANG=it_IT.UTF-8
 SHELL=/bin/bash
ProcFB: 0 nouveaufb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-20-generic root=UUID=07a39871-febb-44f0-8305-018097c6ede1 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.2.0-20.33-generic 3.2.12
RfKill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no
Tags: precise
Uname: Linux 3.2.0-20-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
dmi.bios.date: 10/24/2007
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 5.13
dmi.board.name: Berkeley
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Hewlett-Packard
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr5.13:bd10/24/2007:svnHP-Pavilion:pnGS405AA-ABZa6250.it:pvr:rvnASUSTeKComputerINC.:rnBerkeley:rvr1.xx:cvnHewlett-Packard:ct3:cvrChassisVersion:
dmi.product.name: GS405AA-ABZ a6250.it
dmi.sys.vendor: HP-Pavilion

tags: added: apport-collected precise

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

Launchpad Janitor (janitor) wrote :

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

Changed in linux (Ubuntu):
status: Incomplete → Expired

Ubuntu 12.04
3.2.0-27-generic
USB Wireless :Linksys WUSB54GC v1 802.11g Adapter [Ralink RT73]

$ sudo tail -f /var/log/syslog:
kernel: [48029.612115] phy0 -> rt2x00usb_vendor_request: Error - Vendor Reques$
0x07 failed for offset 0x308c with error -110.

$ sudo iwconfig wlan0
wlan0 IEEE 802.11bg ESSID:"OTE4b259b"
          Mode:Managed Frequency:2.437 GHz Access Point: 00:13:33:A0:30:7A
          Bit Rate=54 Mb/s Tx-Power=20 dBm
          Retry long limit:7 RTS thr:off Fragment thr:off
          Power Management:on
          Link Quality=48/70 Signal level=-62 dBm

$ sudo dpkg -l | grep linux-firmware
ii linux-firmware 1.79 Firmware for Linux kernel drivers

I cant reprodude,it happend at random several times. 1 per day. But its interesting that problems started after moving the adsl modem to another room lengthening the distance between modem and usb-wifi stick. (due to family reasons i cant put modem to its old central place )

Also before the connection is lost i see ping to the modem raising the msses.

Removing and connecting again fixes it.

tags: added: needs-kernel-logs needs-upstream-testing
removed: apport-collected precise

Alexandros Prekates, could you please file a new report by executing the following in a terminal:
ubuntu-bug linux

For more on this, please see the Ubuntu Bug Control and Ubuntu Bug Squad 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. Thank you for your understanding.

Helpful Bug Reporting Links:
https://help.ubuntu.com/community/ReportingBugs#A3._Make_sure_the_bug_hasn.27t_already_been_reported
https://help.ubuntu.com/community/ReportingBugs#Adding_Apport_Debug_Information_to_an_Existing_Launchpad_Bug
https://help.ubuntu.com/community/ReportingBugs#Adding_Additional_Attachments_to_an_Existing_Launchpad_Bug

Marco Scopesi (marco.scopesi) wrote :

My usb wireless card (Bus 001 Device 007: ID 148f:3070 Ralink Technology, Corp. RT2870/RT3070 Wireless Adapter, using rt2800usb) used to work with ubuntu 12.04.
Since 2 weeks I'm getting these errors in dmesg:

phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x1700 with error -71
phy0 -> rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x101c with error -110

and my connection hangs after few minutes.
I tried the same card on Windows 7 and I'm getting the same broken connection.
Maybe this is just an hardware problem...

cheers

darren (dazndom-gmail) wrote :

WHY is this bug not fixed yet ?
4.5 yrs this has been going on,

 I am running 12.04.3 and this bug started on me about 4 weeks ago, it also affects my Sabayon and Mandriva OS on this same computer

http://www.spinics.net/lists/linux-wireless/msg40573.html ..... This page says the maintainer of the driver can't be bothered fixing it

for jupiters sake can somebody please fix it,

phyo -> rt2x00usb_Vendor_request : Error-Vendor Request 0x07. failed for offset 0x308c with error -110

Darren,

There seems to be a variety of issues here, but the 'b43' problem you link here is certainly unrelated. That is a totally different set of hardware and software.

If you are having real problems with the rt2x00usb driver, perhaps you can provide constructive information for this bug report. But if you are using b43, you need to file a different bug report.

darren, 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 while booted into a Ubuntu repository kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: 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.

No need exists to comment here at this time. After reading the above documentation in it's entirety, if you have further questions, you are welcome to redirect them to the appropriate mailing list or forum via http://www.ubuntu.com/support/community/mailinglists , or you may contact me directly.

Thank you for your understanding.

joshyg6 (josheg) wrote :

I'm encountering exactly the same bug with rt73 drivers for onboard ralink wifi chip.. Ubuntu-based LInux Mint 17.. And 3.14--30 kernels.. What th eheck! This is still a bug?! 5 years and no solution?!

joshyg6, thank you for your comment. So your hardware and problem may be tracked, could you please file a new report with Ubuntu (not Linux Mint) by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

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

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

Nicholas Pinto (nian.pinto) wrote :
Download full text (4.9 KiB)

Reporting in from 16.04LTS, this bug still exists and Bug #1388416 appears to be describing the same bug and is marked Confirmed. I just signed up to post this so I'm still unfamiliar with the platform to find a way to link to it here.

I have the same issue, though it appeared to change behaviors after a recent restart-required update. Before the behavior was that after dropping, hot replugging resolved the issue 90% of the time; after the recent update hot replugging does nothing. At first I fell back to rebooting every time and then dug around for a bit and eventually found a more palatable work-around.

Issuing a restart command to the network-manager service often works, though you may need to restart your browser. Sometimes rfkill likes to soft-block the device especially after hot replugging so if it still isn't working try checking there.

I did notice the errors issued by ieee80211/rt2x00usb would be a quantity of 110s, then two or three 71s, and finally one or two 19s. This leads me to believe that something is hanging in the works or maybe the supplicant, that leads to the protocol error and eventual bailing out at the end. I'm not entirely qualified to guess, but I'd say it's possibly an issue in the kernel or systemd, but maybe network-manager. I doubt the module itself is to blame (since it worked in the past), but this is all my own conjecture and I have zero visibility deeper than the logs (I'd poke the guts but I moved from Arch to Ubuntu to avoid this kind of thing honestly). Incidentally back on 2.6.x kernel contemporary with the initial bug report up top, this problem existed on Arch so it perhaps is a chronic kernel issue.

The entities at play seem to be ieee80211, rt2x00usb, rt73usb, the kernel, and network-manager in some capacity.

lsusb:
Bus 002 Device 005: ID 148f:9021 Ralink Technology, Corp. RT2501USB Wireless Adapter

uname -r:
4.4.0-66-generic

dmesg (error 110 has dozens of entries above this and a few forced reset messages):
[27263.243242] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -110
[27263.347192] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x3080 with error -110
[27263.451185] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x3080 with error -110
[27263.555188] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110
[27263.659189] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -110
[27263.763191] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110
[27263.867203] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110
[27263.971195] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x06 failed for offset 0x308c with error -110
[27264.075198] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor Request 0x07 failed for offset 0x308c with error -110
[27264.175843] ieee80211 phy2: rt2x00usb_vendor_request: Error - Vendor R...

Read more...

Changed in linux (Ubuntu):
status: Expired → New

This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run:

apport-collect 362875

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

Changed in linux (Ubuntu):
status: New → Incomplete
tags: added: intrepid
Nicholas Pinto (nian.pinto) wrote :

I tried to do an apport and it seg-faulted in the middle of it. However a few days of researching and looking at the chipset datasheet specific to my model and I found something useful.

The dmesg report complains about vendor request 0x07 which is a multiple byte read in the specs, while the offset 0x3000 corresponds to the MAC control register, specifically the ASIC version number.

As well, the fact that this bug has existed across releases, kernel versions, and the transition to systemd points more to the driver than anything else. I also tested wicd (currently using that now) and the problem persists, which means network-manager isn't the primary source of the bug. All of these can still be in play or making the problem worse but aren't the sole cause.

If I can get sight into the drivers (both rt73 and rt2x00USB), I might be able to pin down more specifics. For the actual bug fixers, I'd advise to check and see if the non-USB version of this chipset shares the problem to isolate the bug some more.

Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in rt2x00 (Ubuntu):
status: New → Confirmed
Jay Foster (jayf0ster) wrote :

I have experienced this bug on a non Ubuntu system for some time. I spent some time comparing the SparkLAN DPO driver source with the main line kernel driver source and tried a couple of changes.

1) There were some places missing a lock (this change did not affect this bug, however).
2) The DPO driver performed the 32-bit register writes as two 16-bit single write commands instead of one four byte multi-write command. I suspected that this might lead to race conditions setting the registers (not atomic) which was causing the Wi-Fi chip to hang. I thought it possible that the Wi-Fi chip firmware might buffer the two 16-bit single writes and then perform a single 32-bit write to the register, thus making it atomic. I asked SparkLAN about this, but received no reply. Note that the DPO driver performs the 32-bit register reads as a single four byte multi-read, just like the main line kernel driver does.

I tested the following patch and the problem went away, either because it fixes the issue or it changes the timing to cover it up. Perhaps a distinction without a difference.

The attachment "rt2x00usb.pat" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.]

tags: added: patch
Kai-Heng Feng (kaihengfeng) wrote :

Unfortunately your patch doesn't work for my rt2800usb, here's the dmesg:

[ 117.351403] wlxacf1df0c507b: authenticate with 2c:36:f8:fa:ec:00
[ 117.405386] wlxacf1df0c507b: send auth to 2c:36:f8:fa:ec:00 (try 1/3)
[ 117.406182] wlxacf1df0c507b: authenticated
[ 117.411923] wlxacf1df0c507b: associate with 2c:36:f8:fa:ec:00 (try 1/3)
[ 117.414946] wlxacf1df0c507b: RX AssocResp from 2c:36:f8:fa:ec:00 (capab=0x11 status=0 aid=13)
[ 117.422791] wlxacf1df0c507b: associated
[ 117.422810] IPv6: ADDRCONF(NETDEV_CHANGE): wlxacf1df0c507b: link becomes ready
[ 117.689395] wlxacf1df0c507b: Limiting TX power to 27 (30 - 3) dBm as advertised by 2c:36:f8:fa:ec:00
[ 118.317773] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 17159, forcing to 0
[ 118.317782] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 159.352565] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 21901, forcing to 0
[ 159.352575] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 159.356085] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 32969, forcing to 0
[ 159.356095] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 159.356112] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 26654, forcing to 0
[ 159.356116] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 159.356145] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 31363, forcing to 0
[ 159.356150] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 159.356276] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 44307, forcing to 0
[ 159.356285] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 160.791879] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 22885, forcing to 0
[ 160.791888] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840
[ 165.425558] ieee80211 phy1: rt2800usb_fill_rxdone: Error - Bad frame size 8650, forcing to 0
[ 165.425569] ieee80211 phy1: rt2x00lib_rxdone: Error - Wrong frame size 0 max 3840

Kai-Heng Feng (kaihengfeng) wrote :

The vendor request error message does go away though...

Kai-Heng Feng (kaihengfeng) wrote :

With your patch,

The problem only occurs to 5G-an network.
2.4G-g works great.

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

Other bug subscribers