| Message ID | 20211213093910.3521363-1-vicamo.yang@canonical.com |
|---|---|
| Headers | show |
| Series | Fix MT7921 failed to start WM firmware | expand |
On 13.12.2021 11.39, You-Sheng Yang wrote: > BugLink: https://bugs.launchpad.net/bugs/1954300 > > [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. > > [Other Info] > > These patches are currently in bluetooth/bluetooth-next.git, and therefore > not yet available to any Ubuntu kernel. Nominated for all >= 5.13. > > Mark Chen (2): > UBUNTU: SAUCE: Bluetooth: btusb: Handle download_firmware failure > cases > UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch > status failed > > drivers/bluetooth/btusb.c | 5 +++++ > 1 file changed, 5 insertions(+) > applied to oem-5.14, thanks
On 13.12.2021 11.39, You-Sheng Yang wrote: > BugLink: https://bugs.launchpad.net/bugs/1954300 > > [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. > > [Other Info] > > These patches are currently in bluetooth/bluetooth-next.git, and therefore > not yet available to any Ubuntu kernel. Nominated for all >= 5.13. > > Mark Chen (2): > UBUNTU: SAUCE: Bluetooth: btusb: Handle download_firmware failure > cases > UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch > status failed > > drivers/bluetooth/btusb.c | 5 +++++ > 1 file changed, 5 insertions(+) > applied to oem-5.13, thanks
On 13.12.21 10:39, You-Sheng Yang wrote: > BugLink: https://bugs.launchpad.net/bugs/1954300 > > [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. > > [Other Info] > > These patches are currently in bluetooth/bluetooth-next.git, and therefore > not yet available to any Ubuntu kernel. Nominated for all >= 5.13. > > Mark Chen (2): > UBUNTU: SAUCE: Bluetooth: btusb: Handle download_firmware failure > cases > UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch > status failed > > drivers/bluetooth/btusb.c | 5 +++++ > 1 file changed, 5 insertions(+) > With the changes pointed out by Tim for Patch 1/2: Acked-by: Kleber Sacilotto de Souza <kleber.souza@canonical.com> Thanks
On 13.12.21 10:39, You-Sheng Yang wrote: > BugLink: https://bugs.launchpad.net/bugs/1954300 > > [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. > > [Other Info] > > These patches are currently in bluetooth/bluetooth-next.git, and therefore > not yet available to any Ubuntu kernel. Nominated for all >= 5.13. > > Mark Chen (2): > UBUNTU: SAUCE: Bluetooth: btusb: Handle download_firmware failure > cases > UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch > status failed > > drivers/bluetooth/btusb.c | 5 +++++ > 1 file changed, 5 insertions(+) > Applied to impish:linux. Thanks, Kleber
On Mon, Dec 13, 2021 at 05:39:06PM +0800, You-Sheng Yang wrote: > BugLink: https://bugs.launchpad.net/bugs/1954300 > > [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. > > [Other Info] > > These patches are currently in bluetooth/bluetooth-next.git, and therefore > not yet available to any Ubuntu kernel. Nominated for all >= 5.13. Applied to jammy:linux updating the backported line to point to the commits from linux-next. Thanks, -Andrea
BugLink: https://bugs.launchpad.net/bugs/1954300 [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. [Other Info] These patches are currently in bluetooth/bluetooth-next.git, and therefore not yet available to any Ubuntu kernel. Nominated for all >= 5.13. Mark Chen (2): UBUNTU: SAUCE: Bluetooth: btusb: Handle download_firmware failure cases UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch status failed drivers/bluetooth/btusb.c | 5 +++++ 1 file changed, 5 insertions(+)