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

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: [email protected]
          Reporter: [email protected]
        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.

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

Martin Hignett ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

           Hardware|All                         |Intel
     Kernel Version|                            |6.15

You may reply to this email to add a comment.

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

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

--- Comment #1 from Martin Hignett ([email protected]) --- Some more details on the symptoms:

The kernel logs indicate an error in bluez or wireplumber. The entire Bluetooth stack is crashed though - for example, my Bluetooth mouse & keyboard also disconnect and remain disconnected if I restart the two Bluetooth services.

You may reply to this email to add a comment.

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

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

sameer ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #2 from sameer ([email protected]) ---
In your case, Kernel Module Crash happened, Could you please try reloading(using modrpobe/insmod) the module without rebooting the system and let me know here?.

Also After how much time you are observing this behavior?.

Is it happening only in call or it happens in all the cases (For example :Listening to Music etc,)

You may reply to this email to add a comment.

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

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

--- Comment #3 from sameer ([email protected]) --- Time is there in the title, I missed it.

You may reply to this email to add a comment.

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

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

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

                 CC|                            |[email protected],
                   |                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #4 from Paul Menzel ([email protected]) --- Please add the output of dmesg, so more hardware details and the loaded firmware versions are visible. Your log starts with the hardware error below:

    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: Received hw exception
interrupt
    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000000: ff 32 87 80
03 01 01 01 03 01 05 0d 02 00 06 0e
    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000010: 01 00 05 14
0e 1e 00 10 fa 53 06 b0 00 00 00 00
    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000020: 00 00 00 00
00 00 00 00 fa 04 00 00 00 00 40 04
    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000030: 10 00 00 00
    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: 00000000: 10 01 0a
    Jul 15 11:54:59 martin-work kernel: Bluetooth: hci0: Hardware error 0x0a

You may reply to this email to add a comment.

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

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

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #5 from Paul Menzel ([email protected]) --- This seems to be a duplicate of bug 218952 ([URL][1]).

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=218952

You may reply to this email to add a comment.

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

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

--- Comment #6 from Nicolas BARANGER ([email protected]) --- Hi all

Unfortunatly I don't have this laptop anymore (dell xps 15 9530), but from my remember of last summer issue, rmmod -f followed by insmod don't work as rmmod -f was not able to remove the module from the kernel.

The only way I found to recover the situation was to forcely reboot the system .

Also, don't know if it's related but I remmember that I had no issues during the last 2 weeks I used this laptop (corporate laptop) and that was just after removing pcie gen5x2 nvme m2 drive end replacing it by a mdadm done with 2 pcie gen4x4 nvme drive.
Also note that the issue always happens when I was using an Aquantia AQC100S 10gb nic plugged on thunderbolt bus and maybe when cpu total load was higher to 30% on pcie bus
My feeling was an hardware issue at I/O or DMA that kernel don't handle properly

NB: I was using grub and not systemd-boot

You may reply to this email to add a comment.

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

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

--- Comment #7 from Nicolas BARANGER ([email protected]) --- If needed, I don't have the hardware anymore but I still have a backup (dd copy) of lvm drives which hold /usr + /var and /home + /
So maybe I can recover some datas from the issue if it help

You may reply to this email to add a comment.

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

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

--- Comment #8 from Martin Hignett ([email protected]) --- I've been listening to music on my Bluetooth headset all afternoon and not experienced any issues so far (~2 hours). I've not had any video calls, so can't comment on that.

I've attached the output of dmesg from today (note: no Bluetooth errors were experienced today).

You may reply to this email to add a comment.

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

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

--- Comment #9 from Martin Hignett ([email protected]) --- Created attachment 308382
--> https://bugzilla.kernel.org/attachment.cgi?id=308382&action=edit
Output from dmesg

You may reply to this email to add a comment.

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

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

--- Comment #10 from Martin Hignett ([email protected]) ---
This happened again this afternoon. I tried to remove the module, but I got an error that it was in use, even with the -f switch. I looked, and it seemed that some other modules depended on it - including btintel_pcie. I tried to remove that one first... that turned out to be a bad idea! rmmod hung, and lots of things stopped working in random ways. I couldn't even kill the rmmod process. I decided to reboot.

I've attached the output of sudo journalctl -k -b -1 -o short-precise --since "14:40" --until "14:50" > bluetooth-error3.log as bluetooth-error3.log

You may reply to this email to add a comment.

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

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

--- Comment #11 from Martin Hignett ([email protected]) --- Created attachment 308385
--> https://bugzilla.kernel.org/attachment.cgi?id=308385&action=edit
Kernel error logs

Output of sudo journalctl -k -b -1 -o short-precise --since "14:40" --until "14:50" > bluetooth-error3.log

You may reply to this email to add a comment.

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

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

--- Comment #12 from Nicolas BARANGER ([email protected]) --- Hi

When I was still having the hardware involved in the issue, I did constat the exact same behavior as Martin described in
https://bugzilla.kernel.org/show_bug.cgi?id=220341#c10

I don't exactly remember all tests I ve made (a lot of tests), but I'm sure that during an X session (using Xorg or Wayland) I was never able to unload the modules and I think even without X, I has never succeeded to remove it without making the computer crash (when trying to force removal manually and too much hardly)

Regards
Nicolas

You may reply to this email to add a comment.

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

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

--- Comment #13 from Paul Menzel ([email protected]) --- Bug 220344 ([URL][1]) looks like the same problem.

If the developers do not respond, I guess you need to bisect the issue to find the culprit.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=220344

You may reply to this email to add a comment.

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

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

--- Comment #14 from Nicolas BARANGER ([email protected]) --- Hi Martin

Before doing the bisection yourself (except if you wanted to do it yourself) in your case I would post a link to this bugzilla quickly explaning the issue on kernel mailing list "linux-bluetooth".
You can find it on this page:
https://subspace.kernel.org/vger.kernel.org.html

From my experiment it's the best way to discuss with kernel mainteners.

If you want to make the bisection yourself, here is a guide:
https://docs.kernel.org/admin-guide/bug-bisect.html

Unfortunatly I cannot help you bisecting the issue as I don't have the hardware anymore and I cannot reproduce the issue today, but if I can help do not hesitate to ask

Regards
Nicolas

You may reply to this email to add a comment.

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

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

--- Comment #15 from Paul Menzel ([email protected]) --- Dear Nicolas, good points. Just a note, that the Bugzilla messages are sent to the linux-bluetooth list, like the one from you [1], so the Linux Bluetooth maintainers should be aware of the issue.

[1]:
https://lore.kernel.org/linux-bluetooth/[email protected]%2F/T/#mc48c93498be698b142662d7d131c624b98bf5287

You may reply to this email to add a comment.

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

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

--- Comment #16 from Martin Hignett ([email protected]) --- I tried the OpenSuSE LTS kernel (6.12.36) and my laptop failed to boot completely. It printed out this a few times before hanging:

[ T1] ACPIL \: Can't tag data mode

As far as I can tell, no dmesg log was created at all.

I fear the best I might hope for with bisect is finding out which kernel fixed that rather than anything related to this Bluetooth bug...

You may reply to this email to add a comment.

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

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

--- Comment #17 from Nicolas BARANGER ([email protected]) --- @Martin Hignett

What about mainline (6.16-rc6) ?

https://git.kernel.org/torvalds/t/linux-6.16-rc6.tar.gz
or
git clone --depth=1
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git

(I had a lots of IO and netfs issues using Linux 6.10 to 6.13.1 ...)

Regards
Nicolas

You may reply to this email to add a comment.

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

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

--- Comment #18 from Nicolas BARANGER ([email protected]) --- I'm sure it will help if you can reproduce on mainline (and developers would have to work on...)

You may reply to this email to add a comment.

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

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

Paul Menzel ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------
CC| |[email protected]

--- Comment #19 from Paul Menzel ([email protected]) --- If bug 220344 is the same issue, than it happens also with Ubuntu’s 6.8.0-60-generic #63~22.04.1-Ubuntu, though I do not know, what they backport. The bug’s first comment also links to a post saying, this started happening with Linux 6.5.

https://docs.kernel.org/admin-guide/verify-bugs-and-bisect-regressions.html
contains more detailed bisecting information. Especially how to package up the Linux kernel files. For RPM based distributions, that’d be:

    make -j $(nproc --all) binrpm-pkg

You may reply to this email to add a comment.

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

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

Martin Hignett ([email protected]) changed:

What |Removed |Added
----------------------------------------------------------------------------

             Status|NEW                         |RESOLVED
         Resolution|---                         |CODE_FIX

--- Comment #20 from Martin Hignett ([email protected]) ---
Its been a few weeks since I've experienced this issue. I have a feeling that one of that later 6.15.x releases fixed it, but I can't be sure which one.

I propose to close this ticket.

You may reply to this email to add a comment.

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