Bug 214557
| Summary: | mt7921e: probe of 0000:05:00.0 failed with error -110 | ||
|---|---|---|---|
| Product: | Drivers | Reporter: | Mike Lothian (mike) |
| Component: | network-wireless | Assignee: | drivers_network-wireless (drivers_network-wireless) |
| Status: | RESOLVED PATCH_ALREADY_AVAILABLE | ||
| Severity: | normal | CC: | bruno.n.pagani, jifengshenmo, kernel, mapengyu, mike, realskorpion, sean.mcauliffe, sephiroth_pk, thanhdatwarriorok, urugang |
| Priority: | P1 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Kernel Version: | 5.15-rc2 | Subsystem: | |
| Regression: | No | Bisected commit-id: | |
| Attachments: |
Full dmesg
Bug |
||
error in log: mt7921e 0000:05:00.0: ASIC revision: ff0c0000 It could be a fw error. Please try latest fw. I've already tested when I noticed it had been updated, no improvement unfortunately I've also tested the updates for the next kernel here: https://github.com/nbd168/wireless But the issue still happens: Oct 25 03:56:21 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: enabling device (0000 -> 0002) Oct 25 03:56:21 axion.fireburn.co.uk kernel: mt7921e 0000:05:00.0: ASIC revision: ff000000 Oct 25 03:56:21 axion.fireburn.co.uk kernel: mt7921e: probe of 0000:05:00.0 failed with error -110 Re-tested with all the patches at https://github.com/nbd168/wireless which I guess is for 5.17 - same issue I'm running into the same problem. On reboot with my Asus g533qs I get: Dec 6 08:40:44 localhost kernel: [ 12.230358] mt7921e 0000:03:00.0: enabling device (0000 -> 0002) Dec 6 08:40:44 localhost kernel: [ 12.230692] mt7921e 0000:03:00.0: disabling ASPM L1 Dec 6 08:40:44 localhost kernel: [ 12.230751] mt7921e 0000:03:00.0: ASIC revision: 79610010 Dec 6 08:40:44 localhost kernel: [ 13.304760] mt7921e: probe of 0000:03:00.0 failed with error -110 However when I power off and power on, I get: Dec 6 08:42:37 localhost kernel: [ 11.394899] mt7921e 0000:03:00.0: enabling device (0000 -> 0002) Dec 6 08:42:37 localhost kernel: [ 11.395114] mt7921e 0000:03:00.0: disabling ASPM L1 Dec 6 08:42:37 localhost kernel: [ 11.395143] mt7921e 0000:03:00.0: ASIC revision: 79610010 Dec 6 08:42:37 localhost kernel: [ 11.474166] mt7921e 0000:03:00.0: HW/SW Version: 0x8a108a10, Build Time: 20211014150838a Dec 6 08:42:37 localhost kernel: [ 11.731801] mt7921e 0000:03:00.0: WM Firmware Version: ____010000, Build Time: 20211014150922 Dec 6 08:42:37 localhost kernel: [ 11.757965] mt7921e 0000:03:00.0: Firmware init done Dec 6 08:42:37 localhost kernel: [ 12.574961] mt7921e 0000:03:00.0 wlp3s0: renamed from wlan0 This problem doesn't happen if I swap out the wifi card and use an Intel AX200NGW.So issue seems to be isolated to the Mediatek 7921. for 5.15.7,only when i need shutdown machine, and unplug power cable,then power on, driver can init wlan0 successdully. Same issue here. I have to do a cold boot without charger plugged in to restore wifi Discussion on github: https://github.com/openwrt/mt76/issues/548 The problem reappears everytime I reboot with charger plugged in. When booting with this patch applied to Linus's tree, the boot stops with a BUG Created attachment 300291 [details]
Bug
I don't see this issue if I compile mt76 as a module That patch does fix the issue, the bug I was seeing was from an unrelated issue The fix for that is https://patchwork.kernel.org/project/linux-usb/patch/20220124090228.41396-2-heikki.krogerus@linux.intel.com/ Would it be possible to backport it to current kernel lines? Because AFAICS, it is merged for 5.17 that will not be out before one month likely. Also, not all distros upgrade kernel to newer lines, so… This patch should work against 5.17-rc https://raw.githubusercontent.com/FireBurn/KernelStuff/master/04-mt76.patch git am 04-mt76.patch And should get warm reboots working Not sure what would be needed to get this working on 5.16 The patches I think are due for 5.18 😭 No, you can see here https://github.com/torvalds/linux/commit/7817adb03cfb52ebb5bdb25fd9fc8f683a1a09d9 that it has been published as part of 5.17-rc2 (and thus if you use -rc2 or -rc3 instead of -rc, you don’t need to manually add the patch). So it should be in 5.17 release. Thanks a lot for the solution. I'll wait for the 5.17 release As far as my ability to read code goes, I would say that the commit linked by Bruno does not have anything to do with this issue, as it looks to be about USB Type-C and not about MediaTek network devices. My apologies if I am mistaken. The issue appears to be there still with Linux 5.17.0. dmesg says: mt7921e 0000:04:00.0: enabling device (0000 -> 0002) mt7921e 0000:04:00.0: ASIC revision: 79610010 mt7921e: probe of 0000:04:00.0 failed with error -110 This is on my desktop system which includes an ASUS ROG Strix X570-E motherboard. (In reply to Riccardo Robecchi from comment #18) > As far as my ability to read code goes, I would say that the commit linked > by Bruno does not have anything to do with this issue, as it looks to be > about USB Type-C and not about MediaTek network devices. My apologies if I > am mistaken. > > The issue appears to be there still with Linux 5.17.0. dmesg says: > mt7921e 0000:04:00.0: enabling device (0000 -> 0002) > mt7921e 0000:04:00.0: ASIC revision: 79610010 > mt7921e: probe of 0000:04:00.0 failed with error -110 > > This is on my desktop system which includes an ASUS ROG Strix X570-E > motherboard. It's so sad... So the bug is still unsolved? Plus, I noticed that in some situation, for example, when I reboot my laptop from Linux to start Windows, the device goes down too. It seems that it is a bug from hardware. The patch that fixes this will be included in 5.18-rc1, I've asked about it being backported but I've not heard back Alternativly you can apply https://raw.githubusercontent.com/FireBurn/KernelStuff/master/04-mt76.patch onto 5.17 (In reply to Riccardo Robecchi from comment #18) > As far as my ability to read code goes, I would say that the commit linked > by Bruno does not have anything to do with this issue, as it looks to be > about USB Type-C and not about MediaTek network devices. My apologies if I > am mistaken. Yes sorry, I mixed things up with the other patch linked by Mike about his unrelated issue… |
Created attachment 298995 [details] Full dmesg Sometimes when I reboot my laptop the driver doesn't initialise properly mt7921e 0000:05:00.0: enabling device (0000 -> 0002) mt7921e 0000:05:00.0: disabling ASPM L1 mt7921e 0000:05:00.0: ASIC revision: ff0c0000 mt7921e: probe of 0000:05:00.0 failed with error -110 lspci -nn 05:00.0 Network controller [0280]: MEDIATEK Corp. Device [14c3:7961] Rebooting tends not to fix things, but switching off then switching off works This is on a new laptop and I'm not sure if it's a regression The module and firmware is built into the kernel and it's a small EFI stub setup Here is the successful messages after a cold start: mt7921e 0000:05:00.0: enabling device (0000 -> 0002) mt7921e 0000:05:00.0: disabling ASPM L1 mt7921e 0000:05:00.0: ASIC revision: 79610010 mt7921e 0000:05:00.0: HW/SW Version: 0x8a108a10, Build Time: 20210612122717a mt7921e 0000:05:00.0: WM Firmware Version: ____010000, Build Time: 20210612122753 mt7921e 0000:05:00.0: Firmware init done <info> [1632825882.0267] rfkill0: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:02.2/0000:05:00.0/ieee80211/phy0/rfkill0) (driver mt7921e)