This bug was fixed in the package linux-oem-5.14 - 5.14.0-1011.11
---------------
linux-oem-5.14 (5.14.0-1011.11) focal; urgency=medium
* focal/linux-oem-5.14: 5.14.0-1011.11 -proposed tracker
(LP: #1954691)
* Packaging resync (LP: #1786013)
- debian/dkms-versions -- update from kernel-versions (main/2021.11.08)
* s2idle suspend failure: amd_pmc AMDI0005:00: SMU response timed out
(LP: #1954633)
- platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops
* Fix power button wakeup with shared IRQs on AMD platforms (LP: #1953540)
- ACPI: Add stubs for wakeup handler functions
- pinctrl: amd: Fix wakeups when IRQ is shared with SCI
* alsa/hda: the microphone can't be detected on a couple of lenovo machines
(LP: #1954612)
- ALSA: hda/realtek - Add headset Mic support for Lenovo ALC897 platform
* mt7921e: Failed to start WM firmware (LP: #1954300)
- SAUCE: Bluetooth: btusb: Handle download_firmware failure cases
- SAUCE: Bluetooth: btusb: Return error code when getting patch status
failed
* Fix cpufreq: cpufreq_online: Failed to initialize policy for cpu: 0 (-19)
(LP: #1954617)
- ACPI: CPPC: Introduce cppc_get_nominal_perf()
- ACPI: CPPC: Add NULL pointer check to cppc_get_perf()
- cpufreq: intel_pstate: hybrid: Rework HWP calibration
* Add support for NVIDIA EC backlight (LP: #1953286)
- platform/x86: Add driver for ACPI WMAA EC-based backlight control
- platform/x86: Remove "WMAA" from identifier names in wmaa-backlight-wmi.c
- platform/x86: Rename wmaa-backlight-wmi to nvidia-wmi-ec-backlight
- [Config] NVIDIA_WMI_EC_BACKLIGHT=m
* Let VMD follow host bridge PCIe settings (LP: #1954611)
- SAUCE: PCI: vmd: Honor ACPI _OSC on PCIe features
-- Timo Aaltonen <[email protected]> Mon, 13 Dec 2021
19:41:56 +0200
** Changed in: linux-oem-5.14 (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-5.14 in Ubuntu.
https://bugs.launchpad.net/bugs/1954300
Title:
mt7921e: Failed to start WM firmware
Status in HWE Next:
New
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-firmware package in Ubuntu:
Fix Released
Status in linux-oem-5.13 package in Ubuntu:
Invalid
Status in linux-oem-5.14 package in Ubuntu:
Invalid
Status in linux source package in Focal:
Invalid
Status in linux-firmware source package in Focal:
Fix Committed
Status in linux-oem-5.13 source package in Focal:
Fix Committed
Status in linux-oem-5.14 source package in Focal:
Fix Released
Status in linux source package in Impish:
Fix Committed
Status in linux-firmware source package in Impish:
Fix Committed
Status in linux-oem-5.13 source package in Impish:
Invalid
Status in linux-oem-5.14 source package in Impish:
Invalid
Status in linux source package in Jammy:
In Progress
Status in linux-firmware source package in Jammy:
Fix Released
Status in linux-oem-5.13 source package in Jammy:
Invalid
Status in linux-oem-5.14 source package in Jammy:
Invalid
Bug description:
[SRU Justification]
[Impact]
MT7921 might fail at device probe at boot:
mt7921e 0000:03:00.0: WM Firmware Version: ____010000, Build Time:
20211014150922
IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready
mt7921e 0000:03:00.0: Message 80000002 (seq 9) timeout
mt7921e 0000:03:00.0: Failed to start WM firmware
mt7921e: probe of 0000:03:00.0 failed with error -110
[Fix]
Kernel fixes:
* 995d948cf2e4 ("Bluetooth: btusb: Return error code when getting patch status
failed")
* 00c0ee9850b7 ("Bluetooth: btusb: Handle download_firmware failure cases")
And firmware:
* 948cad200e94 ("linux-firmware: update frimware for mediatek bluetooth chip
(MT7921)")
[Test Case]
Run checkbox reboot stress tests to try trigger this issue:
$ 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.
========== original bug report ==========
Oct 25 22:40:10 u kernel: [ 6.194102] mt7921e 0000:03:00.0: WM Firmware
Version: ____010000, Build Time: 20211014150922
Oct 25 22:40:11 u kernel: [ 7.948458] rfkill: input handler disabled
Oct 25 22:40:12 u kernel: [ 9.012741] r8169 0000:02:00.0 enp2s0: Link is Up -
1Gbps/Full - flow control rx/tx
Oct 25 22:40:12 u kernel: [ 9.012766] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0:
link becomes ready
Oct 25 22:40:13 u kernel: [ 9.174471] usb 1-2.4: device descriptor read/64,
error -110
Oct 25 22:40:13 u kernel: [ 9.250459] mt7921e 0000:03:00.0: Message 80000002
(seq 9) timeout
Oct 25 22:40:13 u kernel: [ 9.250470] mt7921e 0000:03:00.0: Failed to start
WM firmware
Oct 25 22:40:13 u kernel: [ 9.250596] mt7921e: probe of 0000:03:00.0 failed
with error -110
This takes following fixes to resolve completely:
* kernel patch:
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c
*
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=00c0ee9850b7b0cb7c40b8daba806ae2245e59d4
* firmware:
*
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/commit/?id=948cad200e94d82d339207f8ac7b10f932bd627a
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1954300/+subscriptions
--
Mailing list: https://launchpad.net/~kernel-packages
Post to : [email protected]
Unsubscribe : https://launchpad.net/~kernel-packages
More help : https://help.launchpad.net/ListHelp
