#878181 bluetooth: Bluetooth with different devices stopped working recently on buster/sid

Package:
bluetooth
Source:
bluez
Submitter:
Torsten
Date:
2017-11-17 01:39:03 UTC
Severity:
important
#878181#5
Date:
2017-10-10 19:58:53 UTC
From:
To:
Recently my bluetooth Microsoft Bluetooth Keyboard stopped working
sometimes. Also other devices wherer hard to pair.

I purged all blue* packages, deleted /var/lib/systemd/rfkill/* and
reinstalled all.

I paired different devices with blueman and bluetoothctl. It worked only
in about 10% of the cases. And most devices got problems after about 1-3
minutes.
#878181#10
Date:
2017-10-11 05:41:20 UTC
From:
To:
I deleted the contents of /var/lib/bluetooth/* not the rfkill files
before reinstalling the packages and reinstalling. But I checked that
all rfkill switches where set to 0.
#878181#15
Date:
2017-10-23 08:53:00 UTC
From:
To:
Dear Maintainer,

after some updates last weeki(not sure which one) bluetooth is suddenly unstable.
Doens't matter if I use my headset or mouse or both, bt suddenly stops working. Often after a short period of time.

btmon output:
      Intel Bootup (0x02)
        Zero: 0x00
        Number of packets: 2
        Source: Operational firmware (0x01)
        Reset type: Soft software reset (0x02)
        Reset reason: System exception (0x05)
        DDC status: Persistent RAM (0x02)
      Intel System Exception (0x29)
        invalid packet size
        01 00 00 00 00 00 00 00 02 47 01 01 d8 32 01 50  .........G...2.P
        b0 b5 0b 00 00 47 01 01 06 00 00 00 00 00 00 00  .....G..........
        00 00 00 00 00 00 00 00 ff 93 10 5b f4 8c 2a 36  ...........[..*6
        bb f0 75 00 5c 23 01 50 00 40 00 00 00 00 00 00  ..u.\#.P.@......
        00 00 00 00 04 00 00 00 02 00 00 00 05 00 00 00  ................
        f8 ff 00 00 fc ff 00 00 f9 ff 00 00 14 00 00 50  ...............P
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
        00 00 00 00 00 00 00 00 00 00 00 00 74 18 00 50  ............t..P
        f8 ff 00 00 a0 ad 0b 00 74 13 00 50 10 a0 05 00  ........t..P....
        a4 fd 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
        00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  ................
        ef ef ef ef ef ef ef ef ef ef ef ef              ............

hcidump output:
    L2CAP(d): cid 0x0041 len 7 [psm 19]
      HIDP: Data: Input report
    L2CAP(d): cid 0x0041 len 7 [psm 19]
      HIDP: Data: Input report
    L2CAP(d): cid 0x0041 len 7 [psm 19]
      HIDP: Data: Input report

A quick fix is stopping the bluetooth service and shutdown the hci0 interface, start it again and afterwards start the bluetooth daemon again.
This "fixes" the problem for 0 to 120 seconds.
As this happens with multiple bluetooth devices, which work fine on other computers, I'm pretty sure something broke in bluez.

Best
Sebastian
#878181#20
Date:
2017-11-10 07:42:39 UTC
From:
To:
Hi,

I have the same error logs as Sebastian. But for me it wasn't a bluez
bug, see:
https://bugs.archlinux.org/task/56277#comment163301
And upstream bug reports:
https://bugzilla.kernel.org/show_bug.cgi?id=197147
https://bugzilla.kernel.org/show_bug.cgi?id=197807

Workaround for now:
bt_coex_active = 0

Best regards
Wuff
#878181#25
Date:
2017-11-17 01:34:38 UTC
From:
To:
Thanks to Wuff the following seems to be a workaround for me too:

$ cat /etc/modprobe.d/iwlwifi.conf
options iwlwifi bt_coex_active=0 swcrypto=1 11n_disable=8


Waiting for the new firmware.....