This bug is awaiting verification that the linux-oem-6.11/6.11.0-1007.7 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-done- noble-linux-oem-6.11'. If the problem still exists, change the tag 'verification-needed-noble-linux-oem-6.11' to 'verification-failed- noble-linux-oem-6.11'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you! ** Tags added: kernel-spammed-noble-linux-oem-6.11-v2 verification-needed-noble-linux-oem-6.11 -- 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 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 Committed 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/ubuntu/+source/linux/+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
