mt76x2u wireless broken with message 'vendor request req:07 off:10f4 failed:-110'
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 888
- Forks
- 436
- PR merge metrics
- No merged PRs in 30d
Description
This fault occurs frequently. When it occurs, wifi device not working. reloading the mt76x2u driver with modprobe cannot be recovered, and the system can only be restarted. Upgrading to the mainline kernel version (from 5.15.0.41.44 to 5.18.12) still has this problem. I also tried add 'options mt76_usb disable_usb_sg=1' to /etc/modprobe.d/mt76-usb.conf and Make sure the configuration was loaded correctly.Can any one help?
os version: Ubuntu 22.04.
kernel: Linux leenPC 5.18.12-051812-generic #202207150942 SMP PREEMPT_DYNAMIC Fri Jul 15 10:10:55 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux.
And 'systool -v -m mt76_usb' result information:
leen@leenPC:~$ systool -v -m mt76_usb
Module = "mt76_usb"
Attributes:
coresize = "40960"
initsize = "0"
initstate = "live"
refcnt = "2"
srcversion = "0FA481A5890E877A9C15D17"
taint = ""
uevent = <store method only>
Parameters:
disable_usb_sg = "Y"
Sections:
And 'lsusb' result information:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 413c:2113 Dell Computer Corp. KB216 Wired Keyboard
Bus 001 Device 003: ID 0e8d:7612 MediaTek Inc. MT7612U 802.11a/b/g/n/ac Wireless Adapter
Bus 001 Device 002: ID 24ae:2013 Shenzhen Rapoo Technology Co., Ltd. Rapoo 2.4G Wireless Device
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
The dmesg and journalctl log information when occurs:
And after execute 'modprobe -r mt76x2u && modprobe mt76x2u', the dmesg and journalctl log:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the attached dmesg.log and journalctl.log first, then compare them with dmesg-reload-mt76x2u.log and journalctl-reload-mt76x2u.log after the mt76x2u reload attempt. Trace the mt76x2u and mt76_usb driver entry points to determine why the vendor request times out and why reloading does not recover the device; done means the failure is reproducible, explained, and recovery or prevention is verified.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, linux, ubuntu
- Domain
- networking, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100