Skip to contentSkip to conversation

New: Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

Bug 220344 [email protected] 1 participant 11 messages Jul 17, 2025 – Oct 22 Bluetooth drivers

lore
Share & tools
lore
#0 lore raw

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

Bug ID: 220344
Summary: Intel AX211 bluetooth randomly disconnects and
reconnects, started after kernel update
Product: Drivers
Version: 2.5
Hardware: Intel
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: [email protected]
Reporter: [email protected]
Regression: No

Bluetooth devices disconnect every few minutes. Tried same devices with another laptop with same hardware but Windows OS - works fine. So this is not the devices or the Bluetooth hardware.

Every time the disconnect happens, dmesg shows:

Jul 16 13:47:24 licht-t14s kernel: Bluetooth: hci0: Retrieving Intel exception
info failed (-16)
Jul 16 13:47:24 licht-t14s kernel: Bluetooth: hci0: Hardware error 0x0c

I have tried:
- Downloading the newest firmware file from linux-firmware (file ibt-0040-0041.{sfi/ddc}

- Setting the following options in /etc/modprobe.d

# Disable power saving in both iwlmvm and iwlwifi
options iwlmvm power_scheme=1
options iwlwifi power_save=0

# Disable bluetooth coexistence to avoid BT issues options iwlwifi bt_coex_active=0

I have read on Ubuntu's forum (here:
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/2051720) that this may be a regression in kernel 6.5 but I'm on a newer kernel

Hardware info:
System : Lenovo Thinkpad T14s Gen4 model 21F60051IV
BIOS : N3PET23W (1.14)
Adapter : Intel AX211
Firmware: 133-20.25

OS info:
Kernel : Linux licht-t14s 6.8.0-60-generic #63~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Apr 22 19:00:15 UTC 2 x86_64 x86_64 x86_64 GNU/Linux Distro : Ubuntu 22.04.05

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#1 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

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

Paul Menzel ([email protected]) changed:

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

                 CC|                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #1 from Paul Menzel ([email protected]) --- Thank you for your report. Is this a duplicate of bug 220341 ([URL][1])?

If yes, and you ruled out the newer firmware, than bisecting the issue is needed. As it’s not immediately reproducible this might take some time though.

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

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#2 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

--- Comment #2 from Paul Menzel ([email protected]) --- Was the Linux firmware updated on your system, so you actually need to test an *older* firmware version?

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#3 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

--- Comment #3 from Tal Licht ([email protected]) ---
I think this is not the same bug as 220341 - that bug reports the stack crashing and Bluetooth becoming disabled. This is not the case here - it just causes devices to disconnect periodically. I suspect the firmware is crashing and restarting but have no way to verify this. I will try however to switch to some older firmware and see if this stops. Will report the results.

Quoted 13 lines · On Sat, Jul 19, 2025, 15:06 <[email protected]> wrote:

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

--- Comment #2 from Paul Menzel ([email protected])
---
Was the Linux firmware updated on your system, so you actually need to test an
*older* firmware version?

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

You are receiving this mail because:
You reported the bug.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#4 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

--- Comment #4 from Tal Licht ([email protected]) ---
I've tried going back to the bluetooth firmware that was current at the date the computer was originally installed - 9/Sep/2023.

On this date, these firmware files were current:

ibt-0040-0041.sfi - commit 555452997994b250477de4a03b322dc53513d05a dated 2023-08-28
ibt-0040-0041.ddc - commit b7e0c80b00bb4e3d4c845f2270c5c0c8262154ca dated 2021-09-15
iwlwifi-so-a0-gf-a0-86.ucode -
commit f27dec616e29e44cd90645926c1459639d112c3d dated 2023-11-16 - *this is still the current version today*

I switched the files in /lib/firmware to these versions and rebooted:

root@licht-t14s:~# dmesg | grep -E '(hci0|iwlwifi)'
[   30.809390] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[   30.830430] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id
0x80400 wfpm id 0x80000020
[   30.830491] iwlwifi 0000:00:14.3: PCI dev 51f1/0090, rev=0x370,
rfid=0x2010d000
[   30.835929] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
0.0.2.41
*[   30.836818] iwlwifi 0000:00:14.3: loaded firmware version 86.fb5c9aeb.0
so-a0-gf-a0-86.ucode op_mode iwlmvm*
[   30.839236] Bluetooth: hci0: Device revision is 0
[   30.839241] Bluetooth: hci0: Secure boot is enabled
[   30.839242] Bluetooth: hci0: OTP lock is enabled
[   30.839243] Bluetooth: hci0: API lock is enabled
[   30.839244] Bluetooth: hci0: Debug lock is disabled
[   30.839245] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   30.839246] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
build 38
[   30.840962] Bluetooth: hci0: DSM reset method type: 0x00
*[   30.844291] Bluetooth: hci0: Found device firmware:
intel/ibt-0040-0041.sfi*
[   30.844304] Bluetooth: hci0: Boot Address: 0x100800
*[   30.844305] Bluetooth: hci0: Firmware Version: 254-28.23*
[   30.982422] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211
160MHz, REV=0x370
[   31.158040] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   31.158093] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   31.158101] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[   31.158109] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   31.158396] iwlwifi 0000:00:14.3: loaded PNVM version e28bb9d7
[   31.159564] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[   31.174653] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
[   31.244329] iwlwifi 0000:00:14.3: base HW address: 10:f6:0a:05:ba:09
[   31.260051] iwlwifi 0000:00:14.3: iwlmvm doesn't allow to disable BT
Coex, check bt_coex_active module parameter
[   31.294784] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[   31.793193] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   31.793252] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   31.793260] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[   31.793269] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   31.794692] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[   31.892352] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP,
with index: 0
[   32.392539] Bluetooth: hci0: Waiting for firmware download to complete
[   32.393277] Bluetooth: hci0: Firmware loaded in 1512675 usecs
[   32.393369] Bluetooth: hci0: Waiting for device to boot
[   32.409352] Bluetooth: hci0: Device booted in 15680 usecs
*[   32.409513] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-0041.ddc*
[   32.412401] Bluetooth: hci0: Applying Intel DDC parameters completed
*[   32.415476] Bluetooth: hci0: Firmware timestamp 2023.28 buildtype 1
build 68350*
[   32.415482] Bluetooth: hci0: Firmware SHA1: 0xc64314a8
[   32.587297] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587398] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587484] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587627] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)

Bluetooth keyboard, mouse and headphones connected automatically. I then proceeded to play some music in Spotify which in my experience shortens the time until the disconnection issue happens.

Sure enough after less than 1 minute I started hearing bluetooth sound hiccups which indicate a problem with the bluetooth connection. These repeat occasionally.
***However**, *the devices DID NOT disconnect even after 1 hour of continuous use and I did not see the error message I did with the newer firmware:

kernel: Bluetooth: hci0: Hardware error 0x0c

So this is already some improvement. What I can also try is to downgrade the kernel from the HWE version (6.8) to the GA version (5.15) and see if that helps. I'll try that later once I have a grip I know what I'm doing :-)

Quoted 24 lines · Tal Lichtenstein

I think this is not the same bug as 220341 - that bug reports the stack crashing and Bluetooth becoming disabled. This is not the case here - it just causes devices to disconnect periodically. I suspect the firmware is crashing and restarting but have no way to verify this. I will try however to switch to some older firmware and see if this stops. Will report the results.

Quoted 13 lines · On Sat, Jul 19, 2025, 15:06 <[email protected]> wrote:

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

--- Comment #2 from Paul Menzel ( [email protected]) ---
Was the Linux firmware updated on your system, so you actually need to test an
*older* firmware version?

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

You are receiving this mail because:
You reported the bug.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#5 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

--- Comment #5 from Tal Licht ([email protected]) ---
Update - unfortunately Bluetooth did start disconnecting, it only took a bit longer this time. So no improvement even after downgrading the firmware :(

[ 4945.041226] Bluetooth: hci0: Hardware error 0x0c
[ 4945.055323] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[ 5413.818394] Bluetooth: hci0: Hardware error 0x0c
[ 5413.832258] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[ 6078.608374] Bluetooth: hci0: Hardware error 0x0c
[ 6078.622543] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[ 6154.472547] Bluetooth: hci0: Hardware error 0x0c
[ 6154.486464] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[ 6323.107517] Bluetooth: hci0: Hardware error 0x0c
[ 6323.121611] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[ 9253.552312] Bluetooth: hci0: Hardware error 0x0c
[ 9253.566433] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[10010.348140] Bluetooth: hci0: link tx timeout
[10010.348160] Bluetooth: hci0: killing stalled connection 38:18:4c:be:34:1d
[10371.646448] Bluetooth: hci0: Hardware error 0x0a
[10371.660506] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[10547.126313] Bluetooth: hci0: Hardware error 0x0c
[10547.140440] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[10602.005441] Bluetooth: hci0: Hardware error 0x0a
[10602.019402] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[11660.598378] Bluetooth: hci0: Hardware error 0x0a
[11660.612383] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
Quoted 119 lines · Tal Lichtenstein

I've tried going back to the bluetooth firmware that was current at the date the computer was originally installed - 9/Sep/2023.

On this date, these firmware files were current:

ibt-0040-0041.sfi - commit 555452997994b250477de4a03b322dc53513d05a dated 2023-08-28
ibt-0040-0041.ddc - commit b7e0c80b00bb4e3d4c845f2270c5c0c8262154ca dated 2021-09-15
iwlwifi-so-a0-gf-a0-86.ucode -
commit f27dec616e29e44cd90645926c1459639d112c3d dated 2023-11-16 - *this is still the current version today*

I switched the files in /lib/firmware to these versions and rebooted:

root@licht-t14s:~# dmesg | grep -E '(hci0|iwlwifi)'
[   30.809390] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[   30.830430] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id
0x80400 wfpm id 0x80000020
[   30.830491] iwlwifi 0000:00:14.3: PCI dev 51f1/0090, rev=0x370,
rfid=0x2010d000
[   30.835929] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
0.0.2.41
*[   30.836818] iwlwifi 0000:00:14.3: loaded firmware version
86.fb5c9aeb.0 so-a0-gf-a0-86.ucode op_mode iwlmvm*
[   30.839236] Bluetooth: hci0: Device revision is 0
[   30.839241] Bluetooth: hci0: Secure boot is enabled
[   30.839242] Bluetooth: hci0: OTP lock is enabled
[   30.839243] Bluetooth: hci0: API lock is enabled
[   30.839244] Bluetooth: hci0: Debug lock is disabled
[   30.839245] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   30.839246] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
build 38
[   30.840962] Bluetooth: hci0: DSM reset method type: 0x00
*[   30.844291] Bluetooth: hci0: Found device firmware:
intel/ibt-0040-0041.sfi*
[   30.844304] Bluetooth: hci0: Boot Address: 0x100800
*[   30.844305] Bluetooth: hci0: Firmware Version: 254-28.23*
[   30.982422] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211
160MHz, REV=0x370
[   31.158040] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   31.158093] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   31.158101] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[   31.158109] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   31.158396] iwlwifi 0000:00:14.3: loaded PNVM version e28bb9d7
[   31.159564] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[   31.174653] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
[   31.244329] iwlwifi 0000:00:14.3: base HW address: 10:f6:0a:05:ba:09
[   31.260051] iwlwifi 0000:00:14.3: iwlmvm doesn't allow to disable BT
Coex, check bt_coex_active module parameter
[   31.294784] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[   31.793193] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   31.793252] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   31.793260] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[   31.793269] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   31.794692] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[   31.892352] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP,
with index: 0
[   32.392539] Bluetooth: hci0: Waiting for firmware download to complete
[   32.393277] Bluetooth: hci0: Firmware loaded in 1512675 usecs
[   32.393369] Bluetooth: hci0: Waiting for device to boot
[   32.409352] Bluetooth: hci0: Device booted in 15680 usecs
*[   32.409513] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-0041.ddc*
[   32.412401] Bluetooth: hci0: Applying Intel DDC parameters completed
*[   32.415476] Bluetooth: hci0: Firmware timestamp 2023.28 buildtype 1
build 68350*
[   32.415482] Bluetooth: hci0: Firmware SHA1: 0xc64314a8
[   32.587297] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587398] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587484] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587627] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)

Bluetooth keyboard, mouse and headphones connected automatically. I then proceeded to play some music in Spotify which in my experience shortens the time until the disconnection issue happens.

Sure enough after less than 1 minute I started hearing bluetooth sound hiccups which indicate a problem with the bluetooth connection. These repeat occasionally.
***However**, *the devices DID NOT disconnect even after 1 hour of continuous use and I did not see the error message I did with the newer firmware:

kernel: Bluetooth: hci0: Hardware error 0x0c

So this is already some improvement. What I can also try is to downgrade the kernel from the HWE version (6.8) to the GA version (5.15) and see if that helps. I'll try that later once I have a grip I know what I'm doing :-)

Quoted 24 lines · Tal Lichtenstein

I think this is not the same bug as 220341 - that bug reports the stack crashing and Bluetooth becoming disabled. This is not the case here - it just causes devices to disconnect periodically. I suspect the firmware is crashing and restarting but have no way to verify this. I will try however to switch to some older firmware and see if this stops. Will report the results.

Quoted 13 lines · On Sat, Jul 19, 2025, 15:06 <[email protected]> wrote:

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

--- Comment #2 from Paul Menzel ( [email protected]) ---
Was the Linux firmware updated on your system, so you actually need to test an
*older* firmware version?

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

You are receiving this mail because:
You reported the bug.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#6 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

--- Comment #6 from Tal Licht ([email protected]) --- I've also tried downgrading to the GA kernel (5.15). When I boot this the Wifi driver (iwlwifi) doesn't even load and my external USB-C monitor does not initialize at all.
So using this is not an option :-)

Quoted 160 lines · Tal Lichtenstein

Update - unfortunately Bluetooth did start disconnecting, it only took a bit longer this time. So no improvement even after downgrading the firmware :(

[ 4945.041226] Bluetooth: hci0: Hardware error 0x0c
[ 4945.055323] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[ 5413.818394] Bluetooth: hci0: Hardware error 0x0c
[ 5413.832258] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[ 6078.608374] Bluetooth: hci0: Hardware error 0x0c
[ 6078.622543] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[ 6154.472547] Bluetooth: hci0: Hardware error 0x0c
[ 6154.486464] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[ 6323.107517] Bluetooth: hci0: Hardware error 0x0c
[ 6323.121611] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[ 9253.552312] Bluetooth: hci0: Hardware error 0x0c
[ 9253.566433] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[10010.348140] Bluetooth: hci0: link tx timeout
[10010.348160] Bluetooth: hci0: killing stalled connection
38:18:4c:be:34:1d
[10371.646448] Bluetooth: hci0: Hardware error 0x0a
[10371.660506] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[10547.126313] Bluetooth: hci0: Hardware error 0x0c
[10547.140440] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[10602.005441] Bluetooth: hci0: Hardware error 0x0a
[10602.019402] Bluetooth: hci0: Retrieving Intel exception info failed
(-16)
[11660.598378] Bluetooth: hci0: Hardware error 0x0a
[11660.612383] Bluetooth: hci0: Retrieving Intel exception info failed

(-16)

Quoted 120 lines · Tal Lichtenstein

I've tried going back to the bluetooth firmware that was current at the date the computer was originally installed - 9/Sep/2023.

On this date, these firmware files were current:

ibt-0040-0041.sfi - commit 555452997994b250477de4a03b322dc53513d05a dated 2023-08-28
ibt-0040-0041.ddc - commit b7e0c80b00bb4e3d4c845f2270c5c0c8262154ca dated 2021-09-15
iwlwifi-so-a0-gf-a0-86.ucode -
commit f27dec616e29e44cd90645926c1459639d112c3d dated 2023-11-16 - *this is still the current version today*

I switched the files in /lib/firmware to these versions and rebooted:

root@licht-t14s:~# dmesg | grep -E '(hci0|iwlwifi)'
[   30.809390] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[   30.830430] iwlwifi 0000:00:14.3: Detected crf-id 0x400410, cnv-id
0x80400 wfpm id 0x80000020
[   30.830491] iwlwifi 0000:00:14.3: PCI dev 51f1/0090, rev=0x370,
rfid=0x2010d000
[   30.835929] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version:
0.0.2.41
*[   30.836818] iwlwifi 0000:00:14.3: loaded firmware version
86.fb5c9aeb.0 so-a0-gf-a0-86.ucode op_mode iwlmvm*
[   30.839236] Bluetooth: hci0: Device revision is 0
[   30.839241] Bluetooth: hci0: Secure boot is enabled
[   30.839242] Bluetooth: hci0: OTP lock is enabled
[   30.839243] Bluetooth: hci0: API lock is enabled
[   30.839244] Bluetooth: hci0: Debug lock is disabled
[   30.839245] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   30.839246] Bluetooth: hci0: Bootloader timestamp 2019.40 buildtype 1
build 38
[   30.840962] Bluetooth: hci0: DSM reset method type: 0x00
*[   30.844291] Bluetooth: hci0: Found device firmware:
intel/ibt-0040-0041.sfi*
[   30.844304] Bluetooth: hci0: Boot Address: 0x100800
*[   30.844305] Bluetooth: hci0: Firmware Version: 254-28.23*
[   30.982422] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6E AX211
160MHz, REV=0x370
[   31.158040] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   31.158093] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   31.158101] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[   31.158109] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   31.158396] iwlwifi 0000:00:14.3: loaded PNVM version e28bb9d7
[   31.159564] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[   31.174653] iwlwifi 0000:00:14.3: Detected RF GF, rfid=0x2010d000
[   31.244329] iwlwifi 0000:00:14.3: base HW address: 10:f6:0a:05:ba:09
[   31.260051] iwlwifi 0000:00:14.3: iwlmvm doesn't allow to disable BT
Coex, check bt_coex_active module parameter
[   31.294784] iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0
[   31.793193] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[   31.793252] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[   31.793260] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[   31.793269] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x0
[   31.794692] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[   31.892352] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP,
with index: 0
[   32.392539] Bluetooth: hci0: Waiting for firmware download to complete
[   32.393277] Bluetooth: hci0: Firmware loaded in 1512675 usecs
[   32.393369] Bluetooth: hci0: Waiting for device to boot
[   32.409352] Bluetooth: hci0: Device booted in 15680 usecs
*[   32.409513] Bluetooth: hci0: Found Intel DDC parameters:
intel/ibt-0040-0041.ddc*
[   32.412401] Bluetooth: hci0: Applying Intel DDC parameters completed
*[   32.415476] Bluetooth: hci0: Firmware timestamp 2023.28 buildtype 1
build 68350*
[   32.415482] Bluetooth: hci0: Firmware SHA1: 0xc64314a8
[   32.587297] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587398] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587484] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[   32.587627] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)

Bluetooth keyboard, mouse and headphones connected automatically. I then proceeded to play some music in Spotify which in my experience shortens the time until the disconnection issue happens.

Sure enough after less than 1 minute I started hearing bluetooth sound hiccups which indicate a problem with the bluetooth connection. These repeat occasionally.
***However**, *the devices DID NOT disconnect even after 1 hour of continuous use and I did not see the error message I did with the newer firmware:

kernel: Bluetooth: hci0: Hardware error 0x0c

So this is already some improvement. What I can also try is to downgrade the kernel from the HWE version (6.8) to the GA version (5.15) and see if that helps. I'll try that later once I have a grip I know what I'm doing :-)

Quoted 24 lines · Tal Lichtenstein

I think this is not the same bug as 220341 - that bug reports the stack crashing and Bluetooth becoming disabled. This is not the case here - it just causes devices to disconnect periodically. I suspect the firmware is crashing and restarting but have no way to verify this. I will try however to switch to some older firmware and see if this stops. Will report the results.

Quoted 13 lines · On Sat, Jul 19, 2025, 15:06 <[email protected]> wrote:

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

--- Comment #2 from Paul Menzel ( [email protected]) ---
Was the Linux firmware updated on your system, so you actually need to test an
*older* firmware version?

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

You are receiving this mail because:
You reported the bug.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#7 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

Juerg Haefliger ([email protected]) changed:

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

--- Comment #7 from Juerg Haefliger ([email protected]) --- This looks like:
https://bugs.launchpad.net/bugs/2049676

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#8 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

Guy Rutenberg ([email protected]) changed:

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

--- Comment #8 from Guy Rutenberg ([email protected]) --- Hi,

I have the exact same issue on similar hardware - Lenovo T14 Gen4. It started a while ago (more than a year). The issue manifests itself only in certain
locations: The same computer and bluetooth headset work perfectly fine in my office, but I get the hiccups and disconnects at home.

I've already tried everything Tal wrote down as well. I've tried various kernels and downgraded the iwlwifi firmware all the way back to Dec 2022 and couldn't find the version it worked properly with.

I'm running kernel 6.18.15+deb14-amd64, Debian Unstable.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#9 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

Christopher Trom ([email protected]) changed:

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

--- Comment #9 from Christopher Trom ([email protected]) --- Adding a data point - same symptoms on current software, with a couple of workarounds ruled out.

SYSTEM

Hardware: Intel Wi-Fi 6E AX211 160MHz (CNVi combo WiFi/BT; BT enumerates as USB 8087:0033 via btusb/btintel)
Distro: Arch Linux
Kernel: 7.2.7-arch1-1
linux-firmware: 20260916-1 (current at time of testing)
Bluetooth modules: btusb, btintel (not btintel_pcie - BT side is USB-enumerated despite WiFi being PCIe)
WiFi modules: iwlwifi, iwlmvm

Both kernel and firmware were current as of testing.

SYMPTOM

Same as OP: Bluetooth headphones disconnect, recovering automatically within a couple of seconds. dmesg/journal shows:

kernel: Bluetooth: hci0: Hardware error 0x0c
kernel: Bluetooth: hci0: Retrieving Intel exception info failed (-16)

followed by bluetoothd/wireplumber/pipewire reporting the audio transport failing and reconnecting:

wireplumber: pw.node: (bluez_output.<MAC>.1-XX) running -> error (Received error event)
wireplumber: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_<MAC>/fd0
bluetoothd: profiles/audio/avdtp.c:handle_unanswered_req() No reply to Suspend request
bluetoothd: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected
(107)

FREQUENCY / TIMING

Crashes recorded in one session (single boot), timestamps and gaps between them:

21:21:40

21:29:17  (+7:37)
23:19:54  (separate session, same boot)
23:24:46  (+4:52)
23:30:36  (+5:50, no accompanying Hardware error - just a transport disconnect

w/ no crash)
23:35:34 (+4:58, no accompanying Hardware error)
23:37:17 (+1:43, + Hardware error)

No consistent period. Looked like it might be ~5 minutes for a stretch, but that broke down (see the 1:43 gap).

THINGS I TRIED TO IDENTIFY A TRIGGER

1. WiFi AP roaming

Initially looked correlated (a crash followed a WiFi roam event by ~7s), since this is a combo WiFi/BT chip. Pinned the NetworkManager WiFi connection to a single AP's BSSID + 5GHz band to eliminate roaming entirely:

nmcli con modify <conn> 802-11-wireless.bssid <BSSID> 802-11-wireless.band a

Confirmed via nmcli con show that the pin was active and WiFi stayed on one BSSID. A Hardware error 0x0c crash still occurred 3.5 minutes into a stable, non-roaming WiFi connection, ruling out roaming as the (sole) trigger.

2. BT/WiFi coexistence + power-saving

Tried disabling hardware coexistence arbitration and power management via modprobe options:

options iwlwifi bt_coex_active=0
options iwlwifi power_save=0
options iwlmvm power_scheme=1
options btusb enable_autosuspend=0

Rebuilt initramfs (mkinitcpio -P) and rebooted; verified all four parameters took effect via /sys/module/*/parameters/*. A Hardware error 0x0c crash with identical signature still occurred 3m20s after boot, with coexistence and power-saving both disabled.

At this point the trigger doesn't appear to be WiFi-roaming-related or coexistence/power-management-related. I'm open to suggestions on what else to test (increased BT debug verbosity, btmon capture during a crash, etc.) if useful for the bug report.

Signature · 4 lines
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.
#10 lore raw

[Bug 220344] Intel AX211 bluetooth randomly disconnects and reconnects, started after kernel update

In reply to [email protected]

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

Akshay ([email protected]) changed:

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

--- Comment #10 from Akshay ([email protected]) ---
I have been encountering the same issue and it seems to be due to how the Intel CNVi Bluetooth chips interact with headphones that have both BLE and BR/EDR capabilities and how the kernel enabled L2CAP ecred and ertm by default.

Setting "ControllerMode = bredr" in /etc/bluetooth/main.conf and restarting bluetooth.service completely and permanently eliminates all dropouts.

Here's a complete description (AI-assisted):

A recurring Bluetooth audio dropout issue affecting Intel CNVi Bluetooth adapters (specifically the AX211, 8087:0033) paired with dual-mode (BR/EDR + LE) headsets such as the Sennheiser Momentum 4.

Below is the detailed bug report along with evidence from btsnoop packet traces, root-cause analysis, and reproduction steps.

1. ENVIRONMENT & HARDWARE
-------------------------
- Adapter: Intel Wi-Fi 6E AX211 160MHz CNVi (8087:0033, hci0)
- OS: Fedora Linux 44 (KDE Plasma Desktop Edition) x86_64
- Kernel: Linux 7.2.11-200.fc44.x86_64
- Firmware: ibt-1040-0041.sfi (both production and build 82200 tested)
- Driver: btusb / btintel (Linux 6.11.x through 7.2.x, Fedora 44)
- Audio Stack: PipeWire 1.6.9 + WirePlumber 0.5.18, standard A2DP (reproduced on SBC, AAC, and aptX HD)
- Headset: Sennheiser MOMENTUM 4 (80:C3:BA:4D:8A:F2)
(Also reproducible on other dual-mode BR/EDR+LE headphones)

2. PROBLEM DESCRIPTION
----------------------
When streaming Classic A2DP audio from Linux to a dual-mode headset, the stream suffers brief audible audio dropouts / glitches every 5.0 to 5.4 seconds.

In extended listening sessions, cumulative starvation events eventually trigger an internal controller watchdog crash:
kernel: Bluetooth: hci0: Hardware error 0x0c

During each glitch, PipeWire logs:
spa.bluez5.sink.media: Missing completion reports for packet:
Bluetooth adapter firmware bug?

3. EVIDENCE FROM BTSNOOP TRACES
------------------------------------------
In Bluetooth Core Specifications, baseband time is partitioned into discrete 625-microsecond slots.

Converting the measured stall intervals from btsnoop packet captures directly into baseband slots proves the collision originates inside the controller's internal LE baseband scheduling loop:

Metric Measured in btsnoop Baseband Calculation (625 us)
-------------------------------------------------------------------------
Recurrence Period 5.118s - 5.122s 8,192 slots * 625 us = 5.1200s
Single-Window Stall 138.7ms - 146.5ms 224 slots * 625 us = 140.00ms
Double-Window Stall 281.2ms - 287.0ms 448 slots * 625 us = 280.00ms

Trace Snapshot (Buffer Credit Depletion):
Frame 758 | t = 5.0456s | ACL_TX | in_flight = 0
Frame 759 | t = 5.0589s | ACL_TX | in_flight = 1
Frame 760 | t = 5.0722s | ACL_TX | in_flight = 2
Frame 761 | t = 5.0856s | ACL_TX | in_flight = 3 (BUFFER FULL: 0
credits)

      ---------- INTEL CONTROLLER CEASES ACKing FOR 145.6 ms ----------         
      Frame 762 | t = 5.2312s | EVT_ACK(1) | in_flight = 2 (Controller ACKs)    
      Frame 763 | t = 5.2313s | ACL_TX     | in_flight = 3 (Host sends next

pkt)

During normal streaming, ACL packet intervals are ~12.25 ms. Because the Intel AX211 advertises an ACL buffer depth of only 3 packets (ACL max
packets: 3), a radio pause of 140 ms requires at least 11 packets of buffer capacity. The 3-packet buffer fills in ~36 ms, blocking the host stack for the remaining >100 ms and starving the headset DSP buffer.

4. ROOT CAUSE ANALYSIS
----------------------
1. When BlueZ boots in default "ControllerMode = dual", the kernel issues HCI_OP_WRITE_LE_SUPPORT(1) to the controller.
2. Even with zero active LE connections, entering Dual-Mode activates an internal firmware baseband routine (LE calibration / periodic background scan reservation) scheduled on an exact 2^13 slot cadence (8,192 slots = 5.120 seconds).
3. When this timer triggers, the AX211 baseband arbiter grants the radio exclusively to the LE state machine for 224 to 448 slots (140 to 280
ms),
completely halting BR/EDR transmission and packet acknowledgments.
4. Older audio architectures (PulseAudio with 250-500 ms ALSA buffers) masked this radio blackout in software. Modern low-latency servers (PipeWire) operate with tight pacing (10-20 ms), making the baseband blackout directly audible.
5. In pure BR/EDR mode ("ControllerMode = bredr"), BlueZ commands MGMT_SET_LE(0) -> HCI_OP_WRITE_LE_SUPPORT(0). The LE state machine remains completely dormant, and the 5.120s timer never runs.

5. WORKAROUND & VERIFICATION
----------------------------
Setting "ControllerMode = bredr" in /etc/bluetooth/main.conf and restarting bluetooth.service completely and permanently eliminates all dropouts:
- Gaps > 25ms: 0
- Inter-packet interval: 12.25 ms +/- 0.08 ms
- Audible stutters / dropouts: 0
- Hardware error 0x0c resets: 0

No kernel configuration changes (enable_ecred, disable_ertm), no PipeWire buffer overrides, no codec changes, and no power management overrides were required. Pure BR/EDR mode alone fixes the issue.

6. PROPOSED PERMANENT SOLUTIONS
-------------------------------
1. Intel Firmware (ibt-*.sfi):
The AX211 baseband scheduler should prioritize active BR/EDR ACL audio streams over internal LE background calibration/scanning, or preempt the LE routine so that BR/EDR transmission is never paused for more than 15-20 ms.

2. Kernel Driver (drivers/bluetooth/btintel.c):
If the firmware scheduler cannot be updated, btintel could provide a mechanism or quirk to temporarily throttle or mask background LE support/scheduling when high-throughput BR/EDR A2DP streams are active on single-radio CNVi controllers.

I can provide btsnoop packet captures if needed.

Signature · 4 lines
You may reply to this email to add a comment.

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