Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices

[Luiz Augusto von Dentz <luiz.dentz@gmail.com>]

Hi Chris,

On Mon, Feb 21, 2022 at 5:22 AM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Sorry folks, clicked Send instead of Save Draft in my earlier message.
>
> Anyway...
>
> On 18/02/2022 03:49, Chris Murphy wrote:
> > On Thu, Feb 17, 2022 at 5:15 PM Luiz Augusto von Dentz
> > <luiz.dentz@gmail.com> wrote:
> >>
> >> Hi Chris,
> >>
> >> On Thu, Feb 17, 2022 at 3:36 PM Chris Murphy <lists@colorremedies.com> wrote:
> >>>
> >>> OK I started over, and for now keeping the reporting constrained to
> >>> the hardware I personally have on hand.
> >>>
> >>> Hardware:
> >>> Lenovo Thinkpad X1 Carbon Gen 7
> >>> Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560
> >>> Jefferson Peak (JfP)
> >>> Sony 1000XM3 headset
> >>> bluez-5.63-3.fc36.x86_64
> >>>
> >>> kernel 5.17.0-rc4
> >>> * remove the paired headset with bluetoothctl
> >>> * reset the headset so it's not longer paired either
> >>> * put the headset in pairing mode
> >>> * GNOME Settings Bluetooth panel sees -> LE_WH-1000XM3, Not Setup
> >>> * click on Not Setup and nothing happens
> >>
> >> Well from the logs it doesn't seem the GNOME Setting is trying to do
> >> anything, have you tried bluetoothctl> connect <address>
> >
> > `bluetoothctl scan on`  does see the device
> > $ bluetoothctl pair 38:18:4C:24:2D:1D
> > Device 38:18:4C:24:2D:1D not available
> > $ bluetoothctl connect 38:18:4C:24:2D:1D
> > Device 38:18:4C:24:2D:1D not available
> >
> > $ journalctl -b -o short-monotonic --no-hostname | grep -i blue
> > https://drive.google.com/file/d/1x9EDvDx6XUowyRy2056n6uW-4PLx5KRb/view?usp=sharing
> >
> >
>
> I too am experiencing the problem that already-paired devices fail to connect to my laptop when running a 5.17 kernel.
>
> Extract from dmesg shows:
> [    3.825684] Bluetooth: hci0: Waiting for firmware download to complete
> [    3.825910] Bluetooth: hci0: Firmware loaded in 1551910 usecs
> [    3.825910] Bluetooth: hci0: unexpected event 0xff length: 5 > 0
> [    3.825936] Bluetooth: hci0: Waiting for device to boot
> [    3.839948] Bluetooth: hci0: unexpected event 0xff length: 7 > 0
> [    3.839973] Bluetooth: hci0: Device booted in 13715 usecs
> [    3.840205] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-19-0-4.ddc
> [    3.843002] Bluetooth: hci0: Applying Intel DDC parameters completed
> [    3.843926] Bluetooth: hci0: Firmware revision 0.4 build 125 week 46 2021
>
> Extract from lshw shows:
>                    description: Bluetooth wireless interface
>                    product: AX201 Bluetooth
>                    vendor: Intel Corp.
>                    physical id: e
>                    bus info: usb@1:e
>                    version: 0.02
>                    capabilities: bluetooth usb-2.01
>                    configuration: driver=btusb maxpower=100mA speed=12Mbit/s
>
> I don't know whether this will help, but I've found that the problem only occurs when boot from cold (i.e power on the
> laptop. If I then do a warm reboot, my bluetooh devices connect successfully. The significant difference may be that on
> a cold start, the firmware needs to loaded whereas on a warm reboot I see:
>
> [    2.000989] Bluetooth: hci0: Firmware already loaded
>
> Hope this helps. I am happy to test any fixes or provide additional diagnostics, but I'm not subscribed so please cc me.

What exactly doesn't work? Can't you power up the controller, etc?

-- 
Luiz Augusto von Dentz