Bug 2053283
| Summary: | Cannot connect to Bluetooth mouse with kernel 5.17 | ||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Adam Williamson (Red Hat non-Fedora) <awilliam> | ||||||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||||||
| Status: | CLOSED RAWHIDE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||||||
| Severity: | high | Docs Contact: | |||||||||||||||
| Priority: | unspecified | ||||||||||||||||
| Version: | rawhide | CC: | acaringi, adscvr, airlied, alciregi, bskeggs, bugzilla, glesage, hdegoede, jarodwilson, jeremy, jglisse, jonathan, josef, kernel-maint, lgoncalv, linville, masami256, mchehab, ptalbert, steved | ||||||||||||||
| Target Milestone: | --- | ||||||||||||||||
| Target Release: | --- | ||||||||||||||||
| Hardware: | All | ||||||||||||||||
| OS: | Linux | ||||||||||||||||
| Whiteboard: | |||||||||||||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||||||||||||
| Doc Text: | Story Points: | --- | |||||||||||||||
| Clone Of: | Environment: | ||||||||||||||||
| Last Closed: | 2022-03-08 23:48:00 UTC | Type: | Bug | ||||||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||||||
| Documentation: | --- | CRM: | |||||||||||||||
| Verified Versions: | Category: | --- | |||||||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||||||
| Embargoed: | |||||||||||||||||
| Attachments: |
|
||||||||||||||||
|
Description
Adam Williamson (Red Hat non-Fedora)
2022-02-10 20:45:14 UTC
Created attachment 1860445 [details]
boot messages
Created attachment 1860446 [details]
output of /usr/libexec/bluetooth/bluetoothd -n -d
I tried stopping bluetooth.service and running /usr/libexec/bluetooth/bluetoothd -n -d , waiting for a while, then attempting to force a connection to my mouse from GNOME Bluetooth settings (which didn't work). Then I did ctrl-c to end the bluetoothd run. This is the output from that session.
The system is an XPS 13 laptop, the 9360 "Kaby Lake" model. `btmgmt info` says this: [root@xps13k adamw]# btmgmt info Index list with 1 item hci0: Primary controller addr 9C:B6:D0:D0:D1:BE version 8 manufacturer 29 class 0x00010c supported settings: powered connectable fast-connectable discoverable bondable link-security ssp br/edr le advertising secure-conn debug-keys privacy configuration static-addr phy-configuration wide-band-speech current settings: powered ssp br/edr le secure-conn name BlueZ 5.63 short name hci0: Configuration options supported options: public-address missing options: not sure what else would help to debug, please let me know. Thanks! Created attachment 1860485 [details]
btmon for 90s
Bus 001 Device 005: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bluetooth monitor ver 5.63
= Note: Linux version 5.17.0-0.rc3.89.fc36.x86_64 (x86_64) 0.059832
= Note: Bluetooth subsystem version 2.22 0.059833
= New Index: C8:E2:65:04:99:CF (Primary,USB,hci0) [hci0] 0.059834
= Open Index: C8:E2:65:04:99:CF [hci0] 0.059835
= Index Info: C8:E2:65:04:99:CF (Intel Corp.)
Run btmon for about 90s while scanning for devices and trying to pair with one.
I've got a ton of these: Feb 10 14:49:21 fovo.local bluetoothd[836]: src/adv_monitor.c:btd_adv_monitor_offload_supported() Manager is NULL, get offload support failed Bunch of these Feb 10 14:49:57 fovo.local gnome-control-c[39502]: Setting up /org/bluez/hci0/dev_38_18_4C_24_2D_1D failed: Timeout was reached Feb 10 14:50:07 fovo.local gnome-control-c[39502]: Setting up /org/bluez/hci0/dev_38_18_4C_24_2D_1D failed: GDBus.Error:org.bluez.Error.InProgress: In Progress Feb 10 14:50:08 fovo.local gnome-control-c[39502]: Setting up /org/bluez/hci0/dev_38_18_4C_24_2D_1D failed: GDBus.Error:org.bluez.Error.InProgress: In Progress Feb 10 14:50:09 fovo.local gnome-control-c[39502]: Setting up /org/bluez/hci0/dev_38_18_4C_24_2D_1D failed: GDBus.Error:org.bluez.Error.InProgress: In Progress Feb 10 14:51:32 fovo.local bluetoothd[836]: Pair device timed out for hci0 Scanning is flaky, sometimes it sees things sometimes not. When it sees my Sony headset, I try to pair in GNOME Shell by clicking on the words "Not Set Up" in Settings, and nothing happens. No error in Shell, the "button" for the device recesses, but no additional dialog comes up to pair. And I see the above messages in journal. So other than transiently OK scanning, pairing is 100% broken. Created attachment 1860499 [details]
journalctl with bluetoothd -d
This is about 5 minutes of bluetoothd debug (systemd is also in debug mode so this is quite verbose) while trying various things. Near the end it did eventually pair and I was able to get sound. But it was like wrestling a snapping turtle.
Created attachment 1860501 [details]
lsusb -v output for a USB device that seems to be a bluetooth controller
One USB device claims to be a bluetooth controller. It's listed as Qualcomm/Atheros. Here is the lsusb -v output for it. These are the bluetooth modules that show in lsmod:
btusb 65536 0
btrtl 28672 1 btusb
btbcm 20480 1 btusb
btintel 45056 1 btusb
bluetooth 692224 37 btrtl,btintel,btbcm,bnep,btusb,rfcomm
Started a thread https://lore.kernel.org/linux-bluetooth/CAJCQCtSeUtHCgsHXLGrSTWKmyjaQDbDNpP4rb0i+RE+L2FTXSA@mail.gmail.com/T/#u No improvement in 5.17.0-rc4. I am seeing errors that take the form: [ 15.731405] kernel: Bluetooth: hci0: unexpected event 0xff length: 5 > 0 This matches with a complaint I found here https://lore.kernel.org/linux-bluetooth/20220125144639.2226-1-mike@fireburn.co.uk/ about this patch https://lore.kernel.org/linux-bluetooth/20211201000215.1134831-13-luiz.dentz@gmail.com/ I've also got a lockdep warning when running +debug kernels: [ 26.657824] kernel: krfcommd/1391 is trying to acquire lock: [ 26.657831] kernel: ffff8d697a534940 (sk_lock-AF_BLUETOOTH-BTPROTO_RFCOMM){+.+.}-{0:0}, at: rfcomm_sk_state_change+0x4d/0x110 [rfcomm] Created attachment 1861289 [details]
filtered dmesg 5.17.0-rc4
includes the full lockdep warning and deadlock backtrace
FEDORA-2022-2aa7c08b53 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-2aa7c08b53 FEDORA-2022-9d4e48836d has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-9d4e48836d Those updates don't fix this bug, it was a mispaste. Setting back to ASSIGNED. Still valid with kernel-core-5.17.0-0.rc5.102.fc37.x86_64 . Seems fixed with 5.17.0-0.rc7! I'll edit the update and mark it as fixing this bug. Actually, I filed this against Rawhide so I'll just close it. I'm still seeing problems with Bluetooth on my XPS 13 9360 and ThinkPad T14s, with problems scanning and this in my dmesg: [ 495.039893] Bluetooth: hci0: unexpected event 0xff length: 4 > 0 And this is with 5.17.0-0.rc7.116.fc36.x86_64 on Fedora 36 pre-beta on both Workstation and Silverblue. Related issue I opened (that I assigned to bluez): https://bugzilla.redhat.com/show_bug.cgi?id=2066216 Removing /var/lib/bluetoothn/* and rebooting allows scanning (+ pairing) to work again for a bit, but it eventually fails again, even across reboots, if there's anything in /var/lib/bluetooth/. Try updating to rc8. rc7 still had problems for me (I lost the mouse on suspend/resume), but with rc8 it seems to be back to working perfectly. |