FS#60165 - [linux] 4.18.9 breaks bluetooth

Attached to Project: Arch Linux
Opened by nicolo (nicolo) - Sunday, 23 September 2018, 01:20 GMT
Last edited by Andreas Radke (AndyRTR) - Tuesday, 01 March 2022, 21:25 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Jan Alexander Steffens (heftig)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

After upgrading the kernel to 4.18.9, bluetoothctl is unable to connect to my headphones, giving error

bluetoothd[15413]: Headset Voice gateway rejected org.bluez.Error.Rejected

Downgrading to 4.18.8 works as usual.
This task depends upon

Closed by  Andreas Radke (AndyRTR)
Tuesday, 01 March 2022, 21:25 GMT
Reason for closing:  Fixed
Additional comments about closing:  Fixed upstream.
Comment by Michael (ZeroBeat) - Thursday, 20 June 2019, 20:14 GMT
I can confirm this issue and it is still present in kernel 5.1.11 (5.1.11-arch1-1-ARCH):

Most of the USB devices bluetooth, wifi are not working any longer

example bluetooth device:
32942.700591] usb 1-10.4: new full-speed USB device number 7 using xhci_hcd
[32944.721410] usb 1-10.4: New USB device found, idVendor=0a12, idProduct=0001, bcdDevice=52.76
[32944.721412] usb 1-10.4: New USB device strings: Mfr=0, Product=2, SerialNumber=0
[32945.069015] Bluetooth: hci0: hardware error 0x37

example wifi device:
[ 204.232345] mt76x0u 1-1:1.0: rx urb failed: -71
[ 204.233284] xhci_hcd 0000:00:14.0: WARN Cannot submit Set TR Deq Ptr
[ 204.233291] xhci_hcd 0000:00:14.0: A Set TR Deq Ptr command is pending.
[ 204.263427] mt76x0u 1-1:1.0: TX DMA did not stop

The issue is possible related to xhci and reported on bugzilla.kernel.org here:
https://bugzilla.kernel.org/show_bug.cgi?id=202541

A possible solution is reported to the mailing list here:
https://bugzilla.kernel.org/show_bug.cgi?id=202541#c20

It would be great to revert the patch that caused the trouble until we get an official fix.






Comment by mattia (nTia89) - Monday, 28 February 2022, 16:43 GMT
I cannot reproduce the issue. Is it still valid for you?
Comment by nicolo (nicolo) - Monday, 28 February 2022, 17:20 GMT
I'm not on Arch anymore.
Last time I checked, though, it worked on Void,
so the kernel issue may have been fixed.
Comment by Michael (ZeroBeat) - Monday, 28 February 2022, 17:47 GMT
Looks like that issue has been fixed.
Running 5.16.11-arch1-1 everything is fine.

Loading...