Received-SPF: softfail (google.com: domain of transitioning linux-bluetooth-owner@vger.kernel.org does not designate 23.128.96.19 as permitted sender) client-ip=23.128.96.19;
Message-ID: <fc74637a-f3c8-7870-82ec-90bf55b60462@molgen.mpg.de>
Date:   Thu, 24 Feb 2022 16:43:29 +0100
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101
 Thunderbird/91.6.1
Subject: Re: Since commit e8907f76544ffe225ab95d70f7313267b1d0c76d bluetooth
 scanning stopped working on my system
Content-Language: en-US
To:     Maxim Levitsky <mlevitsk@redhat.com>
Cc:     Luiz Augusto von Dentz <luiz.dentz@gmail.com>,
        Luiz Augusto von Dentz <luiz.von.dentz@intel.com>,
        Marcel Holtmann <marcel@holtmann.org>,
        linux-bluetooth@vger.kernel.org
References: <f648f2e11bb3c2974c32e605a85ac3a9fac944f1.camel@redhat.com>
 <CABBYNZKWpPvJvKefgjw5YXCk9BL7900X+XnobLS6gw+50wKNfA@mail.gmail.com>
 <31367223b2e310521493b257244c188f3c22a619.camel@redhat.com>
From:   Paul Menzel <pmenzel@molgen.mpg.de>
In-Reply-To: <31367223b2e310521493b257244c188f3c22a619.camel@redhat.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Precedence: bulk

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:

[…]

> 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’s still about one regression, you 
successfully bisected or not.

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.)

Marcel also replied, he is using btproxy to debug issues, but I did not 
try it, as it wasn’t 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-718f301490b1@molgen.mpg.de/T/#u