[Bug 220341] New: Bluetooth crashes about 30-40 minutes after I connect my headphones: "Bluetooth: hci0: Hardware error 0x0a"

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=220341

            Bug ID: 220341
           Summary: Bluetooth crashes about 30-40 minutes after I connect
                    my headphones:  "Bluetooth: hci0: Hardware error 0x0a"
           Product: Drivers
           Version: 2.5
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: martin@hignett.net
        Regression: No

Created attachment 308379
  --> https://bugzilla.kernel.org/attachment.cgi?id=308379&action=edit
Kernel log

I have a recurring issue with the Bluetooth stack crashing. 

What am I doing when it crashes?

This has happened 5-6 times in the last week since I got my new laptop. On
every occasion, I'm on a Google video call with my Bluetooth headset connected
(Sony WH-1000MX) in headset mode (mSBC). This happens whether I am using
Firefox or Chrome.

My Hardware

A brand new Lenovo X1 Gen Carbon 13

➜  ~ lspci -nn 
00:00.0 Host bridge [0600]: Intel Corporation Device [8086:6400] (rev 04)
00:02.0 VGA compatible controller [0300]: Intel Corporation Lunar Lake [Intel
Arc Graphics 130V / 140V] [8086:64a0] (rev 04)
00:04.0 Signal processing controller [1180]: Intel Corporation Device
[8086:641d] (rev 04)
00:07.0 PCI bridge [0604]: Intel Corporation Lunar Lake-M Thunderbolt 4 PCI
Express Root Port #0 [8086:a84e] (rev 10)
00:07.2 PCI bridge [0604]: Intel Corporation Lunar Lake-M Thunderbolt 4 PCI
Express Root Port #2 [8086:a860] (rev 10)
00:0a.0 Signal processing controller [1180]: Intel Corporation Device
[8086:647d] (rev 04)
00:0b.0 Processing accelerators [1200]: Intel Corporation Lunar Lake NPU
[8086:643e] (rev 04)
00:0d.0 USB controller [0c03]: Intel Corporation Lunar Lake-M Thunderbolt 4 USB
Controller [8086:a831] (rev 10)
00:0d.2 USB controller [0c03]: Intel Corporation Lunar Lake-M Thunderbolt 4 NHI
#0 [8086:a833] (rev 10)
00:0d.3 USB controller [0c03]: Intel Corporation Lunar Lake-M Thunderbolt 4 NHI
#1 [8086:a834] (rev 10)
00:13.0 Communication controller [0780]: Intel Corporation Device [8086:a862]
(rev 10)
00:14.0 USB controller [0c03]: Intel Corporation Lunar Lake-M USB 3.2 Gen 2x1
xHCI Host Controller [8086:a87d] (rev 10)
00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a87f] (rev 10)
00:14.3 Network controller [0280]: Intel Corporation BE201 320MHz [8086:a840]
(rev 10)
00:14.7 Bluetooth [0d11]: Intel Corporation Device [8086:a876] (rev 10)
00:15.0 Serial bus controller [0c80]: Intel Corporation Lunar Lake-M Serial IO
I2C Controller #0 [8086:a878] (rev 10)
00:15.3 Serial bus controller [0c80]: Intel Corporation Lunar Lake-M Serial IO
I2C Controller #3 [8086:a87b] (rev 10)
00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a870]
(rev 10)
00:1c.0 PCI bridge [0604]: Intel Corporation Lunar Lake-M PCI Express Root Port
#1 [8086:a838] (rev 10)
00:1c.4 PCI bridge [0604]: Intel Corporation Lunar Lake-M PCI Express Root Port
#5 [8086:a83c] (rev 10)
00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a807] (rev 10)
00:1f.3 Multimedia audio controller [0401]: Intel Corporation Lunar Lake-M HD
Audio Controller [8086:a828] (rev 10)
00:1f.4 SMBus [0c05]: Intel Corporation Lunar Lake-M SMbus Controller
[8086:a822] (rev 10)
00:1f.5 Serial bus controller [0c80]: Intel Corporation Lunar Lake-M SPI
Controller [8086:a823] (rev 10)
04:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd
Device [144d:a810]

My Software

Clean install of OpenSuSE Tumbleweed (up to date as of 14th July 2025). I'm not
sure it is relevant, but I'm using systemd-boot instead of Grub.

➜  ~ uname -a                         
Linux martin-work 6.15.5-1-default #1 SMP PREEMPT_DYNAMIC Sun Jul  6 18:09:53
UTC 2025 (478c062) x86_64 x86_64 x86_64 GNU/Linux

What have I tried?

* `sudo systemctl restart bluetooth.service`
* `sudo systemctl restart bluetooth.target`

Neither worked - it seems that the Bluetooth module is hard crashed until I
reboot.


Kernel Logs

Is it possible that this is a hardware error (see the first line in the kernel
log attached)? This is a brand new laptop, so if so, I should return it!

Output of `sudo journalctl --since "11:53" --until "12:00" >
/home/martin/bluetooth-error2.log` attached.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.