[Bug 1216799] New: Bluetooth headphones disconnect from USB bluetooth dongle
https://bugzilla.suse.com/show_bug.cgi?id=1216799 Bug ID: 1216799 Summary: Bluetooth headphones disconnect from USB bluetooth dongle Classification: openSUSE Product: openSUSE Distribution Version: Leap 15.5 Hardware: Other OS: Other Status: NEW Severity: Normal Priority: P5 - None Component: Kernel Assignee: kernel-bugs@opensuse.org Reporter: silviu_marin-caea@otpbank.ro QA Contact: qa-bugs@suse.de Target Milestone: --- Found By: --- Blocker: --- I have bluetooth headphones (Jabra Elite 65t) and bluetooth dongle (Asus USB-BT500). They work at first but when the dongle goes into USB powersave, the headphones get disconnected and don't reconnect properly unless I reinsert the dongle. When it's all good, the headphones appear as High Fidelity Playback A2DP Sink, codec AAC. hwinfo --bluetooth 05: USB 00.1: 11500 Bluetooth Device [Created at usb.122] Unique ID: XN68.bg_nBq8ya6A Parent ID: KgLP.erpEvbsFWX1 SysFS ID: /devices/pci0000:00/0000:00:13.0/usb9/9-4/9-4:1.1 SysFS BusID: 9-4:1.1 Hardware Class: bluetooth Model: "ASUSTek ASUS USB-BT500" Hotplug: USB Vendor: usb 0x0b05 "ASUSTek Computer, Inc." Device: usb 0x190e "ASUS USB-BT500" Revision: "2.00" Serial ID: "00E04C239987" Driver: "btusb" Driver Modules: "btusb" Speed: 12 Mbps Module Alias: "usb:v0B05p190Ed0200dcE0dsc01dp01icE0isc01ip01in01" Driver Info #0: Driver Status: btusb is active Driver Activation Cmd: "modprobe btusb" Config Status: cfg=new, avail=yes, need=no, active=unknown Attached to: #14 (Hub) dmesg | grep Bluetooth [ 6.357471] Bluetooth: Core ver 2.22 [ 6.357495] Bluetooth: HCI device and connection manager initialized [ 6.357499] Bluetooth: HCI socket layer initialized [ 6.357502] Bluetooth: L2CAP socket layer initialized [ 6.357506] Bluetooth: SCO socket layer initialized [ 6.413147] Bluetooth: hci0: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 6.415122] Bluetooth: hci0: RTL: rom_version status=0 version=1 [ 6.415126] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 6.439520] Bluetooth: hci0: RTL: loading rtl_bt/rtl8761bu_config.bin [ 6.444090] Bluetooth: hci0: RTL: cfg_sz 6, total sz 30210 [ 6.715122] Bluetooth: hci0: RTL: fw version 0xdfc6d922 [ 6.841248] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.841252] Bluetooth: BNEP filters: protocol multicast [ 6.841257] Bluetooth: BNEP socket layer initialized [ 6.843260] Bluetooth: MGMT ver 1.22 [ 50.972325] Bluetooth: RFCOMM TTY layer initialized [ 50.972333] Bluetooth: RFCOMM socket layer initialized [ 50.972338] Bluetooth: RFCOMM ver 1.11 ... [ 54.394435] input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input19 I see this in dmesg when it reconnects and it works: [ 486.890067] usb 9-4: USB disconnect, device number 2 [ 487.114036] usb 9-4: new full-speed USB device number 3 using ohci-pci [ 487.351164] usb 9-4: New USB device found, idVendor=0b05, idProduct=190e, bcdDevice= 2.00 [ 487.351171] usb 9-4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 487.351173] usb 9-4: Product: ASUS USB-BT500 [ 487.351175] usb 9-4: Manufacturer: Realtek [ 487.351177] usb 9-4: SerialNumber: 00E04C239987 [ 487.358124] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=dfc6 lmp_ver=0a lmp_subver=d922 [ 487.568138] Bluetooth: hci1: RTL: examining hci_ver=0a hci_rev=000b lmp_ver=0a lmp_subver=8761 [ 487.570174] Bluetooth: hci1: RTL: rom_version status=0 version=1 [ 487.570177] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_fw.bin [ 487.572606] Bluetooth: hci1: RTL: loading rtl_bt/rtl8761bu_config.bin [ 487.572715] Bluetooth: hci1: RTL: cfg_sz 6, total sz 30210 [ 487.842193] Bluetooth: hci1: RTL: fw version 0xdfc6d922 [ 487.944392] Bluetooth: MGMT ver 1.22 [ 493.763658] input: Jabra Elite 65t (AVRCP) as /devices/virtual/input/input20 And many of these when it disconnects and doesn't work anymore: [ 852.621709] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 856.465806] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 859.097858] usb 9-4: reset full-speed USB device number 3 using ohci-pci Then this: [ 923.675107] Bluetooth: hci1: command 0x0428 tx timeout [ 963.676107] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 965.176409] Bluetooth: hci1: link tx timeout [ 965.176429] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 965.692007] Bluetooth: hci1: command 0x041f tx timeout [ 967.712098] Bluetooth: hci1: command 0x0406 tx timeout [ 968.516073] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 969.698590] Bluetooth: hci1: link tx timeout [ 969.698605] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 971.512214] usb 9-4: reset full-speed USB device number 3 using ohci-pci [ 974.560260] usb 9-4: reset full-speed USB device number 3 using ohci-pci ... [ 1080.406158] Bluetooth: hci1: killing stalled connection 70:bf:92:6b:13:31 [ 1082.334436] Bluetooth: hci1: command 0x0408 tx timeout [ 1082.334458] Bluetooth: hci1: No gpio to reset Realtek device, ignoring [ 1084.350582] Bluetooth: hci1: command 0x0408 tx timeout [ 1084.350603] Bluetooth: hci1: No gpio to reset Realtek device, ignoring -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1216799 https://bugzilla.suse.com/show_bug.cgi?id=1216799#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(silviu_marin-caea | |@otpbank.ro) CC| |silviu_marin-caea@otpbank.r | |o, tiwai@suse.com --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Is this a regression from older kernels? -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1216799 https://bugzilla.suse.com/show_bug.cgi?id=1216799#c2 Silviu Marin-Caea <silviu_marin-caea@otpbank.ro> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(silviu_marin-caea | |@otpbank.ro) | --- Comment #2 from Silviu Marin-Caea <silviu_marin-caea@otpbank.ro> --- Yes, it's a regression. I just checked with the kernel from 15.3. I installed only the kernel packages, Nvidia drivers and util-linux to satisfy the kernel dependency. Everything else on the machine is 15.5 with all updates. kernel-default-5.3.18-57.3.x86_64 The bluetooth headphone does not disconnect anymore, it works reliably. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1216799 https://bugzilla.suse.com/show_bug.cgi?id=1216799#c3 --- Comment #3 from Silviu Marin-Caea <silviu_marin-caea@otpbank.ro> --- The kernel from 15.4 had the bug, I tried it. With kernel-default-5.14.21-150400.22.1, the headphone gets disconnected -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1216799 https://bugzilla.suse.com/show_bug.cgi?id=1216799#c4 --- Comment #4 from Silviu Marin-Caea <silviu_marin-caea@otpbank.ro> --- (In reply to Silviu Marin-Caea from comment #2)
Actually, no, it disconnects with this kernel too. It only worked well once. I'll try older kernels. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1216799 https://bugzilla.suse.com/show_bug.cgi?id=1216799#c5 --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- If the older kernels still show the problem, it might be a problem of the BT firmware. You can try to downgrade kernel-firmware-bluetooth stuff, too. -- You are receiving this mail because: You are the assignee for the bug.
https://bugzilla.suse.com/show_bug.cgi?id=1216799 https://bugzilla.suse.com/show_bug.cgi?id=1216799#c6 Silviu Marin-Caea <silviu_marin-caea@otpbank.ro> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |INVALID Status|NEW |RESOLVED --- Comment #6 from Silviu Marin-Caea <silviu_marin-caea@otpbank.ro> --- Finally, I got a laptop where I planned to install 15.0 to see if it works with that. But I started from 15.5 to have a baseline where it doesn't work. Except it did work. I could not reproduce it. So I thought what could cause it on my desktop at home? Well, there is an USB extension cord that I connected the dongle with. Turns out there are no bluetooth disconnections if I plug the dongle directly into the PC. I'm closing the bug as invalid, sorry about the wasted time. -- You are receiving this mail because: You are the assignee for the bug.
participants (1)
-
bugzilla_noreply@suse.com