Hi Maxim, On Thu, Feb 24, 2022 at 5:01 AM Maxim Levitsky <mlevitsk@xxxxxxxxxx> wrote: > > On Tue, 2022-02-22 at 10:35 -0800, Luiz Augusto von Dentz wrote: > > Hi Maxim, > > > > On Mon, Feb 21, 2022 at 7:14 PM Maxim Levitsky <mlevitsk@xxxxxxxxxx> 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. > > > I haven't used bluetoothd much but that is what I see: > > [mlevitsk@starship ~]$bluetoothctl > Agent registered > [bluetooth]# scan on > [bluetooth]# scan on > Failed to start discovery: org.bluez.Error.InProgress > [bluetooth]# scan on > Failed to start discovery: org.bluez.Error.InProgress > [bluetooth]# > > No results show up, attempting to scan again shows the InProgres error. Please collect the HCI with btmon. > On my AMD laptop on the other hand (also runs the same 5.17-rc5 kernel), > after 'scan on' I start seeing lots of scan results of various devices near me. > > > journalctl -u bluetooth -b0 > > -- Logs begin at Wed 2022-01-12 11:47:00 IST, end at Thu 2022-02-24 14:50:59 IST. -- > Feb 23 22:16:45 starship systemd[1]: Starting Bluetooth service... > Feb 23 22:16:45 starship bluetoothd[1825]: Bluetooth daemon 5.60 > Feb 23 22:16:45 starship systemd[1]: Started Bluetooth service. > Feb 23 22:16:45 starship bluetoothd[1825]: Starting SDP server > Feb 23 22:16:45 starship bluetoothd[1825]: profiles/network/bnep.c:bnep_init() kernel lacks bnep-protocol support > Feb 23 22:16:45 starship bluetoothd[1825]: src/plugin.c:plugin_init() System does not support network plugin > Feb 23 22:16:45 starship bluetoothd[1825]: Bluetooth management interface 1.21 initialized > Feb 23 22:16:56 starship bluetoothd[1825]: Endpoint registered: sender=:1.251 path=/MediaEndpoint/A2DPSink/sbc > Feb 23 22:16:56 starship bluetoothd[1825]: Endpoint registered: sender=:1.251 path=/MediaEndpoint/A2DPSource/sbc > Feb 23 22:16:56 starship bluetoothd[1825]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset Voice gateway: socket(STREAM, RFCOMM): Protocol not supported (93) > Feb 23 22:16:56 starship bluetoothd[1825]: src/profile.c:ext_start_servers() RFCOMM server failed for Headset unit: socket(STREAM, RFCOMM): Protocol not supported (93) > Feb 23 23:11:21 starship bluetoothd[1825]: Controller resume with wake event 0x0 > Feb 24 09:05:29 starship bluetoothd[1825]: Controller resume with wake event 0x0 > > > 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. Weird, looks like RFCOMM is not available in your system. > I also updated bluez to 5.6 by installing fedora 33 package, and initiallly 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. > > Best regards, > Maxim Levitsky > > > -- Luiz Augusto von Dentz
