Description of problem: Bluetooth stopped working since kernel 4.13.16 Version-Release number of selected component (if applicable): kernel-4.13.16-300.fc27.x86_64 How reproducible: Occurs at every boot with kernel 4.13.16 or later. With 4.13.13 bluetooth works fine. Steps to Reproduce: 1. update to kernel-4.13.16-300.fc27.x86_64 or later 2. try to use bluetooth 3. Actual results: bluetooth is not working Expected results: working bluetooth Additional info: Laptop model : Razer Blade Stealth (late 2016) Bluetooth device (output from lsusb) : Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications $ dmesg | grep -i bluetooth [ 3.806024] SELinux: Class bluetooth_socket not defined in policy. [ 4.349499] Bluetooth: Core ver 2.22 [ 4.349514] Bluetooth: HCI device and connection manager initialized [ 4.349516] Bluetooth: HCI socket layer initialized [ 4.349517] Bluetooth: L2CAP socket layer initialized [ 4.349523] Bluetooth: SCO socket layer initialized [ 4.382836] Bluetooth: HCI UART driver ver 2.3 [ 4.382838] Bluetooth: HCI UART protocol H4 registered [ 4.382839] Bluetooth: HCI UART protocol BCSP registered [ 4.382850] Bluetooth: HCI UART protocol LL registered [ 4.382851] Bluetooth: HCI UART protocol ATH3K registered [ 4.382851] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 4.382874] Bluetooth: HCI UART protocol Intel registered [ 4.382892] Bluetooth: HCI UART protocol Broadcom registered [ 4.382893] Bluetooth: HCI UART protocol QCA registered [ 4.382893] Bluetooth: HCI UART protocol AG6XX registered [ 4.382894] Bluetooth: HCI UART protocol Marvell registered [ 6.106100] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 6.106101] Bluetooth: BNEP filters: protocol multicast [ 6.106104] Bluetooth: BNEP socket layer initialized [ 16.726552] Bluetooth: RFCOMM TTY layer initialized [ 16.726557] Bluetooth: RFCOMM socket layer initialized [ 16.726660] Bluetooth: RFCOMM ver 1.11 [ 18.784265] Bluetooth: hci0 command 0x0c24 tx timeout [ 20.831305] Bluetooth: hci0 command 0x0c52 tx timeout [ 951.786550] Bluetooth: hci0 urb ffff9a5ce5c91900 failed to resubmit (113) [ 964.778749] Bluetooth: hci0 urb ffff9a5c448b26c0 failed to resubmit (113)
I'm experiencing the same issue on a Dell XPS 13 9360, using a Killer 1535 WiFi/BT adapter (based on something from Qualcomm, QCA6174). I assume it's the same device embedded in the Razer Blade Stealth from the original bug report. With the two following kernels I can't get my BT mouse (a Logitech MX Master 2S) to work: kernel-core-4.13.16-300.fc27.x86_64 kernel-core-4.13.16-302.fc27.x86_64 If I boot with an older kernel-core-4.13.13-300.fc27.x86_64 the mouse works fine (it worked without issues also in F26). # lsusb | grep Qualcomm Bus 001 Device 002: ID 0cf3:e300 Qualcomm Atheros Communications [ 10.600984] Bluetooth: Core ver 2.22 [ 10.601580] Bluetooth: HCI device and connection manager initialized [ 10.601592] Bluetooth: HCI socket layer initialized [ 10.601603] Bluetooth: L2CAP socket layer initialized [ 10.601649] Bluetooth: SCO socket layer initialized [ 10.698369] Bluetooth: HCI UART driver ver 2.3 [ 10.698377] Bluetooth: HCI UART protocol H4 registered [ 10.698382] Bluetooth: HCI UART protocol BCSP registered [ 10.698478] Bluetooth: HCI UART protocol LL registered [ 10.698483] Bluetooth: HCI UART protocol ATH3K registered [ 10.698488] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 10.698603] Bluetooth: HCI UART protocol Intel registered [ 10.698744] Bluetooth: HCI UART protocol Broadcom registered [ 10.698749] Bluetooth: HCI UART protocol QCA registered [ 10.698753] Bluetooth: HCI UART protocol AG6XX registered [ 10.698758] Bluetooth: HCI UART protocol Marvell registered [ 12.451537] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 12.451538] Bluetooth: BNEP filters: protocol multicast [ 12.451540] Bluetooth: BNEP socket layer initialized [ 23.663822] Bluetooth: RFCOMM TTY layer initialized [ 23.663828] Bluetooth: RFCOMM socket layer initialized [ 23.663966] Bluetooth: RFCOMM ver 1.11 [ 25.695871] Bluetooth: hci0 command 0x0c24 tx timeout [ 27.760268] Bluetooth: hci0 command 0x0c52 tx timeout
I'm facing the same issue on my Dell XPS 13 9360 with Qualcomm Atheros QCA6174 wifi chipset. No matter which rf-related command is entered via bluetoothctl, dmesg shows various timeout errors: [ 1542.589333] Bluetooth: hci0 command 0x200b tx timeout [ 1544.637326] Bluetooth: hci0 command 0x200c tx timeout [ 1552.573308] Bluetooth: hci0 command 0x2005 tx timeout [ 1554.621137] Bluetooth: hci0 command 0x200b tx timeout [ 1556.669156] Bluetooth: hci0 command 0x200c tx timeout [ 1564.541072] Bluetooth: hci0 command 0x2005 tx timeout [ 1566.589236] Bluetooth: hci0 command 0x200b tx timeout [ 1568.637145] Bluetooth: hci0 command 0x200c tx timeout [ 1576.573186] Bluetooth: hci0 command 0x2005 tx timeout [ 1578.621030] Bluetooth: hci0 command 0x200b tx timeout [ 1580.668949] Bluetooth: hci0 command 0x200c tx timeout [ 1588.540939] Bluetooth: hci0 command 0x2005 tx timeout [ 1590.589076] Bluetooth: hci0 command 0x200b tx timeout [ 1592.637083] Bluetooth: hci0 command 0x200c tx timeout [ 1600.572970] Bluetooth: hci0 command 0x2005 tx timeout [ 1602.620987] Bluetooth: hci0 command 0x200b tx timeout [ 1604.668808] Bluetooth: hci0 command 0x200c tx timeout [ 1612.540921] Bluetooth: hci0 command 0x2005 tx timeout [ 1614.588897] Bluetooth: hci0 command 0x200b tx timeout [ 1616.636886] Bluetooth: hci0 command 0x200c tx timeout [ 1624.572831] Bluetooth: hci0 command 0x2005 tx timeout [ 1626.620891] Bluetooth: hci0 command 0x200b tx timeout [ 1628.668674] Bluetooth: hci0 command 0x200c tx timeout Earlier dmesg entries: [ 8.142611] Bluetooth: Core ver 2.22 [ 8.142624] Bluetooth: HCI device and connection manager initialized [ 8.142626] Bluetooth: HCI socket layer initialized [ 8.142628] Bluetooth: L2CAP socket layer initialized [ 8.142633] Bluetooth: SCO socket layer initialized [ 8.154280] Bluetooth: HCI UART driver ver 2.3 [ 8.154281] Bluetooth: HCI UART protocol H4 registered [ 8.154281] Bluetooth: HCI UART protocol BCSP registered [ 8.154293] Bluetooth: HCI UART protocol LL registered [ 8.154293] Bluetooth: HCI UART protocol ATH3K registered [ 8.154294] Bluetooth: HCI UART protocol Three-wire (H5) registered [ 8.154318] Bluetooth: HCI UART protocol Intel registered [ 8.154335] Bluetooth: HCI UART protocol Broadcom registered [ 8.154335] Bluetooth: HCI UART protocol QCA registered [ 8.154336] Bluetooth: HCI UART protocol AG6XX registered [ 8.154336] Bluetooth: HCI UART protocol Marvell registered [ 9.493674] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 9.493675] Bluetooth: BNEP filters: protocol multicast [ 9.493677] Bluetooth: BNEP socket layer initialized [ 17.101991] Bluetooth: RFCOMM TTY layer initialized [ 17.101996] Bluetooth: RFCOMM socket layer initialized [ 17.102051] Bluetooth: RFCOMM ver 1.11 If you need any further information feel free to ask.
Hello, Can you confirm whether or not v4.13.15 introduced the issue? v4.13.15 build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1003161 v4.13.14 build: https://koji.fedoraproject.org/koji/buildinfo?buildID=1002396 Thanks!
In addition to the v4.13.15 and v4.13.14 builds, I started a scratch build[0] with a candidate patch reverted. Once it's finished, can you test to see if the problem reproducible with it? [0] https://koji.fedoraproject.org/koji/taskinfo?taskID=23645121
Hi Jeremy, thanks for your effort! I've tried all the versions you suggested. Here are the results: 4.13.13-300: Works 4.13.14-300: Works 4.13.15-300: Does not work! 4.13.16-302: Does not work! 4.13.15-301: (scratch) Works! :-) Your scratch version seems to fix it.
Great, thanks! It looks like this has already been reported upstream so I've linked this report to the kernel bugzilla report.
Hi Jeremy, I can confirm Thomas' report: 4.13.14-300: OK 4.13.15-300: Not working 4.13.15-301: OK Thanks a lot
Update: Just installed 4.14.3-300.fc27.x86_64 from the Fedora 27 Repo. Bluetooth works again for me! :-) @Jeremy: I'm not sure if the issue in the kernel.org bugtracker is the same. I was not using TLP and 4.14 works fine on my machine.
Like Thomas, I've just updated to 4.14.3-300.fc27.x86_64 and BT seems to work fine (no issues so far).
We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. As kernel maintainers, we try to keep up with bugzilla but due the rate at which the upstream kernel project moves, bugs may be fixed without any indication to us. Due to this, we are doing a mass bug update across all of the Fedora 27 kernel bugs. Fedora 27 has now been rebased to 4.15.3-300.f27. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you experience different issues, please open a new bug report for those.
The issue is gone with all the latest kernels, including 4.15.3-300.