What is the proper place to report that this error persists on Ubuntu 22.04 Jammy? After resuming my suspended PC, the wifi becomes unresponsive. The only way to get it working again is to do a full reboot.
kernel: mt7921e 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e 0000:02:00.0: chip reset kernel: mt7921e 0000:02:00.0: Message 0000004e (seq 7) timeout kernel: mt7921e 0000:02:00.0: AMD-Vi: Event logged [IO_PAGE_FAULT domain=0x000a address=0x0 flags=0x0020] kernel: mt7921e 0000:02:00.0: chip reset failed kernel: mt7921e 0000:02:00.0: Failed to get patch semaphore kernel: mt7921e 0000:02:00.0: Message 80000010 (seq 4) timeout Any advice? -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux-firmware in Ubuntu. https://bugs.launchpad.net/bugs/1958286 Title: mt7921e 0000:02:00.0: PM: failed to resume async: error -110 Status in HWE Next: New Status in linux-firmware package in Ubuntu: Fix Released Status in linux-firmware source package in Focal: Fix Released Status in linux-firmware source package in Hirsute: Won't Fix Status in linux-firmware source package in Impish: Fix Released Status in linux-firmware source package in Jammy: Fix Released Bug description: [SRU Justification] [Impact] Mediatek MT7921 may fail to resume from runtime suspend can cause chip reset. mt7921e 0000:02:00.0: PM: failed to resume async: error -110 mt7921e 0000:02:00.0: chip reset [Fix] This is fixed with both bluetooth and WiFi firmware upgrade to upstream commit 094d7adc1136 ("linux-firmware: update firmware for MT7921 WiFi device") and commit 1e744b85cd4c ("linux-firmware: update firmware for mediatek bluetooth chip(MT7921)"). [Test Case] This can be triggered by checkbox warm reset stress test: $ checkbox-cli run com.canonical.certification::stress/reboot [Where problems could occur] This imports fixes requiring both kernel driver and proprietary firmware updates, the firmware part might cause instability or so. [Other Info] This affects all kernels supporting MT7921, which means F/H/I/J. ========== original bug report ========== [Summary] Boot into Ubuntu desktop, MT7921 shows IP is obtained, however there is no response from gateway pings, neither is 8.8.8.8. kernel: [ 588.893227] mt7921e 0000:02:00.0: PM: failed to resume async: error -110 kernel: [ 588.893236] mt7921e 0000:02:00.0: chip reset [Reproduce Steps] 1. Boot into Ubuntu desktop 2. Check if MT7921 obtains IP, ping gateway and ping 8.8.8.8 3. No response, need to do cold boot to recover 4. The issue is easily be seen after warm reset stress, I locally test warm reset stress for 100 times [Results] Expected: Has traffic and response by ping Actual: No response To manage notifications about this bug go to: https://bugs.launchpad.net/hwe-next/+bug/1958286/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
