Bug 1323833 - Bluetooth module in Intel 8260 fails to init
Summary: Bluetooth module in Intel 8260 fails to init
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 23
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-04 21:41 UTC by Igor
Modified: 2020-11-12 22:17 UTC (History)
10 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2016-10-26 16:49:42 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
screenshot of bluetooth settings panel when broken (19.00 KB, image/png)
2016-04-04 21:46 UTC, Igor
no flags Details

Description Igor 2016-04-04 21:41:48 UTC
Description of problem:
After upgrading to kernel 4.4 (4.4.2-301.fc23.x86_64), Bluetooth is not working upon first bootup. I see this message in dmesg:
"Bluetooth: hci0: Failed to send firmware header (-38)"

Version-Release number of selected component (if applicable):
Latest F23 kernel (4.4.2-301)


How reproducible:
Very

Steps to Reproduce:
1. Boot into kernel 4.4.2
2. Try to use bluetooth
3.

Actual results:
Bluetooth does not work.

Expected results:
Bluetooth should work.

Additional info:
As an easy workaround, I run `rmmod btusb` and then `modprobe btusb` and bluetooth starts working agin!

Comment 1 Igor 2016-04-04 21:46:39 UTC
Created attachment 1143464 [details]
screenshot of bluetooth settings panel when broken

this is what bluetooth settings look like before i do the rmmod/modprobe trick.

Comment 2 Igor 2016-04-04 21:51:34 UTC
oops sorry, this is actually on the following kernel:
[root@thedude igor47]# uname -a
Linux thedude 4.4.6-300.fc23.x86_64 #1 SMP Wed Mar 16 22:10:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

here is the relevant dmesg section from bootup:

[   13.480100] Bluetooth: Core ver 2.21
[   13.480118] NET: Registered protocol family 31
[   13.480120] Bluetooth: HCI device and connection manager initialized
[   13.480124] Bluetooth: HCI socket layer initialized
[   13.480127] Bluetooth: L2CAP socket layer initialized
[   13.480135] Bluetooth: SCO socket layer initialized
[   13.487353] media: Linux media interface: v0.10
[   13.489232] Netfilter messages via NETLINK v0.30.
[   13.496371] ip_set: protocol 6
[   13.504223] Linux video capture interface: v2.00
[   13.567216] usbcore: registered new interface driver btusb
[   13.570799] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   13.576244] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   13.576364] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   13.576636] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   13.576813] Bluetooth: hci0: Device revision is 5
[   13.576817] Bluetooth: hci0: Secure boot is enabled
[   13.576819] Bluetooth: hci0: OTP lock is enabled
[   13.576821] Bluetooth: hci0: API lock is enabled
[   13.576823] Bluetooth: hci0: Debug lock is disabled
[   13.576825] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   13.577269] iwlwifi 0000:02:00.0: can't access the RSA semaphore it is write protected
[   13.580771] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   13.582178] Bluetooth: hci0: Failed to send firmware signature (-38)
[   13.606948] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   13.606952] Bluetooth: BNEP filters: protocol multicast
[   13.606956] Bluetooth: BNEP socket layer initialized


after i rmmod/modprobe:
[  402.222373] usbcore: deregistering interface driver btusb
[  404.612547] usbcore: registered new interface driver btusb
[  404.613685] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[  404.619360] Bluetooth: hci0: Device revision is 5
[  404.619363] Bluetooth: hci0: Secure boot is enabled
[  404.619365] Bluetooth: hci0: OTP lock is enabled
[  404.619366] Bluetooth: hci0: API lock is enabled
[  404.619368] Bluetooth: hci0: Debug lock is disabled
[  404.619369] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  404.619616] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[  405.975464] Bluetooth: hci0: Waiting for firmware download to complete
[  405.976220] Bluetooth: hci0: Firmware loaded in 1331720 usecs
[  405.976292] Bluetooth: hci0: Waiting for device to boot
[  405.988262] Bluetooth: hci0: Device booted in 11715 usecs
[  405.989253] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[  405.991289] Bluetooth: hci0: Applying Intel DDC parameters completed
[  405.992295] Bluetooth: hci0: Setting Intel event mask failed (-16)
[  406.051859] Bluetooth: RFCOMM TTY layer initialized
[  406.051866] Bluetooth: RFCOMM socket layer initialized
[  406.051871] Bluetooth: RFCOMM ver 1.11

Comment 3 Igor 2016-04-04 22:09:10 UTC
sorry for all of the corrections and email noise. upon further testing, i see that this problem actually persists under kernel 4.3.3 as well!

the problem actually only occurs on cold bootup from shutdown; a warm reboot is fine under both kernel versions i tried. under this older kernel:

[igor47@thedude ~]$ uname -a
Linux thedude 4.3.3-303.fc23.x86_64 #1 SMP Tue Jan 19 18:31:55 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux

i see the following dmesg output:

[   10.686630] Bluetooth: Core ver 2.20
[   10.686649] NET: Registered protocol family 31
[   10.686651] Bluetooth: HCI device and connection manager initialized
[   10.686656] Bluetooth: HCI socket layer initialized
[   10.686658] Bluetooth: L2CAP socket layer initialized
[   10.686666] Bluetooth: SCO socket layer initialized
[   10.689366] media: Linux media interface: v0.10
[   10.705670] Linux video capture interface: v2.00
[   10.771431] usbcore: registered new interface driver btusb
[   10.771676] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   10.777709] Bluetooth: hci0: Device revision is 5
[   10.777712] Bluetooth: hci0: Secure boot is enabled
[   10.777713] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   10.780635] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   10.792169] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   10.792172] Bluetooth: BNEP filters: protocol multicast
[   10.792176] Bluetooth: BNEP socket layer initialized
[   10.798140] uvcvideo: Found UVC 1.00 device Integrated_Webcam_HD (0bda:5682)
[   10.807140] input: Integrated_Webcam_HD as /devices/pci0000:00/0000:00:14.0/usb1/1-5/1-5:1.0/input/input15
[   10.807222] usbcore: registered new interface driver uvcvideo
[   10.807224] USB Video Class driver (1.1.1)
[   10.856918] Netfilter messages via NETLINK v0.30.
[   10.862797] ip_set: protocol 6
[   10.944059] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   10.944205] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   10.944478] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   10.945036] iwlwifi 0000:02:00.0: can't access the RSA semaphore it is write protected
[   10.953110] Bluetooth: hci0: Failed to send firmware data (-38)

and this is what it looks like after rmmod/modprobe:

[  120.315242] usbcore: deregistering interface driver btusb
[  123.823288] usbcore: registered new interface driver btusb
[  123.824051] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[  123.830042] Bluetooth: hci0: Device revision is 5
[  123.830045] Bluetooth: hci0: Secure boot is enabled
[  123.830046] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[  123.830215] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[  125.183334] Bluetooth: hci0: Waiting for firmware download to complete
[  125.184329] Bluetooth: hci0: Firmware loaded in 1327723 usecs
[  125.184415] Bluetooth: hci0: Waiting for device to boot
[  125.196398] Bluetooth: hci0: Device booted in 11721 usecs
[  125.197398] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[  125.199490] Bluetooth: hci0: Applying Intel DDC parameters completed
[  125.257167] Bluetooth: RFCOMM TTY layer initialized
[  125.257178] Bluetooth: RFCOMM socket layer initialized
[  125.257183] Bluetooth: RFCOMM ver 1.11

after a warm reboot, here is what i see in dmesg:

[   12.732833] Bluetooth: Core ver 2.20
[   12.732851] NET: Registered protocol family 31
[   12.732853] Bluetooth: HCI device and connection manager initialized
[   12.732857] Bluetooth: HCI socket layer initialized
[   12.732860] Bluetooth: L2CAP socket layer initialized
[   12.732868] Bluetooth: SCO socket layer initialized
[   12.740691] media: Linux media interface: v0.10
[   12.760591] Linux video capture interface: v2.00
[   12.792339] IPv6: ADDRCONF(NETDEV_UP): wlp2s0: link is not ready
[   12.792459] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   12.792730] iwlwifi 0000:02:00.0: L1 Enabled - LTR Disabled
[   12.793240] iwlwifi 0000:02:00.0: can't access the RSA semaphore it is write protected
[   12.830452] usbcore: registered new interface driver btusb
[   12.830884] Bluetooth: hci0: Firmware revision 0.0 build 90 week 25 2015
[   12.847549] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   12.847552] Bluetooth: BNEP filters: protocol multicast
[   12.847556] Bluetooth: BNEP socket layer initialized

and everything works just fine without any rmmod/modprobe tricks.

Comment 4 Laura Abbott 2016-09-23 19:36:15 UTC
*********** MASS BUG UPDATE **************
 
We apologize for the inconvenience.  There is a large number of bugs to go through and several of them have gone stale.  Due to this, we are doing a mass bug update across all of the Fedora 23 kernel bugs.
 
Fedora 23 has now been rebased to 4.7.4-100.fc23.  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 have moved on to Fedora 24 or 25, and are still experiencing this issue, please change the version to Fedora 24 or 25.
 
If you experience different issues, please open a new bug report for those.

Comment 5 Laura Abbott 2016-10-26 16:49:42 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 4 weeks. If you are still experiencing this issue, please reopen and attach the relevant data from the latest kernel you are running and any data that might have been requested previously.

Comment 6 陳鐸元 2017-09-30 15:51:29 UTC
I'm having the same issue with Intel 8265.

kernel: F26(4.12.14-300.fc26.x86_64)

linux-firmware version: 20170828

Comment 7 DanMan 2020-11-12 22:17:46 UTC
Still having the same issue under Fedora 33 with kernel 5.8.18-300.fc33.x86_64

The error on boot is also "Failed to send firmware signature (-38)". Suggested workaround (rmmod, modprobe) still works, too.

Hardware is a Gigabyte GC-WB867D-I with an Intel 8260 chipset for both Wifi and Bluetooth. The latter is connected via USB, the former via PCIe.

What more information do you need?


Note You need to log in before you can comment on or make changes to this bug.