Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:18 as permitted sender) client-ip=2620:137:e000::1:18;
MIME-Version: 1.0
References: <f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com>
 <CABBYNZKWpPvJvKefgjw5YXCk9BL7900X+XnobLS6gw+50wKNfA@mail.gmail.com>
 <31367223b2e310521493b257244c188f3c22a619.camel@redhat.com>
 <fc74637a-f3c8-7870-82ec-90bf55b60462@molgen.mpg.de> <0838aa454b7b127fab1b2a945180304088251b13.camel@redhat.com>
In-Reply-To: <0838aa454b7b127fab1b2a945180304088251b13.camel@redhat.com>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Fri, 25 Feb 2022 14:27:22 -0800
Message-ID: <CABBYNZKMj6yhqsvkx=tcj=tz_9_78r87NBqk6TC1cyO6g4Pesw@mail.gmail.com>
Subject: Re: Since commit e8907f76544ffe225ab95d70f7313267b1d0c76d bluetooth
 scanning stopped working on my system
To:     Maxim Levitsky <mlevitsk@redhat.com>
Cc:     Paul Menzel <pmenzel@molgen.mpg.de>,
        Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
        Marcel Holtmann <marcel@holtmann.org>,
        "linux-bluetooth@vger.kernel.org" <linux-bluetooth@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

Hi Maxim,

On Thu, Feb 24, 2022 at 8:29 AM Maxim Levitsky <mlevitsk@redhat.com> wrote:
>
> On Thu, 2022-02-24 at 16:43 +0100, Paul Menzel wrote:
> > Dear Maxim,
> >
> >
> > Am 24.02.22 um 14:01 schrieb Maxim Levitsky:
> > > On Tue, 2022-02-22 at 10:35 -0800, Luiz Augusto von Dentz wrote:
> > > > On Mon, Feb 21, 2022 at 7:14 PM Maxim Levitsky wrote:
> > > > > Today I updated to a new kernel and I am bisecting few
> > > > > regressions:
> >
> > [=E2=80=A6]
> >
> > > I do notice that even on 5.16 kernel, I am not able to use the HSF
> > > or whatever low quality bi-directional bluetooh protocol is called
> > > for my headset. Used to work, I don't know what broke it, likely not
> > > related to this.
> > >
> > > I also updated bluez to 5.6 by installing fedora 33 package, and
> > > initially it seems to work, but after reboot, the issue shows up
> > > again. Looks like sometimes the scan does work. So far I wasn't able
> > > to make it work even once since then. Reloading btusb doesn't help.
> > > Can't install newer package due to deps on glib sadly. I might be
> > > able to compile it from source, but that will take some time to
> > > figure out how the components of the bluez stack are connected
> > > together.
> > >
> > > For the reference I have 'Intel Corp. AX200 Bluetooth' and I have
> > > the same device on my AMD laptop and both have USB ID 8087:0029 My
> > > AMD laptop has Fedora 34 though.
> >
> > Sorry, I lost track, if it=E2=80=99s still about one regression, you
> > successfully bisected or not.
> yes, I sucessfully bisected the regression. 1 commit before mentioned com=
mit
> the bluetooth works for me, and not after it, with same .config and every=
thing else.
>
>
> >
> > Anyway, passing through the USB Bluetooth device to QEMU helped me [1],
> > and might help you to overcome the dependency problems. (My steps
> > actually worked, but turned out the Linux kernel commit I tested with
> > had another regression not making the Bluetooth controller initialize.)
> First thing I tried, but alas it worked for me in fedora 34 VM I tried to=
 test with
> (with the same 5.17-rc5 kernel, albeet with different .config, more tailo=
red for a VM).

Give it a try with:

https://patchwork.kernel.org/project/bluetooth/patch/20220224232950.56204-1=
-brian.gix@intel.com/

Btw, are there any other users of the MGMT socket? Or it is just bluetoothd=
?

> Best regards,
>         Maxim Levitsky
>
> >
> > Marcel also replied, he is using btproxy to debug issues, but I did not
> > try it, as it wasn=E2=80=99t clear to me how to get it working easily, =
and he
> > also wrote something about non-public patches.
> >
> >
> > Kind regards,
> >
> > Paul
> >
> >
> > [1]:
> > https://lore.kernel.org/linux-bluetooth/5891f0d5-8d51-9da5-7663-718f301=
490b1@molgen.mpg.de/T/#u
> >
>
>


--=20
Luiz Augusto von Dentz