Description of problem: latest kernel (kernel-4.13.4-200.fc26.x86_64) screwed bluetooth Version-Release number of selected component (if applicable): kernel-4.13.4-200.fc26.x86_64 How reproducible: new kernel makes bluetooth unusable (unable to connect new diveces, the old ones (the paired ones) do no work anymore Steps to Reproduce: 1. update to latest kernel-4.13.4-200.fc26.x86_64 2. use bluetooth 3. Actual results: bluetooth does not work Expected results: bluetooth works Additional info: my usb hardware (thinkpad x carbon 4gen) Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 005: ID 138a:0090 Validity Sensors, Inc. Bus 001 Device 004: ID 04f2:b5c1 Chicony Electronics Co., Ltd Bus 001 Device 003: ID 8087:0a2b Intel Corp. <== BLUETOOTH Bus 001 Device 002: ID 1199:9079 Sierra Wireless, Inc. Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
the nex kernel, version kernel-4.13.5-200.fc26.x86_64, has the same issues with bt. here comes what I get using dmesg: NOT WORKING dmesg |grep -i bluetooth [ 4.672608] SELinux: Class bluetooth_socket not defined in policy. [ 5.183262] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [ 5.275089] Bluetooth: Core ver 2.22 [ 5.275105] Bluetooth: HCI device and connection manager initialized [ 5.275107] Bluetooth: HCI socket layer initialized [ 5.275109] Bluetooth: L2CAP socket layer initialized [ 5.275116] Bluetooth: SCO socket layer initialized [ 5.322113] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 5.330024] Bluetooth: hci0: Device revision is 5 [ 5.330025] Bluetooth: hci0: Secure boot is enabled [ 5.330026] Bluetooth: hci0: OTP lock is enabled [ 5.330027] Bluetooth: hci0: API lock is enabled [ 5.330027] Bluetooth: hci0: Debug lock is disabled [ 5.330028] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 5.335392] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 6.958537] Bluetooth: hci0: Waiting for firmware download to complete [ 6.958739] Bluetooth: hci0: Firmware loaded in 1601273 usecs [ 6.958770] Bluetooth: hci0: Waiting for device to boot [ 6.969748] Bluetooth: hci0: Device booted in 10728 usecs [ 6.970533] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [ 6.974025] Bluetooth: hci0: Applying Intel DDC parameters completed [ 7.136729] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7.136730] Bluetooth: BNEP filters: protocol multicast [ 7.136733] Bluetooth: BNEP socket layer initialized [ 24.998268] Bluetooth: RFCOMM TTY layer initialized [ 24.998276] Bluetooth: RFCOMM socket layer initialized [ 24.998354] Bluetooth: RFCOMM ver 1.11 [ 52.702832] Bluetooth: Failed to disable LE scan: status 0x0c [ 55.449801] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 55.449808] Bluetooth: HIDP socket layer initialized the bt is so screwed up that I had to delete the bt mouse definition and perform a new pairing. when this issue is present, I am unable to detect new (not paired) devices also. everything is working fine with kernel 4.12.14-300.fc26.x86_64 the proper bt behaviour: WORKING (PREVIOUS KERNEL) [konrad@deathstar Dropbox]$ uname -a Linux deathstar 4.12.14-300.fc26.x86_64 #1 SMP Wed Sep 20 16:28:07 UTC 2017 x86_64 x86_64 x86_64 GNU/Linux [konrad@deathstar Dropbox]$ dmesg |grep -i bluetooth [ 4.868729] SELinux: Class bluetooth_socket not defined in policy. [ 5.503364] thinkpad_acpi: rfkill switch tpacpi_bluetooth_sw: radio is unblocked [ 5.608797] Bluetooth: Core ver 2.22 [ 5.608812] Bluetooth: HCI device and connection manager initialized [ 5.608814] Bluetooth: HCI socket layer initialized [ 5.608816] Bluetooth: L2CAP socket layer initialized [ 5.608821] Bluetooth: SCO socket layer initialized [ 5.657145] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014 [ 5.664230] Bluetooth: hci0: Device revision is 5 [ 5.664231] Bluetooth: hci0: Secure boot is enabled [ 5.664231] Bluetooth: hci0: OTP lock is enabled [ 5.664232] Bluetooth: hci0: API lock is enabled [ 5.664232] Bluetooth: hci0: Debug lock is disabled [ 5.664233] Bluetooth: hci0: Minimum firmware build 1 week 10 2014 [ 5.669730] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi [ 7.291780] Bluetooth: hci0: Waiting for firmware download to complete [ 7.292176] Bluetooth: hci0: Firmware loaded in 1598343 usecs [ 7.292273] Bluetooth: hci0: Waiting for device to boot [ 7.303185] Bluetooth: hci0: Device booted in 10691 usecs [ 7.303496] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc [ 7.307245] Bluetooth: hci0: Applying Intel DDC parameters completed [ 7.627928] Bluetooth: BNEP (Ethernet Emulation) ver 1.3 [ 7.627932] Bluetooth: BNEP filters: protocol multicast [ 7.627948] Bluetooth: BNEP socket layer initialized [ 55.565424] Bluetooth: RFCOMM TTY layer initialized [ 55.565429] Bluetooth: RFCOMM socket layer initialized [ 55.565520] Bluetooth: RFCOMM ver 1.11 [ 65.883445] Bluetooth: HIDP (Human Interface Emulation) ver 1.2 [ 65.883448] Bluetooth: HIDP socket layer initialized [ 65.884287] input: Microsoft Bluetooth Notebook Mouse 5000 as /devices/pci0000:00/0000:00:14.0/usb1/1-7/1-7:1.0/bluetooth/hci0/hci0:256/0005:045E:0700.0003/input/input17 [ 65.884634] hid-generic 0005:045E:0700.0003: input,hidraw0: BLUETOOTH HID v1.00 Mouse [Microsoft Bluetooth Notebook Mouse 5000] on f4:8c:50:fd:be:15
also: I'm not the only one. please see workaround: https://bugs.archlinux.org/task/55796
additional info: bt is included in the wifi card, which is: Intel Corporation Wireless 8260
*** Bug 1502179 has been marked as a duplicate of this bug. ***
Same here with 01:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a)
Same her with following card: $ lspci | grep -i network 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
Same here with following card: $ lspci | grep -i network 03:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
as I stated before, adding options: options iwlwifi bt_coex_active=0 to /etc/modprobe.d/iwlwifi.conf (you must create the file) fixes the issue. anyway with the previuos 4.12 this was not necessary, so maybe there is a regression in the module shipped with kernel 4.13
(In reply to Davide Corrado from comment #8) > as I stated before, adding options: > > options iwlwifi bt_coex_active=0 > > to /etc/modprobe.d/iwlwifi.conf (you must create the file) > > fixes the issue. anyway with the previuos 4.12 this was not necessary, so > maybe there is a regression in the module shipped with kernel 4.13 The workaround seems not work for me. I am using a ThinkPad X1 Tablet $ lspci |grep Network 04:00.0 Network controller: Intel Corporation Wireless 8260 (rev 3a) $ cat /sys/module/iwlwifi/parameters/bt_coex_active N My bt device is "BLUETOOTH HID v3.09 Keyboard [ThinkPad Compact Bluetooth Keyboard with TrackPoint]" I am on Fedora 27 with kernel 4.13.12-300.fc27.x86_64
I can confirm I have the same issue with Intel 8265 and Fedora 27. After researching the issue, it has been confirmed in the kernel's Bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=197147 The workaround does indeed. There is good news, the bluetooth team from Intel has identified the issue and have released a fix in the linux-firmware repo. I have tried the patched firmware and it does work. Please remember to remove/comment out the workaround fix in /etc/modprobe.d/iwlwifi.conf Fedora team, please review and considering releasing the updated linux-firmware package ASAP. This issue was particularly bad and has caused much frustration.
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.