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

[Chris Murphy <lists@colorremedies.com>]

On Wed, Feb 16, 2022 at 4:49 PM Luiz Augusto von Dentz
<luiz.dentz@gmail.com> wrote:
>
> Hi Chris,
>
> On Tue, Feb 15, 2022 at 10:40 PM Chris Murphy <lists@colorremedies.com> wrote:
> >
> > On Tue, Feb 15, 2022 at 8:38 AM Chris Murphy <lists@colorremedies.com> wrote:
> > >
> > > On Tue, Feb 15, 2022 at 8:29 AM Chris Murphy <lists@colorremedies.com> wrote:
> > > >
> > > > On Thu, Feb 10, 2022 at 6:44 PM Chris Murphy <lists@colorremedies.com> wrote:
> > > >
> > > > > Case 2:
> > > > >
> > > > > Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560
> > > > > Jefferson Peak (JfP)
> > > >
> > > > Comparing 5.16.9 (working) and 5.17.0-rc7 (non-working) on this
> > > > Thinkpad X1 Carbon, I'm seeing two notable differences:
> > > >
> > > > Multiple messages like this:
> > > > [   15.731405] kernel: Bluetooth: hci0: unexpected event 0xff length: 5 > 0
> >
> >
> > btmon is here:
> > https://bugzilla.redhat.com/attachment.cgi?id=1860485
>
> LE or Classic? Perhaps this is related to:

I don't understand the question, how can I find out? All I know is
it's a Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)


> https://patchwork.kernel.org/project/bluetooth/patch/20220216221822.2694867-1-luiz.dentz@gmail.com/
>
> Btw, in the logs it doesn't really show any connection attempt just
> advertisements reports so perhaps you want to collect the logs while
> attempting to connect or perhaps you are just waiting for the
> auto-connect to kick in? Does your device appear to be advertising?

I was collecting logs while toggling the "connect" switch in GNOME
settings->bluetooth-> for my bluetooth headset that had already been
paired; and then I chose to "forget" the device in the list; turned
the device off then back on in pairing mode, but it just hangs when I
try to set it up. All while running btmon. Seems like it can see
devices, but won't pair or connect.

When I keep user space the same and revert to kernel 5.16, the headset
immediately connects within seconds of being turned on.

Thanks!

-- 
Chris Murphy