Bluetooth Broken In Kernel Versions 6.5+ (Intel AX210)

[Dustin Falgout]

```
kernel: Bluetooth: hci0: command 0xfc05 tx timeout
```

This issue started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel.

```
$ uname -a

Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```

```
$ lsusb | grep -i bluetooth

Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
```

```
$ journalctl -b | egrep -i bluetooth

Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
```

```
linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic]
```
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu82.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC3: dustin 2472 F.... pulseaudio
 /dev/snd/controlC2: dustin 2472 F.... pulseaudio
 /dev/snd/controlC0: dustin 2472 F.... pulseaudio
 /dev/snd/controlC1: dustin 2472 F.... pulseaudio
CRDA: N/A
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
DistroRelease: KDE neon 22.04
MachineType: Gigabyte Technology Co., Ltd. B650M AORUS ELITE AX
NonfreeKernelModules: zfs
Package: linux (not installed)
ProcFB: 0 amdgpudrmfb
ProcKernelCmdLine: root=zfs:zpool/ubuntu/SYSTEM quiet splash spl.spl_hostid=0x00bab10c
ProcVersionSignature: Ubuntu 6.5.0-21.21~22.04.1-generic 6.5.8
RelatedPackageVersions:
 linux-restricted-modules-6.5.0-21-generic N/A
 linux-backports-modules-6.5.0-21-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu3.29
Tags: jammy
Uname: Linux 6.5.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: docker sudo vboxusers
WifiSyslog:

_MarkForUpload: True
dmi.bios.date: 01/10/2024
dmi.bios.release: 5.31
dmi.bios.vendor: American Megatrends International, LLC.
dmi.bios.version: F21
dmi.board.asset.tag: Default string
dmi.board.name: B650M AORUS ELITE AX
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.asset.tag: Default string
dmi.chassis.type: 3
dmi.chassis.vendor: Default string
dmi.chassis.version: Default string
dmi.modalias: dmi:bvnAmericanMegatrendsInternational,LLC.:bvrF21:bd01/10/2024:br5.31:svnGigabyteTechnologyCo.,Ltd.:pnB650MAORUSELITEAX:pvrDefaultstring:rvnGigabyteTechnologyCo.,Ltd.:rnB650MAORUSELITEAX:rvrx.x:cvnDefaultstring:ct3:cvrDefaultstring:skuDefaultstring:
dmi.product.family: B650 MB
dmi.product.name: B650M AORUS ELITE AX
dmi.product.sku: Default string
dmi.product.version: Default string
dmi.sys.vendor: Gigabyte Technology Co., Ltd.

[nickolas (nickolas-linux-kernel-bugs)]

This issue is still present on kernel 6.7.1 and firmware 20240115.
Opening a new bug for this as directed in this old bug: https://bugzilla.kernel.org/show_bug.cgi?id=215167

$ uname -a
Linux andromeda 6.7.1-arch1-1 #1 SMP PREEMPT_DYNAMIC Sun, 21 Jan 2024 22:14:10 +0000 x86_64 GNU/Linux

$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl -b | egrep -i bluetooth
egrep: warning: egrep is obsolescent; using grep -E
Jan 24 00:20:24 andromeda kernel: Bluetooth: Core ver 2.22
Jan 24 00:20:24 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI device and connection manager initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: HCI socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Jan 24 00:20:24 andromeda kernel: Bluetooth: SCO socket layer initialized
Jan 24 00:20:25 andromeda systemd[1]: Reached target Bluetooth Support.
Jan 24 00:20:25 andromeda NetworkManager[790]: <info> [1706077225.3441] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 24 00:20:27 andromeda kernel: Bluetooth: hci0: Reading Intel version command failed (-110)

Not sure what other logs or info you need, but just let me know if it would help.

[nickolas (nickolas-linux-kernel-bugs)]

This issue is still present in kernel 6.7.2

[dustin (dustin-linux-kernel-bugs)]

I'm also experiencing this issue. It started with kernel 6.5. Bluetooth has been broken ever since. The issue was not present in earlier versions of the kernel.

```
$ uname -a

Linux 6.5.0-17-generic #17~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Tue Jan 16 14:32:32 UTC 2 x86_64 x86_64 x86_64 GNU/Linux
```

```
$ lsusb | grep -i bluetooth

Bus 001 Device 004: ID 8087:0032 Intel Corp. AX210 Bluetooth
```

```
$ journalctl -b | egrep -i bluetooth

Jan 30 10:28:53 systemd[3247]: Reached target Bluetooth.
Jan 30 10:28:53 systemd[1]: Reached target Bluetooth Support.
Jan 30 10:28:55 kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Jan 30 10:28:55 kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
```

```
linux-firmware/jammy-proposed,now 20220329.git681281e4-0ubuntu3.25 all [installed,automatic]
```

[Removed by request (removed10315590)]

I can confirm this issue exists on both Ubuntu 22.04.3 and 24.04.beta (2024-01-25) with Linux 6.5x.

Both the Logitech (Bluetooth) M535 mouse and Microsoft Surface (Pro 7) Type Cover were problematic with Linux 6.5x to the point where they were unusable (timeouts or non-responsive for the mouse and boot-up or non-responsive Type Cover).

The only solution I found was to re-image with Ubuntu 22.04 (offline), place a hold on the installed Linux 6.2x, then connect to internet to complete the installation and updating process. The Linux hold prevents the updating to the 6.5x kernel.

If Linux 6.5x got installed (usually as a choice to have internet connected during the OS installation which followed with an update/upgrade), it had to be removed and replaced by Linux 6.2x to resolve the Bluetooth issues with the mouse and Type Cover.

Bluetooth failed to perform properly on Ubuntu 24.04 or 22.04 with Linux 6.5.0-14-generic.

Bluetooth performs properly under the following conditions:
Ubuntu 22.04.3, Linux 6.2.0-26-generic (hold), gnome-bluetooth 3.34.5-8, bluez 5.64

lsusb - Bus 003 includes three devices:
Device 004: ID 045e:09c0 Microsoft Corp. Surface Type Cover
Device 003: ID 8087:0026 Intel Corp. AX201 Bluetooth (Logitech M535 mouse)
Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

I don't have any additional specifics for the Linux 6.5x builds of Ubuntu 22.04 and 24.04 other than I was unable to get the Bluetooth mouse and Type Cover to work properly. I went through several builds of both Ubuntu versions and the only one that worked properly was the one I detailed above.

[nickolas (nickolas-linux-kernel-bugs)]

This issue is still present in kernel 6.7.3

[dustin (dustin-linux-kernel-bugs)]

I discovered that Bluetooth starts working again after a cold boot (shutdown, disconnect power for 30 seconds, then boot normally).

[nickolas (nickolas-linux-kernel-bugs)]

Bluetooth still does not work with 6.7.4, however the logs have changed from the error that was shown before:

$ journalctl -b | grep -E -i bluetooth
Feb 11 14:27:14 andromeda kernel: Bluetooth: Core ver 2.22
Feb 11 14:27:14 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Feb 11 14:27:14 andromeda kernel: Bluetooth: HCI device and connection manager initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: HCI socket layer initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: SCO socket layer initialized
Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 11 14:27:14 andromeda kernel: Bluetooth: hci0: Firmware Version: 255-255.255
Feb 11 14:27:15 andromeda systemd[1]: Reached target Bluetooth Support.
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Reading supported features failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Error reading debug features
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Feb 11 14:27:15 andromeda systemd[1]: Stopped target Bluetooth Support.
Feb 11 14:27:15 andromeda NetworkManager[781]: <info> [1707683235.5366] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Device revision is 1
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Secure boot is enabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: OTP lock is enabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: API lock is enabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Debug lock is disabled
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Feb 11 14:27:15 andromeda systemd[1]: Reached target Bluetooth Support.
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Feb 11 14:27:15 andromeda kernel: Bluetooth: hci0: Firmware Version: 255-255.255
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Waiting for firmware download to complete
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Firmware loaded in 1386206 usecs
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Waiting for device to boot
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Device booted in 14608 usecs
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Feb 11 14:27:17 andromeda kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
Feb ...

[vjstink (vjstink-linux-kernel-bugs)]

I have the same issue as Nickolas, turning off the computer does not help.

The device is also the same: Intel AX200 8087:0029. Mine is on a desktop motherboard.

$ uname -r
6.7.4-arch1-1

$ lsusb | grep -i bluetooth
Bus 001 Device 006: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl -b | grep -E -i bluetooth
----
Feb 15 09:06:07 home bluetoothd[948]: Bluetooth management interface 1.22 initialized
Feb 15 09:06:07 home systemd[1]: Started Bluetooth service.
Feb 15 09:06:07 home systemd[1]: Reached target Bluetooth Support.
Feb 15 09:06:07 home NetworkManager[1027]: <info> [1707980767.6232] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.44.2-3/libnm-device-plugin-bluetooth.so)
Feb 15 09:06:08 home kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
Feb 15 09:06:08 home kernel: Bluetooth: hci0: command 0xfc05 tx timeout

Same error was present on 6.7.3 and 6.7.2. I believe 6.6.9 was the last version where it worked fine.

[Removed by request (removed10315590)]

Ubuntu recently released an update, v22.04.4, which included an updated version of bluez v5.63. One of the bugs fixed by the update was "Fix issue with storing IRK causing invalid read access." My previous experience was wit Ubuntu v22.04.3 with a linux 6.5x kernel. The new build has Kernel: Linux 6.5.0-21-generic paired with the bluez update. Having no more bluetooth issues with this new build (Ubuntu minimal including snap) as I did with the 22.04.3 build perhaps it's possible these changes resolved the bluetooth issue of the BT mouse disconnecting without reason. Others may want to try this. If it turns out to be helpful, please post to this bug report and perhaps we can move on to additional updates like Ubuntu 24.04 scheduled for April.

https://discourse.ubuntu.com/t/jammy-jellyfish-release-notes/24668
https://git.kernel.org/pub/scm/bluetooth/bluez.git/tree/ChangeLog?id=5.63

[nickolas (nickolas-linux-kernel-bugs)]

Bluetooth is still not working on boot with kernel 6.7.9 with linux-firmware 20240220

$ lsusb | grep -i bluetooth
Bus 001 Device 008: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl -b | grep -E -i bluetooth
Mar 09 10:41:19 andromeda kernel: Bluetooth: Core ver 2.22
Mar 09 10:41:19 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Mar 09 10:41:19 andromeda kernel: Bluetooth: HCI device and connection manager initialized
Mar 09 10:41:19 andromeda kernel: Bluetooth: HCI socket layer initialized
Mar 09 10:41:19 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Mar 09 10:41:19 andromeda kernel: Bluetooth: SCO socket layer initialized
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Firmware Version: 255-255.255
Mar 09 10:41:20 andromeda systemd[1]: Reached target Bluetooth Support.
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: FW download error recovery failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Reading supported features failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Error reading debug features
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: sending frame failed (-19)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Failed to read MSFT supported features (-19)
Mar 09 10:41:20 andromeda systemd[1]: Stopped target Bluetooth Support.
Mar 09 10:41:20 andromeda NetworkManager[795]: <info> [1710002480.4767] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Device revision is 1
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Secure boot is enabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: OTP lock is enabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: API lock is enabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Debug lock is disabled
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
Mar 09 10:41:20 andromeda kernel: Bluetooth: hci0: Firmware Version: 255-255.255
Mar 09 10:41:20 andromeda systemd[1]: Reached target Bluetooth Support.
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Waiting for firmware download to complete
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Firmware loaded in 1393326 usecs
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Waiting for device to boot
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Device booted in 14610 usecs
Mar 09 10:41:22 andromeda kernel: Bluetooth: hci0: Malformed MSFT vendor event: 0x02
Mar 09 10:41:22 andromeda kernel: Blue...

[asimsalam (asimsalam)]

I can confirm that it is occurring on my Asus laptop as well with Intel AX200.

~$ uname -r
6.5.0-25-generic
~$ lsusb | grep -i bluetooth

Bus 003 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth
~$ journalctl -b | egrep -i bluetooth

Mar 09 11:37:22 neelum NetworkManager[988]: <info> [1710013042.6555] Loaded device plugin: NMBluezManager (/usr/lib/x86_64-linux-gnu/NetworkManager/1.36.6/libnm-device-plugin-bluetooth.so)
Mar 09 11:37:22 neelum kernel: Bluetooth: Core ver 2.22
Mar 09 11:37:22 neelum kernel: NET: Registered PF_BLUETOOTH protocol family
Mar 09 11:37:22 neelum kernel: Bluetooth: HCI device and connection manager initialized
Mar 09 11:37:22 neelum kernel: Bluetooth: HCI socket layer initialized
Mar 09 11:37:22 neelum kernel: Bluetooth: L2CAP socket layer initialized
Mar 09 11:37:22 neelum kernel: Bluetooth: SCO socket layer initialized
Mar 09 11:37:25 neelum systemd[1]: Starting Bluetooth service...
Mar 09 11:37:25 neelum bluetoothd[1403]: Bluetooth daemon 5.64
Mar 09 11:37:25 neelum systemd[1]: Started Bluetooth service.
Mar 09 11:37:25 neelum systemd[1]: Reached target Bluetooth Support.
Mar 09 11:37:25 neelum bluetoothd[1403]: Starting SDP server
Mar 09 11:37:25 neelum bluetoothd[1403]: Bluetooth management interface 1.22 initialized
Mar 09 11:37:25 neelum kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Mar 09 11:37:25 neelum kernel: Bluetooth: BNEP filters: protocol multicast
Mar 09 11:37:25 neelum kernel: Bluetooth: BNEP socket layer initialized
Mar 09 11:37:27 neelum kernel: Bluetooth: hci0: command 0xfc05 tx timeout
Mar 09 11:37:27 neelum kernel: Bluetooth: hci0: Reading Intel version command failed (-110)
~$

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[vjstink (vjstink-linux-kernel-bugs)]

(In reply to Nickolas Gupton from comment #7)
> Bluetooth is still not working on boot with kernel 6.7.9 with linux-firmware
> 20240220
> However, if I run this script (may take 2-3 runs sometimes) it will work:
>
> $ cat reset_bluetooth.sh
> modprobe -r btusb
> modprobe -r btintel
> sleep 2
> modprobe btintel
> modprobe btusb
> sleep 1
> systemctl restart bluetooth

Thanks for the script, it actually works after a couple of tries as you say, really great.

I wonder, how did you enable these extra debug messages in journalctl? For example, in mine it doesn't say anything about which firmware files it tries to load.
I was trying to identify what it loads to replace them with some older versions and see if I can make it work that way.

I also want to confirm again that the issue is still present in kernel 6.8.1 with the latest firmware update: 20240312

[contact (contact-linux-kernel-bugs)]

Had the same issue. Somehow, after a long power-off and turning on again, Bluetooth managed to show up and the message was gone. Using an AX200 as well.

Currently using kernel 6.8.2

[agurenko (agurenko-linux-kernel-bugs)]

(In reply to Olivier Delierre from comment #9)
> Had the same issue. Somehow, after a long power-off and turning on again,
> Bluetooth managed to show up and the message was gone. Using an AX200 as
> well.
>
> Currently using kernel 6.8.2

Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch for a few minutes and it worked on boot. This is very weird behavior.

[dustin (dustin-linux-kernel-bugs)]

(In reply to Gurenko Alex from comment #10)
> (In reply to Olivier Delierre from comment #9)
> > Had the same issue. Somehow, after a long power-off and turning on again,
> > Bluetooth managed to show up and the message was gone. Using an AX200 as
> > well.
> >
> > Currently using kernel 6.8.2
>
> Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch
> for a few minutes and it worked on boot. This is very weird behavior.

Sadly, its short lived. Mine stopped working again after the first resume from suspend that occurred after the cold boot.

[agurenko (agurenko-linux-kernel-bugs)]

(In reply to Dustin from comment #11)
> (In reply to Gurenko Alex from comment #10)
> > (In reply to Olivier Delierre from comment #9)
> > > Had the same issue. Somehow, after a long power-off and turning on again,
> > > Bluetooth managed to show up and the message was gone. Using an AX200 as
> > > well.
> > >
> > > Currently using kernel 6.8.2
> >
> > Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch
> > for a few minutes and it worked on boot. This is very weird behavior.
>
> Sadly, its short lived. Mine stopped working again after the first resume
> from suspend that occurred after the cold boot.

Yes, same here, after normal reboot or shutdown (assuming it happens, because it also hangs on shutdown/reboot now), it **only** works after PSU power cycle

[gabrielreisvelloso (gabrielreisvelloso-linux-kernel-bugs)]

(In reply to Gurenko Alex from comment #12)
> (In reply to Dustin from comment #11)
> > (In reply to Gurenko Alex from comment #10)
> > > (In reply to Olivier Delierre from comment #9)
> > > > Had the same issue. Somehow, after a long power-off and turning on
> again,
> > > > Bluetooth managed to show up and the message was gone. Using an AX200
> as
> > > > well.
> > > >
> > > > Currently using kernel 6.8.2
> > >
> > > Wow, indeed, after upgrade powered off my desktop, flipped the PSU switch
> > > for a few minutes and it worked on boot. This is very weird behavior.
> >
> > Sadly, its short lived. Mine stopped working again after the first resume
> > from suspend that occurred after the cold boot.
>
> Yes, same here, after normal reboot or shutdown (assuming it happens,
> because it also hangs on shutdown/reboot now), it **only** works after PSU
> power cycle

Can confirm here, did the test and only work with complete PSU power cycle. Turn of, waited few seconds and then power on again.

Have a Intel AX200 chip and Linux archlinux 6.8.2-arch2-1 #1 SMP PREEMPT_DYNAMIC Thu, 28 Mar 2024 17:06:35 +0000 x86_64 GNU/Linux

[jugoslav.gacas (jugoslav.gacas-linux-kernel-bugs)]

I can also confirm the issue. I tried using latest kernel 6.8.2.arch2-1 on arch linux, and also LTS version 6.6.23-1 and on both I see same behavior.

$ lsusb | grep -i bluetooth
Bus 001 Device 004: ID 8087:0029 Intel Corp. AX200 Bluetooth

The behavior is exactly the same as other described.

[thomas.creutz (thomas.creutz-linux-kernel-bugs)]

I also get:

~$ dmesg | grep -i blue
[ 13.838221] Bluetooth: Core ver 2.22
[ 13.838236] NET: Registered PF_BLUETOOTH protocol family
[ 13.838237] Bluetooth: HCI device and connection manager initialized
[ 13.838240] Bluetooth: HCI socket layer initialized
[ 13.838241] Bluetooth: L2CAP socket layer initialized
[ 13.838244] Bluetooth: SCO socket layer initialized
[ 14.329584] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 14.329588] Bluetooth: BNEP filters: protocol multicast
[ 14.329590] Bluetooth: BNEP socket layer initialized
[ 16.032582] Bluetooth: hci0: Reading Intel version command failed (-110)
[ 16.032583] Bluetooth: hci0: command 0xfc05 tx timeout

~$ modinfo btintel
filename: /lib/modules/6.5.0-26-generic/kernel/drivers/bluetooth/btintel.ko
firmware: intel/ibt-12-16.ddc
firmware: intel/ibt-12-16.sfi
firmware: intel/ibt-11-5.ddc
firmware: intel/ibt-11-5.sfi
license: GPL
version: 0.1
description: Bluetooth support for Intel devices ver 0.1
author: Marcel Holtmann <email address hidden>
srcversion: FDF2221B8ED4B01F8EADF85
depends: bluetooth
retpoline: Y
intree: Y
name: btintel
vermagic: 6.5.0-26-generic SMP preempt mod_unload modversions

~$ lsusb | grep -i bluetooth
Bus 001 Device 005: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter

[luiz.dentz (luiz.dentz-linux-kernel-bugs)]

Can you guys try with the following change:

https://patchwork.kernel<email address hidden>/

[robert (robert-linux-kernel-bugs)]

(In reply to Luiz Von Dentz from comment #16)
> Can you guys try with the following change:
>
> https://patchwork.kernel.org/project/bluetooth/patch/20240401193515.2525201-
> <email address hidden>/

I have the same issue and applied this patch to my kernel, but it seems to have broken the btintel module. I get a null pointer deref on boot and bluetooth is broken:

[ 2.317366] BUG: kernel NULL pointer dereference, address: 0000000000000070
[ 2.317699] #PF: supervisor read access in kernel mode
[ 2.317993] #PF: error_code(0x0000) - not-present page
[ 2.318280] PGD 0 P4D 0
[ 2.318283] Oops: 0000 [#1] PREEMPT SMP NOPTI
[ 2.318842] CPU: 3 PID: 185 Comm: kworker/u33:0 Not tainted 6.8.3-gentoo-dist #1
[ 2.318844] Hardware name: AZW SER/SER, BIOS SER7PRO_P5C8V30 09/15/2023
[ 2.318845] Workqueue: hci0 hci_alloc_dev_priv [bluetooth]
[ 2.319426] RIP: 0010:btintel_configure_setup+0x245/0x970 [btintel]
[ 2.320365] Code: 85 ff 75 a1 f0 41 80 8e 51 06 00 00 02 f0 41 80 8e 51 06 00 00 04 f0 41 80 8e 51 06 00 00 08 49 c7 86 38 17 00 00 b0 63 66 c1 <83> 7b 70 0a 75 7b 48 8b 83 d0 00 00 00 80 78 01 37 75 6e 0f 1f 44
[ 2.320691] RSP: 0018:ffffa215005cfd48 EFLAGS: 00010202
[ 2.321452] RAX: 0000000000000000 RBX: 0000000000000000 RCX: 0000000080200006
[ 2.321760] RDX: 0000000080200007 RSI: ffffd3238404d700 RDI: 0000000000000000
[ 2.322437] RBP: ffff91a940ccc6c8 R08: 0000000080200007 R09: 0000000080200006
[ 2.322438] R10: 0000000000000001 R11: 0000000000000000 R12: ffff91a940ccc6d0
[ 2.322439] R13: ffff91a947f50c00 R14: ffff91a940ccc000 R15: ffff91a940ccca88
[ 2.322441] FS: 0000000000000000(0000) GS:ffff91af820c0000(0000) knlGS:0000000000000000
[ 2.323737] CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
[ 2.323739] CR2: 0000000000000070 CR3: 000000010dfa2000 CR4: 0000000000f50ef0
[ 2.323740] PKRU: 55555554
[ 2.323740] Call Trace:
[ 2.323743] <TASK>
[ 2.326248] ? __die_body+0x68/0xb0
[ 2.326253] ? page_fault_oops+0x3a3/0x400
[ 2.326256] ? exc_page_fault+0x60/0xf0
[ 2.326265] ? asm_exc_page_fault+0x26/0x30
[ 2.326269] ? btintel_configure_setup+0x245/0x970 [btintel]
[ 2.328091] ? btintel_configure_setup+0x16c/0x970 [btintel]
[ 2.328093] ? __ia32_compat_sys_sysinfo+0x230/0x270
[ 2.329006] hci_dev_open_sync+0x166/0x1610 [bluetooth]
[ 2.329013] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329015] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329016] ? srso_alias_return_thunk+0x5/0xfbef5
[ 2.329018] hci_alloc_dev_priv+0x164e/0x1bc0 [bluetooth]
[ 2.329023] process_scheduled_works+0x24b/0x450
[ 2.329026] worker_thread+0x2c3/0x420
[ 2.329028] ? __pfx_worker_thread+0x10/0x10
[ 2.329030] kthread+0xe8/0x110
[ 2.329032] ? __pfx_kthread+0x10/0x10
[ 2.329033] ret_from_fork+0x37/0x50
[ 2.329036] ? __pfx_kthread+0x10/0x10
[ 2.329038] ret_from_fork_asm+0x1b/0x30
[ 2.329043] </TASK>
[ 2.329043] Modules linked in: amdxcp(+) ac97_bus(+) iwlwifi(+) snd_hda_codec(+) btusb snd_pcm_dmaengine gpu_sched vfat btbcm snd_pci_ps drm_suballoc_helper btintel i2c_algo_bit fat snd_rpl_pci_acp6x kvm(+) drm_ttm_helper snd_hda_core snd_acp_pci btrtl ttm s...

[jugoslav.gacas (jugoslav.gacas-linux-kernel-bugs)]

The issue has been fixed for me after upgrading to kernel 6.8.4-arch1-1 on Arch-linux.

[contact (contact-linux-kernel-bugs)]

(In reply to Jugoslav Gacas from comment #18)
> The issue has been fixed for me after upgrading to kernel 6.8.4-arch1-1 on
> Arch-linux.

Can confirm. Upgraded kernel to 6.8.4-arch1-1, removed btusb from the module loading blacklist, powered-off the PC and powering it on again, bluetooth was working.

Tried several things such as rebooting, rebooting on my Windows drive, rebooting to Archlinux again, powering-off: no power-off hanging, and bluetooth was working immediately after each start-up, without having to deal with modprobe anyhow.

[nickolas (nickolas-linux-kernel-bugs)]

I am on kernel 6.8.4 and using firmware 20242312, but Bluetooth is still not working for me:

$ uname -a
Linux andromeda 6.8.4-arch1-1 #1 SMP PREEMPT_DYNAMIC Fri, 05 Apr 2024 00:14:23 +0000 x86_64 GNU/Linux

$ journalctl -b | grep -E -i bluetooth
Apr 09 07:01:20 andromeda kernel: Bluetooth: Core ver 2.22
Apr 09 07:01:20 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
Apr 09 07:01:20 andromeda kernel: Bluetooth: HCI device and connection manager initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: HCI socket layer initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: L2CAP socket layer initialized
Apr 09 07:01:20 andromeda kernel: Bluetooth: SCO socket layer initialized
Apr 09 07:01:21 andromeda systemd[1]: Reached target Bluetooth Support.
Apr 09 07:01:21 andromeda NetworkManager[794]: <info> [1712664081.1498] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
Apr 09 07:01:23 andromeda kernel: Bluetooth: hci0: Reading Intel version command failed (-110)

[nickolas (nickolas-linux-kernel-bugs)]

Sorry, a typo in my last comment, firmware 20240312 is what I meant.

[Rex Tsai (chihchun)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:
apport-collect 2051720

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

[agurenko (agurenko-linux-kernel-bugs)]

(In reply to Nickolas Gupton from comment #21)
> Sorry, a typo in my last comment, firmware 20240312 is what I meant.

make sure you do full "power on - power off - power on" cycle **with fixed kernel**, it's known that warm boot or older kernel somewhere in this cycle prevent Bluetooth to recover.

[nickolas (nickolas-linux-kernel-bugs)]

Yeah, I turn my PC off every night. Have turned it on from a cold power off every morning for the last year or so this hasn't been working. That doesn't help at all, the only thing that works to get Bluetooth working after boot is running the script I showed in a previous comment.

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[Dustin Falgout (lots0logs)]

apport information

[wt (wt-linux-kernel-bugs)]

Does this have any relation to the message I am seeing in the journal logs after warm boot? Namely this:

Bluetooth: hci0: command 0xfc00 tx timeout

I can confirm that I still get this message on a mainline kernel build.

I have started a thread on linux-bluetooth with the subject "QCA6390 bluetooth doesn't work after warm boot or disable/reenable" if that helps.

[nickolas (nickolas-linux-kernel-bugs)]

kernel: 6.9.1
linux-firmware: 20240510

For me bluetooth still does not work on boot, the timeout error is no longer shown in the logs but without running that reset script the journal will just endlessly repeat these messages and the bluetooth will never work. I think the 'fix' that was put in for this simply hid the issue from the logs and wasn't actually resolved.

$ lsusb | grep -i bluetooth
Bus 001 Device 007: ID 8087:0029 Intel Corp. AX200 Bluetooth

$ journalctl --since 2024-05-22 | grep -E -i bluetooth
May 23 07:21:03 andromeda kernel: Bluetooth: Core ver 2.22
May 23 07:21:03 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
May 23 07:21:03 andromeda kernel: Bluetooth: HCI device and connection manager initialized
May 23 07:21:03 andromeda kernel: Bluetooth: HCI socket layer initialized
May 23 07:21:03 andromeda kernel: Bluetooth: L2CAP socket layer initialized
May 23 07:21:03 andromeda kernel: Bluetooth: SCO socket layer initialized
May 23 07:21:03 andromeda systemd[1]: Reached target Bluetooth Support.
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Firmware Version: 132-3.24
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: Firmware already loaded
May 23 07:21:03 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 23 07:21:03 andromeda NetworkManager[789]: <info> [1716466863.8963] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
May 23 07:24:04 andromeda kernel: Bluetooth: Core ver 2.22
May 23 07:24:04 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
May 23 07:24:04 andromeda kernel: Bluetooth: HCI device and connection manager initialized
May 23 07:24:04 andromeda kernel: Bluetooth: HCI socket layer initialized
May 23 07:24:04 andromeda kernel: Bluetooth: L2CAP socket layer initialized
May 23 07:24:04 andromeda kernel: Bluetooth: SCO socket layer initialized
May 23 07:24:04 andromeda systemd[1]: Reached target Bluetooth Support.
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Boot Address: 0x24800
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Firmware Version: 132-3.24
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: Firmware already loaded
May 23 07:24:04 andromeda kernel: Bluetooth: hci0: HCI LE Coded PHY feature bit is set, but its usage is not supported.
May 23 07:24:05 andromeda NetworkManager[779]: <info> [1716467045.0155] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.46.0-2/libnm-device-plugin-bluetooth.so)
May 23 07:28:33 andromeda kernel: Bluetooth: Core ver 2.22
May 23 07:28:33 andromeda kernel: NET: Registered PF_BLUETOOTH protocol family
May 23 07:28:33 andromeda kernel: Bluetooth: HCI device and connection manager initialized
May 23 07:28:33 andromeda kernel: Bluetooth: HCI socket layer initialized
May 23 07:28:33 andromeda kernel: Bluetooth: L2CAP socket layer initialized
May 23 07:28:33 ...

[pmenzel+bugzilla.kernel.org (pmenzel+bugzilla.kernel.org-linux-kernel-bugs)]

@nickolas, from your bug description it’s unclear, if this is a regression, or if Bluetooth never worked for you. Could you please clarify?

Please attach the output of `dmesg`.

Also, please run `bluetoothctl` and share all the output.

[dustin (dustin-linux-kernel-bugs)]

This is a regression. It has been broken since 6.5. It worked fine in prior kernel versions.

dmesg:
```
[88870.532674] iwlwifi 0000:0f:00.0: WRT: Invalid buffer destination
[88870.672880] iwlwifi 0000:0f:00.0: WFPM_UMAC_PD_NOTIFICATION: 0x20
[88870.672897] iwlwifi 0000:0f:00.0: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[88870.672910] iwlwifi 0000:0f:00.0: WFPM_AUTH_KEY_0: 0x90
[88870.672921] iwlwifi 0000:0f:00.0: CNVI_SCU_SEQ_DATA_DW9: 0x0
[88870.698472] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[88870.698512] Bluetooth: hci0: Bad flag given (0x1) vs supported (0x0)
[88871.304617] audit: type=1400 audit(1716388650.420:36): apparmor="DENIED" operation="capable" class="cap" profile="/usr/sbin/cupsd" pid=130211 comm="cupsd" capability=12 capname="net_admin"
[88871.626870] usb 3-1.1: new full-speed USB device number 9 using xhci_hcd
[88871.805974] usb 3-1.1: New USB device found, idVendor=18d1, idProduct=9470, bcdDevice= 0.01
[88871.805977] usb 3-1.1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[88871.805979] usb 3-1.1: Product: Titan Security Key v2
[88871.805980] usb 3-1.1: Manufacturer: Google
[88871.805981] usb 3-1.1: SerialNumber: 2
[88871.895114] hid-generic 0003:18D1:9470.000C: hiddev3,hidraw5: USB HID v1.11 Device [Google Titan Security Key v2] on usb-0000:13:00.3-1.1/input0
[88873.707802] wlp15s0: authenticate with 68:7f:f0:00:75:00
[88873.711729] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[88873.758100] wlp15s0: authenticate with 68:7f:f0:00:75:00
[88873.758108] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[88873.759975] wlp15s0: authenticated
[88873.762841] wlp15s0: associate with 68:7f:f0:00:75:00 (try 1/3)
[88873.767689] wlp15s0: RX AssocResp from 68:7f:f0:00:75:00 (capab=0x1011 status=0 aid=29)
[88873.772354] wlp15s0: associated
[88873.839960] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by 68:7f:f0:00:75:00
[90310.593408] Bluetooth: hci0: Hardware error 0x0c
[90310.622241] Bluetooth: hci0: Retrieving Intel exception info failed (-16)
[90810.448474] wlp15s0: disconnect from AP 68:7f:f0:00:75:00 for new auth to 68:7f:f0:00:74:ff
[90810.556380] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[90810.559334] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[90810.604710] wlp15s0: authenticate with 68:7f:f0:00:74:ff
[90810.604716] wlp15s0: send auth to 68:7f:f0:00:74:ff (try 1/3)
[90810.606524] wlp15s0: authenticated
[90810.607829] wlp15s0: associate with 68:7f:f0:00:74:ff (try 1/3)
[90810.612780] wlp15s0: RX ReassocResp from 68:7f:f0:00:74:ff (capab=0x1011 status=0 aid=31)
[90810.618033] wlp15s0: associated
[90810.799009] wlp15s0: Limiting TX power to 40 (40 - 0) dBm as advertised by 68:7f:f0:00:74:ff
[91268.883979] wlp15s0: disconnect from AP 68:7f:f0:00:74:ff for new auth to 68:7f:f0:00:75:00
[91268.957741] wlp15s0: authenticate with 68:7f:f0:00:75:00
[91268.960512] wlp15s0: send auth to 68:7f:f0:00:75:00 (try 1/3)
[91269.000877] wlp15s0: authenticated
[91269.003228] wlp15s0: associate with 68:7f:f0:00:75:00 (try 1/3)
[91269.017600] wlp15s0: RX ReassocResp from 68:7f:f0:00:75:00 (capab=0x1011 status=0 aid=20)
[91269.022231] wlp15s0: associated
[91269.028341] wlp15s0: Limiting TX power to 4...

[pmenzel+bugzilla.kernel.org (pmenzel+bugzilla.kernel.org-linux-kernel-bugs)]

@dustin, thank you, but please *attach* the full log next time.

    [90310.622241] Bluetooth: hci0: Retrieving Intel exception info failed (-16)

is different from this issue title. Please create a new issue, and attach all the information there.

> This is a regression. It has been broken since 6.5. It worked fine in prior
> kernel versions.

That is actually a good thing. It’d be great if you bisected the commit introducing the regression [1].

[1]: https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and-bisect-regressions.html

[dustin (dustin-linux-kernel-bugs)]

That error is new. I've actually never seen it before now. The error I was getting ever since I updated to 6.5+ was exactly the same as the error in this bug's description. I see it's still in the logs I posted today in addition to that new error.

[dustin (dustin-linux-kernel-bugs)]

Btw, I opened an issue with Ubuntu before I found this issue. You can find the debug info I posted including logs there: https://bugs.launchpad.net/linux/+bug/2051720

[dustin (dustin-linux-kernel-bugs)]

It looks like that new error is from when I attempted to use my BT headphones for a meeting the other day after doing a cold boot. It's unrelated. Sorry about that. You can see at the end of the logs I posted where bluetooth stopped working after waking from suspend and the error is the exact error from this bug's description.

[nickolas (nickolas-linux-kernel-bugs)]

Created attachment 306340
dmesg log

(In reply to Paul Menzel from comment #26)
> @nickolas, from your bug description it’s unclear, if this is a regression,
> or if Bluetooth never worked for you. Could you please clarify?
>
> Please attach the output of `dmesg`.
>
> Also, please run `bluetoothctl` and share all the output.

The issue is still presenting the same as originally reported, bluetooth does not work on boot and requires the reset script I provided before it will start working. The only difference between then and now is that one log is missing.

Here are the extra logs you've asked for, the dmesg log was quite long so I attached it as a file:

# dmesg
(see attached file)

(before running the reset script)
$ bluetoothctl
Waiting to connect to bluetoothd...

(after running the reset script)
$ bluetoothctl
Waiting to connect to bluetoothd...[bluetooth]# Agent registered
[bluetooth]# hci0 new_settings: powered bondable ssp br/edr le secure-conn wide-band-speech
[bluetooth]# [CHG] Controller A4:B1:C1:D5:F5:24 Pairable: yes
[bluetooth]# AdvertisementMonitor path registered
[bluetooth]#

(In reply to Dustin from comment #27)
> This is a regression. It has been broken since 6.5. It worked fine in prior
> kernel versions.

I believe your issue is different than this one, this issue has been reported starting in 5.16 on the original bug linked that they closed and asked for someone to make a new issue if it was still present.

[pmenzel+bugzilla.kernel.org (pmenzel+bugzilla.kernel.org-linux-kernel-bugs)]

(In reply to Nickolas Gupton from comment #32)

> this issue has been reported starting in 5.16 on the original bug linked that
> they closed and asked for someone to make a new issue if it was still
> present.

Bug 215167 [1] reports a regression in Linux 5.14, and the referenced openSUSE report says at the end it should be fixed in 5.16.1.

Nickolas, thank you for attaching the full Linux logs. As the error from the bug title is not present in the log, I recommend to close this issue, and create a new one for your problem with a descriptive title like *Bluetooth only starts working after reloading btusb and btintel*, attaching all the files there. If you could bisect [3] the commit, that would even get you there faster. The Bluetooth device can even be passed to a virtual machine, and if the problem is reproducible there, bisection is quite fast [4][5].

I am sorry about this, but unfortunately, the comments by others on probably different issues, make it very hard and time consuming to understanding the actual issue. It looks like the maintainers are overworked and the subsystem has not enough resources. Still if you buy a device with Intel hardware (and even better a device with official GNU/Linux support), it’s valid to expect that Intel hardware works also on GNU/Linux.

[1]: https://bugzilla.kernel.org/show_bug.cgi?id=215167
[2]: https://bugzilla.opensuse.org/show_bug.cgi?id=1193124
[3]: https://www.kernel.org/doc/html/latest/admin-guide/verify-bugs-and-bisect-regressions.html
[4]: https://lore<email address hidden>/
[5]: https://<email address hidden>/

[priit (priit-linux-kernel-bugs)]

still present in kernel 6.9.3

dmesg | grep -i bluetooth
[ 4.466394] Bluetooth: Core ver 2.22
[ 4.466410] NET: Registered PF_BLUETOOTH protocol family
[ 4.466411] Bluetooth: HCI device and connection manager initialized
[ 4.466417] Bluetooth: HCI socket layer initialized
[ 4.466419] Bluetooth: L2CAP socket layer initialized
[ 4.466422] Bluetooth: SCO socket layer initialized
[ 5.405005] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.405007] Bluetooth: BNEP filters: protocol multicast
[ 5.405010] Bluetooth: BNEP socket layer initialized
[ 6.696883] Bluetooth: hci0: command 0xfc05 tx timeout
[ 6.696966] Bluetooth: hci0: Reading Intel version command failed (-110)

what's even more troublesome is that previously I was able to make it work with (sometimes with couple of tries):
sudo rmmod btusb && sudo modprobe btusb

now with this kernel I get only this over and over:
[ 74.101494] usbcore: deregistering interface driver btusb
[ 74.279683] usbcore: registered new interface driver btusb
[ 76.457250] Bluetooth: hci0: command 0xfc05 tx timeout
[ 76.457268] Bluetooth: hci0: Reading Intel version command failed (-110)

[priit (priit-linux-kernel-bugs)]

And yes, it is regression. also it does not work with kernel 6.6 (LTS).
However it does work perfectly well with kernel 6.1.92.

Linux Zen 6.1.92-1-MANJARO #1 SMP PREEMPT_DYNAMIC Mon May 27 03:37:00 UTC 2024 x86_64 GNU/Linux

$ dmesg | grep -i bluetooth
[ 5.621856] Bluetooth: Core ver 2.22
[ 5.621877] NET: Registered PF_BLUETOOTH protocol family
[ 5.621878] Bluetooth: HCI device and connection manager initialized
[ 5.621881] Bluetooth: HCI socket layer initialized
[ 5.621883] Bluetooth: L2CAP socket layer initialized
[ 5.621887] Bluetooth: SCO socket layer initialized
[ 5.659250] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 5.661255] Bluetooth: hci0: Device revision is 1
[ 5.661259] Bluetooth: hci0: Secure boot is enabled
[ 5.661260] Bluetooth: hci0: OTP lock is enabled
[ 5.661262] Bluetooth: hci0: API lock is enabled
[ 5.661263] Bluetooth: hci0: Debug lock is disabled
[ 5.661264] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 5.663789] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 5.663805] Bluetooth: hci0: Boot Address: 0x24800
[ 5.663807] Bluetooth: hci0: Firmware Version: 132-3.24
[ 6.464952] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 6.464954] Bluetooth: BNEP filters: protocol multicast
[ 6.464957] Bluetooth: BNEP socket layer initialized
[ 7.025995] Bluetooth: hci0: Waiting for firmware download to complete
[ 7.026211] Bluetooth: hci0: Firmware loaded in 1330487 usecs
[ 7.026245] Bluetooth: hci0: Waiting for device to boot
[ 7.041215] Bluetooth: hci0: Device booted in 14630 usecs
[ 7.041217] Bluetooth: hci0: Malformed MSFT vendor event: 0x02
[ 7.041527] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[ 7.047218] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 7.050221] Bluetooth: hci0: Firmware revision 0.3 build 132 week 3 2024
[ 7.217324] Bluetooth: MGMT ver 1.22
[ 18.841731] Bluetooth: RFCOMM TTY layer initialized
[ 18.841737] Bluetooth: RFCOMM socket layer initialized
[ 18.841740] Bluetooth: RFCOMM ver 1.11

sorry, but I have no time or will to install and test with every non-supported kernel versions inbetween 6.1 and 6.6 to see where the error came back in.

[luiz.dentz (luiz.dentz-linux-kernel-bugs)]

What now, CCP (aka AX201), is what I have in my laptop for ages and I never had a single problem with it:

Linux 6.8.10-300.fc40.x86_64 #1 SMP PREEMPT_DYNAMIC Fri May 17 21:20:54 UTC 2024 x86_64 GNU/Linux

[ 5.935014] Bluetooth: hci1: Found device firmware: intel/ibt-20-1-3.sfi
[ 5.935118] Bluetooth: hci1: Boot Address: 0x24800
[ 5.935120] Bluetooth: hci1: Firmware Version: 132-3.24

Having 0xfc05 to timeout normally means the controller is not responding since it is the very first command the btintel.c will send, most likely that is because there is something at preventing any communication to work or something, so Id be really surprised this is a regression at btusb/btintel otherwise we would be consistently seeing this in our systems as well.