Bluetooth broken on 18.04 with linux-hwe 5.0

[dobey]

After rebooting with the new 5.0 HWE kernel on 18.04, bluetooth no longer works properly. Switching to VT1 results in a stream of BLE failure messages while my Logitech MX Ergo or MX Master 2S try to connect.

I have also tried installing a backported build of bluez 5.50 from 19.04 to no avail, as the failure continues in the same manner. Rebooting and manually selecting the 4.18 kernel gives me working bluetooth again.

[Kai-Heng Feng (kaihengfeng)]

Please run `apport-collect 1840264`.

[dobey (dobey)]

OK. I've rebooted into the 5.0.0-25-generic kernel, and ran apport-collect, but it simply pops a dialog with "No additional information collected."

[dobey (dobey)]

The VT dmesg spew when booted to 5.0 gives the following:

"Bluetooth: hci0: request failed to create LE connection: status 0x0c"

The console is filled with these messages until the device stops trying to reconnect.

[dobey (dobey)]

OK. I've tried on my XPS 13 laptop and it works fine there, with Intel 7260 adapter. My PC where this is failing, has a Killer 1550 (Intel 9260) adapter. So this seems likely an issue with the driver in the 5.0.0-25 kernel on Intel 9260.

[Mohd Zain (mhdzain98)]

In System reports it says in crash reports as /usr/bin/bt-adapter
and in system logs it says Process 25037 (bt-adapter) of user 1000 dumped core.
This started happening as soon as i have done linux firmware driver update

[Reshad Dernjani (reshadd94)]

Bluetooth keeps disconnecting.
I am on 20.04 with kernel 5.6.3.

Pairing is very unstable if I want to pair my mx keys keyboard it works only when I disconnect all bluetooth devices including my mx master 3 and than pair the desired device only. After that enabling my devices keyboard and mouse works but as said the keyboard disconnects and sometimes replicates a key stroke multiple times.

Also bluetooth headset does not work. It connects (same as above) but plays only weird cracking sound.

dmesg | grep Blue
[ 3.146254] Bluetooth: Core ver 2.22
[ 3.146265] Bluetooth: HCI device and connection manager initialized
[ 3.146268] Bluetooth: HCI socket layer initialized
[ 3.146269] Bluetooth: L2CAP socket layer initialized
[ 3.146271] Bluetooth: SCO socket layer initialized
[ 3.151323] Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017
[ 3.152333] Bluetooth: hci0: Device revision is 1
[ 3.152334] Bluetooth: hci0: Secure boot is enabled
[ 3.152334] Bluetooth: hci0: OTP lock is enabled
[ 3.152335] Bluetooth: hci0: API lock is enabled
[ 3.152335] Bluetooth: hci0: Debug lock is disabled
[ 3.152336] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 3.153088] Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi
[ 4.649137] Bluetooth: hci0: Waiting for firmware download to complete
[ 4.649303] Bluetooth: hci0: Firmware loaded in 1463906 usecs
[ 4.649330] Bluetooth: hci0: Waiting for device to boot
[ 4.663324] Bluetooth: hci0: Device booted in 13671 usecs
[ 4.666107] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc
[ 4.666330] Bluetooth: hci0: Failed to send Intel_Write_DDC (-22)
[ 4.668309] Bluetooth: hci0: Firmware revision 0.0 build 128 week 11 2020
[ 5.357694] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 5.357695] Bluetooth: BNEP filters: protocol multicast
[ 5.357698] Bluetooth: BNEP socket layer initialized
[ 25.972964] Bluetooth: RFCOMM TTY layer initialized
[ 25.972969] Bluetooth: RFCOMM socket layer initialized
[ 25.972972] Bluetooth: RFCOMM ver 1.11
[ 4639.734854] Bluetooth: hci0: command 0x0402 tx timeout
[ 4641.750537] Bluetooth: hci0: command 0x2042 tx timeout

Should I open another bug report for this?
Any additional info needed?

[Launchpad Janitor (janitor)]

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