Received-SPF: pass (google.com: domain of linux-bluetooth-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com>
In-Reply-To: <f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com>
From:   Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Date:   Tue, 22 Feb 2022 10:35:48 -0800
Message-ID: <CABBYNZKWpPvJvKefgjw5YXCk9BL7900X+XnobLS6gw+50wKNfA@mail.gmail.com>
Subject: Re: Since commit e8907f76544ffe225ab95d70f7313267b1d0c76d bluetooth
 scanning stopped working on my system
To:     Maxim Levitsky <mlevitsk@redhat.com>
Cc:     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"
Precedence: bulk

Hi Maxim,

On Mon, Feb 21, 2022 at 7:14 PM Maxim Levitsky <mlevitsk@redhat.com> wrote:
>
> Today I updated to a new kernel and I am bisecting few regressions:
>
> I noticed that if I open GNOME's bluetooth setting, it hangs for like minute or so,
> and then shows only the paired devices and no scan results.
>
> I bisected this to this commit.
>
> For reference I am running fairly old fedora 32 on this machine, and thus I have
> bluez 5.55 and stock GNOME from fedora 32.
>
> I can provide any more info on anything if required and/or test patches.
>
> I wasn't able tor revert this commit as it is part of a bigger rewrite of scanning
> which makes sense.
>
> I tried merging bluetooth-next master as of today,
> into my kernel but no noticeable improvement.

Is there any error being reported in bluetoothd, does bluetoothctl
have the same problem? It would be great if you could provide an HCI
trace of the problem.

-- 
Luiz Augusto von Dentz