Bluetooth KO with kernel 5.16

Hi there,
I already had issues with my MX Master 3 but since today’s update and arrival of 5.16 I don’t see it anymore in bluetooth mode.

I have this error :slight_smile:

~]$ sudo systemctl status bluetooth
● bluetooth.service - Bluetooth service
     Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled; vendor preset: disabled)
     Active: active (running) since Mon 2022-01-24 10:38:50 CET; 34min ago
       Docs: man:bluetoothd(8)
   Main PID: 843 (bluetoothd)
     Status: "Running"
      Tasks: 1 (limit: 18379)
     Memory: 2.8M
        CPU: 86ms
     CGroup: /system.slice/bluetooth.service
             └─843 /usr/lib/bluetooth/bluetoothd

janv. 24 10:39:33 ordi1 bluetoothd[843]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
janv. 24 10:39:34 ordi1 bluetoothd[843]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
janv. 24 10:39:38 ordi1 bluetoothd[843]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
janv. 24 10:39:40 ordi1 bluetoothd[843]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
janv. 24 10:48:03 ordi1 bluetoothd[843]: Failed to set mode: Failed (0x03)
janv. 24 10:48:05 ordi1 bluetoothd[843]: Failed to set mode: Failed (0x03)
janv. 24 10:48:07 ordi1 bluetoothd[843]: Failed to set mode: Failed (0x03)
janv. 24 10:48:14 ordi1 bluetoothd[843]: Failed to set mode: Failed (0x03)
janv. 24 10:52:00 ordi1 bluetoothd[843]: Failed to set mode: Failed (0x03)
janv. 24 11:11:52 ordi1 bluetoothd[843]: Failed to set mode: Failed (0x03)

Could it be linked to those ?

PS : I want to use 5.16 as it takes in charge my HP Victus, wheras I had to use turnarounds like this :

Any idea of what to do apart wait & see ?

you can go to 5.15 kernel or 5.10 kernel that are LTS

Nope ! As said, with those, I have to add rtl89-dkms-git.
In addition, 5.16 has a better support of my Ryzen.

As I see no similar threads apart the ones I mentionned, I wonder if I’m part of a small minority with this Bluetooth issue.

Bumping up this tread.

I’ve also got bluetooth issues. Though I had before my recent updates some glitches with it. I’ve got similar error messages the reporter in the github issue link, though I use the recommended LTS kernel (5.15.19.-1). The problem is not kernel specific.

Last update didn’t change anything : I don’t see my MX Master 3 as bluetooth device anymore.

I have had the same issue on 5.16. on every other boot Bluetooth was just not there, even though the service was running. Some people already have suggested to roll back to 5.15, I have to say this also worked for me. But with the latest stable update I have tried the experimental 5.17 Kernel which also seem to fix this bluetooth problem, might even be a better solution since you won’t miss out on features.

This happens to me too :frowning: with the latest kernel (5.16.7.arch1-1) and the lts 5.15.21-1-lts.

feb 08 11:32:35 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:36 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:36 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:37 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:37 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:37 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:37 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:32:37 arie bluetoothd[750]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
feb 08 11:34:08 arie bluetoothd[750]: /org/bluez/hci0/dev_F8_4E_17_80_51_2E/sep3/fd2: fd(43) ready
feb 08 14:06:33 arie bluetoothd[750]: src/profile.c:ext_io_disconnected() Unable to get io data for Hands-Free Voice gateway: getpeername: Transport endpoint is not connected (107)

I know in one of the earlier 5.15 kernels I had an issue with bluetooth (I think it might not have even started)… and the solution revealed itself after I looked for any pacnew files that might have come along with recent stable updates… which was the case for me, so wasn’t a kernel issue.

There are lots of various commands to check for pacnew files, but I’ve settled on a simpler one that looks into the pacman.log$ grep pacnew /var/log/pacman.log and just look at entries around the date you updated as well as other “recent” dates) related to bluetooth/bluez. If you have a bluetooth related pacnew file and weren’t aware it existed, you likely probably hadn’t merged the changes that may be stopping your bluetooth from working.

This may not reveal a solution to your issues, but a good step to confirm all config changes took place when packages were updated.

What is your bluetooth&network hardware?
inxi --bluetooth --network -a

I am using Linux Kernel 5.16 and did not test bluetooth.
But I got a lot of spam errors in log on my new laptop when searching bluetooth devices after waking up suspend.

❯ journalctl --no-pager -p 3 -b
...
Feb 20 15:10:12 p15v kernel: Bluetooth: hci0: Timed out waiting for suspend events
Feb 20 15:10:12 p15v kernel: Bluetooth: hci0: Suspend timeout bit: 9
Feb 20 15:10:12 p15v kernel: Bluetooth: hci0: Suspend notifier action (3) failed: -110
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:01 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:02 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:02 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:02 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:02 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:02 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
Feb 20 15:12:02 p15v bluetoothd[824]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
....

Bluetooth hardware info:

❯ inxi --bluetooth -a
Bluetooth:
  Device-1: Intel AX201 Bluetooth type: USB driver: btusb v: 0.8
    bus-ID: 3-14:5 chip-ID: 8087:0026 class-ID: e001
  Report: rfkill ID: hci0 rfk-id: 1 state: up address: see --recommends
~]$  inxi --bluetooth --network -a
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    vendor: Hewlett-Packard driver: r8169 v: kernel port: f000 bus-ID: 04:00.0
    chip-ID: 10ec:8168 class-ID: 0200
  Device-2: Realtek RTL8852AE 802.11ax PCIe Wireless Network Adapter
    vendor: Hewlett-Packard driver: rtw89_pci v: kernel port: e000
    bus-ID: 05:00.0 chip-ID: 10ec:8852 class-ID: 0280
Bluetooth:
  Device-1: Realtek Bluetooth Radio type: USB driver: btusb v: 0.8
    bus-ID: 1-4:3 chip-ID: 0bda:2852 class-ID: e001 serial: 00e04c000001
  Report: bt-adapter ID: hci0 rfk-id: 1 state: up

Hi,

At least a good thing, I can see I am not alone with my issue.

I am on a fresh new install of Manjaro with kernel 5.15.25-1 and I must pair my keyboard each time I start a new session. The bluetooth service seems to start with a failure, but is OK when stop it, it starts with no error. Anyway, my keyboard is seen by bluetoothctl and is registered as paired, but does not work.

And after I pair it again, I have lots of lines saying src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed
I am writing on my bluetooth keyboard now, even with these errors from the service. So what?

1 Like