From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Chris Murphy <lists@colorremedies.com>
Cc: Bluetooth <linux-bluetooth@vger.kernel.org>
Subject: Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
Date: Wed, 16 Feb 2022 15:49:45 -0800 [thread overview]
Message-ID: <CABBYNZKfy-ntFhbx0TStNwFiwxCF4sPVaHS4wDbef0shb=pawg@mail.gmail.com> (raw)
In-Reply-To: <CAJCQCtRYKbTQ16eUq2qODZ=dE=HB6pZpLNswdqMbiWw+DBE9KQ@mail.gmail.com>
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:
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?
>
>
> >
> > This matches with a complaint I found here
> > https://lore.kernel.org/linux-bluetooth/20220125144639.2226-1-mike@fireburn.co.uk/
> > about this patch
> > https://lore.kernel.org/linux-bluetooth/20211201000215.1134831-13-luiz.dentz@gmail.com/
> >
> >
> >
> > --
> > Chris Murphy
>
>
>
> --
> Chris Murphy
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2022-02-16 23:49 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-11 1:44 bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices Chris Murphy
2022-02-15 15:29 ` Chris Murphy
2022-02-15 15:38 ` Chris Murphy
2022-02-16 3:47 ` Chris Murphy
2022-02-16 23:49 ` Luiz Augusto von Dentz [this message]
2022-02-17 1:35 ` Chris Murphy
2022-02-17 23:36 ` Chris Murphy
2022-02-18 0:15 ` Luiz Augusto von Dentz
2022-02-18 3:49 ` Chris Murphy
2022-02-21 11:39 ` Chris Clayton
2022-02-21 13:22 ` Chris Clayton
2022-02-21 17:11 ` Luiz Augusto von Dentz
2022-02-21 20:23 ` Chris Clayton
2022-02-21 21:27 ` Luiz Augusto von Dentz
2022-02-21 22:33 ` Chris Clayton
2022-02-22 20:03 ` Chris Clayton
2022-02-23 17:51 ` Luiz Augusto von Dentz
2022-02-23 22:42 ` Chris Clayton
2022-02-24 5:59 ` Chris Clayton
2022-02-24 8:16 ` Luiz Augusto von Dentz
2022-02-24 10:08 ` Chris Clayton
2022-02-24 15:16 ` Luiz Augusto von Dentz
2022-02-24 16:18 ` Thorsten Leemhuis
2022-02-26 8:04 ` Chris Clayton
2022-02-28 19:34 ` Luiz Augusto von Dentz
2022-02-28 21:02 ` Chris Clayton
2022-02-28 21:20 ` Luiz Augusto von Dentz
2022-03-01 9:26 ` Chris Clayton
2022-03-01 18:34 ` Luiz Augusto von Dentz
2022-03-01 18:56 ` Chris Clayton
2022-03-01 18:57 ` Luiz Augusto von Dentz
2022-03-01 19:40 ` Chris Clayton
2022-03-01 22:40 ` Luiz Augusto von Dentz
2022-03-01 22:47 ` Luiz Augusto von Dentz
2022-03-02 2:31 ` Luiz Augusto von Dentz
2022-03-02 6:55 ` Luiz Augusto von Dentz
2022-03-02 9:59 ` Chris Clayton
2022-03-02 8:54 ` Chris Clayton
2022-02-24 8:24 ` Chris Clayton
2022-02-21 17:12 ` Luiz Augusto von Dentz
2022-02-21 17:18 ` Luiz Augusto von Dentz
2022-02-24 10:26 ` Thorsten Leemhuis
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CABBYNZKfy-ntFhbx0TStNwFiwxCF4sPVaHS4wDbef0shb=pawg@mail.gmail.com' \
--to=luiz.dentz@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lists@colorremedies.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).