openwrt / openwrt/mt76

mt7610u: flood of "rx urb failed" and "vendor request * failed"

Open
#454 6 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C
Stars
888
Forks
436
PR merge metrics
No merged PRs in 30d

Description

This issue is not related to openwrt but only concerns the mt76 driver itself.

I'm running kernel 5.8 on a desktop computer, and whenever I plug in a MT7610U dongle, it seems to upset mt76x0u because I get a non-stop flood of errors. The dongle is a generic one without any branding on it, and it seems to work just fine on Windows 10 with both Microsoft's stock drivers and the OEM drivers stored on the SPI flash. It doesn't seem to be a firmware issue, as I've verified /lib/firmware/mediatek/mt7610u.bin is present on my computer. Any ideas on why this is happening?

usb 1-1.3: new high-speed USB device number 8 using xhci_hcd
usb 1-1.3: New USB device found, idVendor=0e8d, idProduct=7610, bcdDevice= 1.00
usb 1-1.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3
usb 1-1.3: Product: WiFi
usb 1-1.3: Manufacturer: MediaTek
usb 1-1.3: SerialNumber: 1.0
usb 1-1.3: reset high-speed USB device number 8 using xhci_hcd
mt76x0u 1-1.3:1.0: ASIC revision: 76100002 MAC revision: 76502000
mt76u_complete_rx: 6284 callbacks suppressed
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
mt76x0u 1-1.3:1.0: rx urb failed: -32
xhci_hcd 0000:09:00.0: WARN Cannot submit Set TR Deq Ptr
xhci_hcd 0000:09:00.0: A Set TR Deq Ptr command is pending.
mt76x0u 1-1.3:1.0: vendor request req:07 off:09a8 failed:-110
mt76x0u 1-1.3:1.0: vendor request req:06 off:09a8 failed:-71
mt76x0u 1-1.3:1.0: vendor request req:42 off:0230 failed:-71
mt76u_complete_rx: 13264 callbacks suppressed
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: rx urb failed: -71
mt76x0u 1-1.3:1.0: vendor request req:42 off:0232 failed:-71
mt76x0u 1-1.3:1.0: vendor request req:42 off:0234 failed:-71
mt76x0u 1-1.3:1.0: vendor request req:42 off:0236 failed:-71
mt76x0u 1-1.3:1.0: firmware upload failed: -71
mt76x0u 1-1.3:1.0: vendor request req:06 off:0800 failed:-71
mt76x0u 1-1.3:1.0: vendor request req:07 off:0080 failed:-71
mt76x0u 1-1.3:1.0: vendor request req:06 off:0080 failed:-71
mt76x0u 1-1.3:1.0: vendor request req:06 off:0080 failed:-71
mt76x0u: probe of 1-1.3:1.0 failed with error -71
usb 1-1.3: USB disconnect, device number 8

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the MT7610U failure with the mt76x0u driver on kernel 5.8, then inspect the driver’s USB error path using the reported rx URB, vendor request, and firmware upload messages. Done means the dongle probes successfully without the repeated errors or disconnecting.

Written by the indexing model from the issue text.

Assessment

Tech stack
c, linux
Domain
networking, operating-systems
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.