Jason, we have some more recent builds of the kernel available for debugging purposes. The documentation on how to install them is here: https://wiki.ubuntu.com/Kernel/MainlineBuilds Could you follow those instructions to install the mainline 7.3 kernel and see if the problem persists? You can download it here: https://kernel.ubuntu.com/mainline/v7.3-rc1/ Thanks. -- You received this bug notification because you are subscribed to linux in Ubuntu. Matching subscriptions: Bgg, Bmail, Nb https://bugs.launchpad.net/bugs/2166130 Title: Bluetooth Issue Status in linux package in Ubuntu: Triaged Bug description: btintel_pcie: Lunar Lake Bluetooth controller enters error state after firmware load (regression 7.0.0-28 → 7.0.0-29) Summary Intel Bluetooth (PCI ID 8086:A876) on Lenovo Yoga 9 14ILL10 (Lunar Lake) fails to initialize on kernels 7.0.0-29-generic and 7.0.0-30 generic. The btintel_pcie driver successfully loads both firmware stages (IML and PCI transport), but the controller enters an error state during the post-firmware reset. The “alive interrupt” times out and Intel Soft Reset fails with -ETIME (-62). Bluetooth worked correctly on kernel 7.0.0-28-generic with the same firmware files. The regression was introduced in 7.0.0-29. Steps to Reproduce Boot Lenovo Yoga 9 14ILL10 (model 83LC) with kernel 7.0.0-29-generic or 7.0.0-30-generic Bluetooth controller fails to initialize — bluetoothctl show reports “No default controller available” Expected Behavior Bluetooth controller initializes successfully (as it did on kernel 7.0.0-28-generic). Actual Behavior hciconfig shows hci0 with BD Address 00:00:00:00:00:00, state DOWN, 5 TX errors. bluetoothctlcontroller available.” Driver unbind/rebind reproduces the same failure — not a transient boot issue. show reports “No default System Information Distro: Ubuntu 26.04 (Resolute) Working kernel: 7.0.0-28-generic (confirmed working Aug 2–10, 2026) Broken kernels: 7.0.0-29-generic (7.0.0-29.29) and 7.0.0-30-generic (7.0.0-30.30) Machine: Lenovo Yoga 9 2-in-1 14ILL10, model 83LC SoC: Intel Lunar Lake BIOS: Q9CN22WW (01/09/2025) BT device: PCI 8086:A876, subsystem 8086:000E Driver: btintel_pcie (in-tree, /lib/modules/7.0.0-30-generic/kernel/drivers/bluetooth/btintel_pcie.ko.zst) Firmware: intel/ibt-0190-0291-iml.sfi + intel/ibt-0190-0291-pci.sfi (Firmware Version 107-8.26) linux-firmware: 20260319.git217ca6e4.1ubuntu Kernel Log (dmesg, annotated) Stage 1 — IML firmware: SUCCESS Bluetooth: hci0: Device revision is 0 Bluetooth: hci0: Secure boot is enabled Bluetooth: hci0: OTP lock is disabled Bluetooth: hci0: API lock is enabled Bluetooth: hci0: Debug lock is disabled Bluetooth: hci0: Minimum firmware build 1 week 10 2014 Bluetooth: hci0: Bootloader timestamp 2023.33 buildtype 1 build 45995 Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-iml.sfi Bluetooth: hci0: Boot Address: 0x30098800 Bluetooth: hci0: Firmware Version: 107-8.26 Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 60577 usecs Bluetooth: hci0: Waiting for device to boot Bluetooth: hci0: Device booted in 2195 usecs Bluetooth: hci0: Waiting for device transition to d0 Bluetooth: hci0: Device moved to D0 in 0 usecs Bluetooth: hci0: dsbr: enable: 0x01 value: 0x0b Stage 2 — PCI transport firmware: FAILURE Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfiBluetooth: hci0: Boot Address: 0x10000800 Bluetooth: hci0: Firmware Version: 107-8.26 Bluetooth: hci0: Received gp1 mailbox interrupt ← repeated ~36 times Bluetooth: hci0: Waiting for firmware download to complete Bluetooth: hci0: Firmware loaded in 579658 usecs ← much slower than IML stage Bluetooth: hci0: Received gp1 mailbox interrupt Bluetooth: hci0: Controller in error state ← FAILURE POINT Bluetooth: hci0: Timeout (3000 ms) on alive interrupt, alive context: intel_reset1 Bluetooth: hci0: Failed to send frame (-62) Bluetooth: hci0: sending frame failed (-62) Bluetooth: hci0: Failed to send Intel Reset command Bluetooth: hci0: Intel Soft Reset failed (-62) Retry attempt: SAME FAILURE Bluetooth: hci0: Firmware download retry count: 1 [...IML firmware loads again successfully...] Bluetooth: hci0: Found device firmware: intel/ibt-0190-0291-pci.sfi Bluetooth: hci0: Firmware loaded in 1033894 usecs Bluetooth: hci0: Controller in error state Bluetooth: hci0: Timeout (3000 ms) on alive interrupt, alive context: intel_reset1 Bluetooth: hci0: Intel Soft Reset failed (-62) Bluetooth: hci0: Received hw exception interrupt Bluetooth: hci0: Unsupported cnvi 0x00000000 ← hardware ID unreadable Bluetooth: hci0: Controller in error state Bluetooth: hci0: Failed to read MSFT supported features (-62) Comparison — working boot on 7.0.0-28 (May 29, 2026) Bluetooth: hci0: Device booted in 35237 usecs Bluetooth: hci0: Device moved to D0 in 51 usecs Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-0190-0291-pci.ddc Bluetooth: hci0: Applying Intel DDC parameters completed Bluetooth: hci0: Firmware timestamp 2025.25 buildtype 1 build 95112 Bluetooth: hci0: Firmware SHA1: 0x73cbad49 Bluetooth: hci0: Fseq status: Success (0x00) Bluetooth: hci0: Fseq executed: 00.00.04.202 Bluetooth: hci0: Fseq BT Top: 00.00.04.197 Additional Context rfkill reports Bluetooth as not blocked (soft or hard) The same failure reproduces after manual driver unbind/rebind (not a race condition at boot) A systemd sleep hook (/usr/lib/systemd/system-sleep/bluetooth-wakeup-fix) unbinds/rebinds this device around s2idle to prevent spurious wakeups — this is unrelated to the failure (the failure occurs on fresh boot before any sleep cycle) Kernel 7.0.0-29-generic tested and confirmed broken — same failure as 7.0.0-30 Regression bisected to the 7.0.0-28 → 7.0.0-29 kernel transition ProblemType: Bug DistroRelease: Ubuntu 26.04 Package: linux-image-7.0.0-29-generic 7.0.0-29.29 ProcVersionSignature: Ubuntu 7.0.0-29.29-generic 7.0.12 Uname: Linux 7.0.0-29-generic x86_64 ApportVersion: 2.34.1-0ubuntu0.1 Architecture: amd64 AudioDevicesInUse: USER PID ACCESS COMMAND /dev/snd/controlC0: jkredfoot 6048 F.... pipewire jkredfoot 6063 F.... wireplumber /dev/snd/seq: jkredfoot 6048 F.... pipewire CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Tue Sep 1 22:36:48 2026 InstallationDate: Installed on 2026-02-16 (198 days ago) InstallationMedia: Ubuntu 24.04.3 LTS "Noble Numbat" - Release amd64 (20250805.1) MachineType: LENOVO 83LC ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR=<set> ProcFB: 0 xedrmfb ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-7.0.0-29-generic root=UUID=ff800d1a-2b21-4bc4-a94c-5194f1b6a033 ro quiet splash snd_sof.sof_debug=0x1 snd_soc_sof_sdw.dyndbg=+p crashkernel=2G-4G:320M,4G-32G:512M,32G-64G:1024M,64G-128G:2048M,128G-:4096M PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: linux UpgradeStatus: Upgraded to resolute on 2026-05-14 (110 days ago) dmi.bios.date: 01/09/2025 dmi.bios.release: 1.22 dmi.bios.vendor: LENOVO dmi.bios.version: Q9CN22WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0T76574 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 31 dmi.chassis.vendor: LENOVO dmi.chassis.version: Yoga 9 2-in-1 14ILL10 dmi.ec.firmware.release: 1.22 dmi.modalias: dmi:bvnLENOVO:bvrQ9CN22WW:bd01/09/2025:br1.22:efr1.22:svnLENOVO:pn83LC:pvrYoga92-in-114ILL10:rvnLENOVO:rnLNVNB161216:rvrSDK0T76574WIN:cvnLENOVO:ct31:cvrYoga92-in-114ILL10:skuLENOVO_MT_83LC_BU_idea_FM_Yoga92-in-114ILL10:pfaYoga92-in-114ILL10: dmi.product.family: Yoga 9 2-in-1 14ILL10 dmi.product.name: 83LC dmi.product.sku: LENOVO_MT_83LC_BU_idea_FM_Yoga 9 2-in-1 14ILL10 dmi.product.version: Yoga 9 2-in-1 14ILL10 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2166130/+subscriptions
Комментариев нет:
Отправить комментарий