Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now
and be available at https://launchpad.net/ubuntu/+source/linux-
firmware/1.187.24 in a few hours, and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how
to enable and use -proposed.  Your feedback will aid us getting this
update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, what testing has been
performed on the package and change the tag from verification-needed-
focal to verification-done-focal. If it does not fix the bug for you,
please add a comment stating that, and change the tag to verification-
failed-focal. In either case, without details of your testing we will
not be able to proceed.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance for helping!

N.B. The updated package will be released to -updates after the bug(s)
fixed by this package have been verified and the package has been in
-proposed for a minimum of 7 days.

-- 
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     : kernel-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~kernel-packages
More help   : https://help.launchpad.net/ListHelp

Reply via email to