This bug was fixed in the package linux-oem-6.11 - 6.11.0-1007.7
---------------
linux-oem-6.11 (6.11.0-1007.7) noble; urgency=medium
* noble/linux-oem-6.11: 6.11.0-1007.7 -proposed tracker (LP: #2085318)
* iwlwifi 0000:00:14.3: Failed to start RT ucode: -110 (LP: #2085504)
- SAUCE: Revert "wifi: iwlwifi: remove retry loops in start"
* Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported
features (-110)" (LP: #2085485)
- Bluetooth: btintel_pcie: Add handshake between driver and firmware
- Bluetooth: btintel_pcie: Add recovery mechanism
* Fix phantom monitor on some machines with kernel 6.11 (LP: #2085456)
- SAUCE: Revert "video/aperture: optionally match the device in
sysfb_disable()"
* BT Switch cannot open under Ubuntu 24.04 on MT7920 (LP: #2085437)
- SAUCE: Bluetooth: btmtk: Remove resetting mt7921 before downloading the fw
* OVTI08F4:00: number of CSI2 data lanes 2 is not supported (LP: #2084059)
- SAUCE: media: ipu-bridge: Add support for additional link frequencies
* Fix USB device suspend failure while HCD in S4 wakeup (LP: #2085410)
- SAUCE: USB: Fix the issue of task recovery failure caused by USB status
when
S4 wakes up
* [SRU] add support of QCA BT 0489:e0fc (LP: #2085406)
- SAUCE: Bluetooth: btusb: add Foxconn 0xe0fc for Qualcomm WCN785x
* The ASPM is disabled on Realtek NIC which prevents the system from entering
s0ix (LP: #2085398)
- SAUCE: r8169: Add Dell platforms to the ASPM quirk
* r8169: transmit queue 0 timed out error when re-plugging the Ethernet cable
(LP: #2084526)
- r8169: disable ALDPS per default for RTL8125
* Service LED will show 1A8W when unplug WD22TB4 with TBT3 HDD then resume
from suspend (LP: #2082225)
- SAUCE: PCI: pciehp: Fix system hang during resume with daisy-chained
hotplug
controllers
* AMD ACP7.1 support (LP: #2077941)
- ASoC: amd: acp: add ZSC control register programming sequence
- ASoC: amd: acp: add legacy driver support for ACP7.1 based platforms
* Support ov05c10 camera sensor in Intel ipu-bridge (LP: #2081866)
- SAUCE: media: Support ov05c10 camera sensor
* Dell Alienware sysytem reports errors of dell_wmi_sysman and dell_smbios in
demsg (LP: #2084808)
- platform/x86: dell-sysman: add support for alienware products
* Intel(R) PRO/1000 I219 ethernet adapter [8086:550c] may block entrance of
modern standby (LP: #2081130)
- platform/x86: intel/pmc: Ignore all LTRs during suspend
- e1000e: change I219 (19) devices to ADP
- x86/apic: Always explicitly disarm TSC-deadline timer
* Fix distorted sound output after suspend more than 30 seconds on Cirrus
audio codec (LP: #2084759)
- SAUCE: mfd: cs42l43: Disable IRQs during suspend
* Dell AIO backlight is not working, dell_uart_backlight module is missing
(LP: #2083800)
- [Config] enable CONFIG_DELL_UART_BACKLIGHT
* Add Intel Arrow Lake-H LPSS PCI IDs (LP: #2083905)
- mfd: intel-lpss: Add Intel Arrow Lake-H LPSS PCI IDs
* Missing device ID for amd_atl driver for AMD Strix platform (LP: #2083292)
- SAUCE: x86/amd_nb: Add new PCI ID for AMD family 1Ah model 20h
* Need driver support for Realtek RTL8126A rev.b 5Gbps ethernet [10ec:8126]
(LP: #2079017)
- r8169: add support for RTL8126A rev.b
- r8169: add missing MODULE_FIRMWARE entry for RTL8126A rev.b
* Missing devices nodes for AMD Instinct MI300 card when installed along with
integrated display (LP: #2078773)
- drm: Use XArray instead of IDR for minors
- accel: Use XArray instead of IDR for minors
- drm: Expand max DRM device number to full MINORBITS
* UBSAN: array-index-out-of-bounds in module mt76 (LP: #2081785)
- wifi: mt76: mt7925: fix a potential array-index-out-of-bounds issue for
clc
* Support Qualcomm WCN7851 Dual Bluetooth Adapter 0489:E0F3 (LP: #2081796)
- SAUCE: Bluetooth: btusb: Add one more ID 0x0489:0xe0f3 for Qualcomm
WCN785x
* [SRU] uncore: Add ARL and LNL support on 6.11 (LP: #2081810)
- perf/x86/intel/uncore: Add Arrow Lake support
- perf/x86/intel/uncore: Factor out common MMIO init and ops functions
- perf/x86/intel/uncore: Add Lunar Lake support
- perf/x86/intel/uncore: Add LNL uncore iMC freerunning support
- perf/x86/intel/uncore: Use D0:F0 as a default device
[ Ubuntu: 6.11.0-9.9 ]
* oracular/linux: 6.11.0-9.9 -proposed tracker (LP: #2084250)
* re-enable Ubuntu FAN in the Noble kernel (LP: #2064508)
- SAUCE: fan: add VXLAN implementation
- SAUCE: fan: Fix NULL pointer dereference
- SAUCE: fan: support vxlan strict length validation
* update for V3 kernel bits and improved multiple fan slice support
(LP: #1470091) // re-enable Ubuntu FAN in the Noble kernel (LP: #2064508)
- SAUCE: fan: tunnel multiple mapping mode (v3)
* Setting I/O scheduler to 'none' causes error in oracular (LP: #2083845)
- block: Fix elv_iosched_local_module handling of "none" scheduler
* Miscellaneous Ubuntu changes
- [Config] Update toolchain versions
-- Kuan-Ying Lee <kuan-ying....@canonical.com> Thu, 24 Oct 2024
15:45:12 +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 in Ubuntu.
https://bugs.launchpad.net/bugs/2085485
Title:
Bluetooth[8086:a876] crash with "hci0: Failed to read MSFT supported
features (-110)"
Status in HWE Next:
New
Status in linux package in Ubuntu:
In Progress
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.11 source package in Noble:
Fix Released
Status in linux source package in Oracular:
In Progress
Status in linux-oem-6.11 source package in Oracular:
Invalid
Status in linux source package in Plucky:
In Progress
Status in linux-oem-6.11 source package in Plucky:
Invalid
Bug description:
[Impact]
Encounter "hci0: Failed to read MSFT supported features (-110)" while doing
reboot stress test.
[Fix]
Intel provides 2 commits the fix this issue which is included in the
linux-next now.
04c41b875f5b Bluetooth: btintel_pcie: Add recovery mechanism
f4c8e876ef6b Bluetooth: btintel_pcie: Add handshake between driver and
firmware
[Test]
Reboot stress test on the machine with PCIe BT[8086:a876], the BT should work
during 100+ reboots.
[Where problems could occur]
The 2 patches affect the boot process and the handshake between driver and
firmware, so if it leads to any regression you could spot it easily after boot
up. And another patch adds a recovery mechanism to recover controller if
firmware download fails. So, it should be robust enough to overcome the boot
regression.
To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2085485/+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
