This bug was fixed in the package linux-oem-6.11 - 6.11.0-1012.12
---------------
linux-oem-6.11 (6.11.0-1012.12) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1012.12 -proposed tracker (LP:
#2093384)
* Stuck forever while accessing HID-SENSOR-200011.5.auto/iio:device1 device
(LP: #2093315)
- SAUCE: iio: hid-sensor-attributes: validate sensitivity attributes
* Fix audio output fail after resume from suspend with CS42L43 codec
(LP: #2093330)
- SAUCE: ASoC: cs42l43: Add codec force suspend/resume ops
* Enable Realtek NIC ASPM on one Dell Tower platform (LP: #2091352)
- SAUCE: r8169: enable rtl8168h/rtl8125/rtl8126 ltr support
- SAUCE: r8169: fix cannot enter l1ss issue
- SAUCE: r8169: Add one Dell platform to the ASPM quirk
- SAUCE: r8169: remove ASPM quirk RTL_GIGA_MAC_VER_46 restrict
* mt7925: system will sometimes hang while rebooting (LP: #2092746)
- Bluetooth: btusb: mediatek: move Bluetooth power off command position
- Bluetooth: btusb: mediatek: add callback function in btusb_disconnect
- Bluetooth: btusb: mediatek: add intf release flow when usb disconnect
- Bluetooth: btusb: mediatek: change the conditions for ISO interface
* [SRU] Fix system hang issue caused by the btmtk driver (LP: #2092473)
- Bluetooth: btmtk: adjust the position to init iso data anchor
* Hotplug in HDMI cable on the dock leads to many xe driver warning messages
(LP: #2092373)
- drm/i915/dp: Fix AUX IO power enabling for eDP PSR
* xe driver can't detect hotplug monitor (LP: #2092186)
- drm/xe: Remove runtime argument from display s/r functions
- drm/xe: Fix missing conversion to xe_display_pm_runtime_resume
- drm/xe/display: Separate the d3cold and non-d3cold runtime PM handling
- drm/xe/display: Add missing HPD interrupt enabling during non-d3cold RPM
resume
-- Kuan-Ying Lee <kuan-ying....@canonical.com> Fri, 10 Jan 2025
14:49:02 +0800
** Changed in: linux-oem-6.11 (Ubuntu Noble)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux-oem-6.11 in Ubuntu.
https://bugs.launchpad.net/bugs/2092473
Title:
[SRU] Fix system hang issue caused by the btmtk driver
Status in HWE Next:
New
Status in linux-oem-6.11 package in Ubuntu:
New
Status in linux-oem-6.11 source package in Noble:
Fix Released
Bug description:
[ Impact ]
On some machine with Mediatek USB bluetooth controller, activate
scanning will lead to system hang. This is due to unexpected null
pointer dereference in the set up flow.
[ Fix ]
Cherry-pick one commit from mainline linux:
61c5a3def90a (Bluetooth: btmtk: adjust the position to init iso
data anchor)
[ Test ]
1. Boot into the kenrel
2. Run bluetoothctl
3. In the bluetoothctl shell, run "scan on"
4. The MTK bluetooth usb device should be able to scan, and system should not
hang.
[ Where problems could occur ]
The call trace in the upstream commit shows that the intention for the
patch is to fix what was happening unexpected USB disconnect. However,
here in 6.11-oem the btusb_mtk_disconnect() in the call trace, which
is what usb_kill_anchored_urbs() an uninitailized usb anchor and lead
to the error, is not even implemented.
From the call trace collected we collected, the code path seems to be
btusb_disconnect()->hci_unregister_dev()->btmtk shutdwn callback.
However they all lead to calling the usb_kill_anchored_urbs() before
the same btmtk_data->isopkt_anchor is initialized by the
init_usb_anchor(). That's probably why the patch could fix the issue
here as well.
The upstream patch author didn't state when or why such "unexpected
USB disconnect during setup" might happen.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2092473/+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
