Bug 1383564 - Bluetooth: hci0 command 0xfc09 tx timeout [NEEDINFO]
Summary: Bluetooth: hci0 command 0xfc09 tx timeout
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kernel Maintainer List
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-11 05:10 UTC by Zhang Yi
Modified: 2017-04-28 17:19 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-04-28 17:19:17 UTC
Type: Bug
jforbes: needinfo?


Attachments (Terms of Use)
dmesg (63.55 KB, text/plain)
2016-10-11 05:10 UTC, Zhang Yi
no flags Details

Description Zhang Yi 2016-10-11 05:10:33 UTC
Created attachment 1209014 [details]
dmesg

Description of problem:
Bluetooth: hci0 command 0xfc09 tx timeout

Got this error log after system boot up, the hardware is Thinkpad X1 Carbon laptop

Version-Release number of selected component (if applicable):
4.7.3-200.fc24.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Detailed log pls check the attached file

[    6.753564] Bluetooth: hci0 command 0xfc09 tx timeout
[    9.165631] e1000e: enp0s31f6 NIC Link is Up 1000 Mbps Full Duplex, Flow Control: None
[    9.165668] IPv6: ADDRCONF(NETDEV_CHANGE): enp0s31f6: link becomes ready
[   10.480681] wlp4s0: authenticate with 00:f2:8b:e0:ca:3e
[   10.490862] wlp4s0: send auth to 00:f2:8b:e0:ca:3e (try 1/3)
[   10.495287] wlp4s0: authenticated
[   10.496183] wlp4s0: associate with 00:f2:8b:e0:ca:3e (try 1/3)
[   10.497441] wlp4s0: RX AssocResp from 00:f2:8b:e0:ca:3e (capab=0x111 status=0 aid=22)
[   10.498815] wlp4s0: associated
[   10.498850] IPv6: ADDRCONF(NETDEV_CHANGE): wlp4s0: link becomes ready
[   10.557763] wlp4s0: Limiting TX power to 10 dBm as advertised by 00:f2:8b:e0:ca:3e
[   14.750887] Bluetooth: hci0: Failed to send firmware data (-110)
[   35.043882] fuse init (API version 7.25)
[   38.854557] FAT-fs (mmcblk0): Volume was not properly unmounted. Some data may be corrupt. Please run fsck.
[   38.861024] EXT4-fs (sdb1): mounted filesystem with ordered data mode. Opts: (null)
[   83.298336] usb 1-7: new full-speed USB device number 7 using xhci_hcd
[   83.464323] usb 1-7: New USB device found, idVendor=8087, idProduct=0a2b
[   83.464331] usb 1-7: New USB device strings: Mfr=0, Product=0, SerialNumber=0
[   83.467796] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[   83.474846] Bluetooth: hci0: Device revision is 5
[   83.474853] Bluetooth: hci0: Secure boot is enabled
[   83.474856] Bluetooth: hci0: OTP lock is enabled
[   83.474858] Bluetooth: hci0: API lock is enabled
[   83.474860] Bluetooth: hci0: Debug lock is disabled
[   83.474864] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[   83.475756] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[   85.060587] Bluetooth: hci0: Waiting for firmware download to complete
[   85.061579] Bluetooth: hci0: Firmware loaded in 1557765 usecs
[   85.061623] Bluetooth: hci0: Waiting for device to boot
[   85.074641] Bluetooth: hci0: Device booted in 12720 usecs
[   85.075020] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[   85.078671] Bluetooth: hci0: Applying Intel DDC parameters completed
[   85.079666] Bluetooth: hci0: Setting Intel event mask failed (-16)
[   85.152765] Bluetooth: RFCOMM TTY layer initialized
[   85.152784] Bluetooth: RFCOMM socket layer initialized
[   85.152964] Bluetooth: RFCOMM ver 1.11

Comment 1 Kevin Kofler 2016-10-11 09:22:30 UTC
This has nothing whatsoever to do with kbluetooth, the old KDE Bluetooth applet that is not even in Fedora anymore (replaced with BlueDevil years ago).

Comment 2 Justin M. Forbes 2017-04-11 14:45:57 UTC
*********** MASS BUG UPDATE **************

We apologize for the inconvenience.  There are 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 24 kernel bugs.

Fedora 25 has now been rebased to 4.10.9-100.fc24.  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 26, and are still experiencing this issue, please change the version to Fedora 26.

If you experience different issues, please open a new bug report for those.

Comment 3 Justin M. Forbes 2017-04-28 17:19:17 UTC
*********** MASS BUG UPDATE **************
This bug is being closed with INSUFFICIENT_DATA as there has not been a response in 2 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.


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