From: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
To: Chris Clayton <chris2553@googlemail.com>
Cc: Chris Murphy <lists@colorremedies.com>,
Bluetooth <linux-bluetooth@vger.kernel.org>,
regressions@lists.linux.dev
Subject: Re: bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices
Date: Mon, 28 Feb 2022 11:34:56 -0800 [thread overview]
Message-ID: <CABBYNZJQOSZ1fecTRQOX+w8crdiLdr0_tVstgbnyEVq3NaxscQ@mail.gmail.com> (raw)
In-Reply-To: <16cac2c8-c1ca-c8d7-e3d9-5f00be511614@googlemail.com>
Hi Chris,
On Sat, Feb 26, 2022 at 12:04 AM Chris Clayton <chris2553@googlemail.com> wrote:
>
> Hi,
>
> On 24/02/2022 15:16, Luiz Augusto von Dentz wrote:
> >> I'll try another bisection today, but limit its range to changes made in the net/bluetooth directory.
>
> That bisection has proved very difficult because the bluetooth "service" in kernels at some steps of the bisection were
> completely borked to the extent that blueman's device-manager application wouldn't start and emitted the messages:
>
> blueman-manager 12.00.37 ERROR Manager:137 on_dbus_name_appeared: Default adapter not found, trying first available.
> blueman-manager 12.00.37 ERROR Manager:141 on_dbus_name_appeared: No adapter(s) found, exiting
>
> Obviously, I don't know whether the problem I am trying to pinpoint is hiding behind this more fundamental problem with
> the bluetooth "service", so being unable to say whether that kernel was good or bad, I had to skip. There seems to be a
> batch of commits that mean that, whilst the kernel builds okay, hunting down a bluetooth-related problem is not
> possible. Eventually and I cursed and gave up. Whatever was causing this breakage has obviously been fixed.
>
> > Please record the HCI with btmon, it must be producing something since
> > it records even the mgmt commands.
> >
>
> Refreshed by a good night's sleep, I started another bisection (between 5.16 and 5.17-rc1) yesterday morning but this
> time did not limit it to net/bluetooth. That was going okay until I ran into what I assume is the same batch of borked
> kernels. I've been more persistent this time but have just had a run of 16 steps in which the bluetooth support in the
> kernel is broken so badly that testing bluetooth is not possible. I will push on today, but I've suspended that activity
> to get the hci trace that Luiz has asked for.
>
> Using information from the bisect, I built a kernel that had tested as bad (but not borked). The commit is
> f2b551fad8d8f2ac5e1f810ad595298381e0b0c5. As I've mentioned before, the problem with devices not connecting is
> intermittent - for a given kernel, sometimes a connection works and other times it doesn't. On the first boot of this
> kernel, my bluetooth devices could connect, Attached are 4 files related to this - the output from btmon, and the
> related portions of daemon.log, kern.log and sys.log from /var/log/. Each of the these files is suffixed with ".good".
>
> I then powered down the laptop and booted into the same kernel. This time the bluetooth devices could not connect. Four
> more files are attached for this boot and are suffixed with ".bad". I said in an earlier email that when connection
> fails, there is no output from btmon, so that log is empty. That's still the case, but I guess that fact itself is a
> clue to what the problem might be. What I can add, however, is that if, in that same bad kernel, I unload and then
> reload the btusb module, connections start to work. Maybe that too is a clue. The same unload/load process revives
> bluetooth on a kernel built after a pull of Linus' latest and greatest this morning.
>
> Since I now have a workround, I'm going stop the current bisection that I was doing. I've done another couple of steps
> this morning and both produced kernels on which I could not test bluetooth and had to tell git bisect to skip. If
> however, I can provide any other diagnostics, please let me know.
>
> Chris
Can you try with the following patch:
https://patchwork.kernel.org/project/bluetooth/patch/20220228173918.524733-1-brian.gix@intel.com/
--
Luiz Augusto von Dentz
next prev parent reply other threads:[~2022-02-28 19:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com>
[not found] ` <CAJCQCtRiTQ1BTEHugxhS-zmXFG4qi4WLxsRyZsG9-_Q0isM+7Q@mail.gmail.com>
[not found] ` <CAJCQCtS35JeABLDBaNpfgxjq+ZJ9rZgwtRnSYLNm8tMwtdYGMw@mail.gmail.com>
[not found] ` <CABBYNZKTSe83iP4tm36we4cpAbeGUbEw9frZD1wCM9yo1zry5w@mail.gmail.com>
[not found] ` <CAJCQCtTpHQe2co3fLNs5csKQchmwH=3YwQOvFnuc2nhjRseVnw@mail.gmail.com>
[not found] ` <9ad505e1-7b59-7ebf-378b-23a6c0e25802@googlemail.com>
[not found] ` <CABBYNZ+9tUKgLyUWM5vkMW8vHxYsXv6DEaDWdHt8xTTs6puGQA@mail.gmail.com>
[not found] ` <aaeb4131-d177-d41e-617b-b0060cd83c92@googlemail.com>
[not found] ` <CABBYNZLB+8UzhzttMrKbHW_+-A1EsY9iT5Y55VuOOEPuD4kAHQ@mail.gmail.com>
[not found] ` <b1a4a920-dbba-58be-72b4-2c95b9b79283@googlemail.com>
[not found] ` <82216882-463a-8976-e6bc-4a8919107a31@googlemail.com>
[not found] ` <CABBYNZ+mO1gQgfwhemY9cqbi8vNLm_60A9c1vPYT2tH4rhgFww@mail.gmail.com>
[not found] ` <a35b4b75-bb64-89c8-bacd-d58ed8576272@googlemail.com>
[not found] ` <2ce6175c-74ec-8469-80a5-374bd1429542@googlemail.com>
[not found] ` <CABBYNZJNTOT-mEQe2cfZiEX6A2pR7+sacBqtBRPRZY69YmgtvA@mail.gmail.com>
2022-02-24 10:08 ` bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices 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 [this message]
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
[not found] ` <0ab4466e-1fa8-1904-3f71-770fbd28c83a@leemhuis.info>
2022-03-04 6:21 ` bug kernel 5.17, qualcom and intel adapters, unable to reliably connect to bluetooth devices #forregzbot 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=CABBYNZJQOSZ1fecTRQOX+w8crdiLdr0_tVstgbnyEVq3NaxscQ@mail.gmail.com \
--to=luiz.dentz@gmail.com \
--cc=chris2553@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=lists@colorremedies.com \
--cc=regressions@lists.linux.dev \
/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).