Bug 1382424

Summary: can not turn bluetooth on
Product: [Fedora] Fedora Reporter: 747500
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: 747500, bugzilla, chhudson, gansalmon, ichavero, itamar, jonathan, kernel-maint, madhu.chinakonda, mchehab
Target Milestone: ---Flags: jforbes: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-04-28 17:28:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
dmesg none

Description 747500 2016-10-06 16:12:21 UTC
Created attachment 1207976 [details]
dmesg

# lsusb
...
Bus 001 Device 004: ID 8087:0a2b Intel Corp. 
...


m/b: Gigabyte Technology Co., Ltd. B150N Phoenix-WIFI-CF


# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)


# hciconfig hci0
hci0:	Type: Primary  Bus: USB
	BD Address: 00:00:00:00:00:00  ACL MTU: 0:0  SCO MTU: 0:0
	DOWN 
	RX bytes:0 acl:0 sco:0 events:0 errors:0
	TX bytes:6 acl:0 sco:0 commands:2 errors:0


# dmesg | grep -i iwl
[    3.926190] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[    3.933378] iwlwifi 0000:02:00.0: Unsupported splx structure
[    3.941679] iwlwifi 0000:02:00.0: loaded firmware version 21.302800.0 op_mode iwlmvm
[    3.994076] iwlwifi 0000:02:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[    3.996107] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    3.997472] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    4.140445] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[    4.163354] iwlwifi 0000:02:00.0 wlp2s0: renamed from wlan0
[    4.720393] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    4.722874] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    4.861152] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled
[    4.862045] iwlwifi 0000:02:00.0: L1 Disabled - LTR Enabled


# dmesg | grep -i blue
[    3.769032] Bluetooth: Core ver 2.21
[    3.770146] Bluetooth: HCI device and connection manager initialized
[    3.770148] Bluetooth: HCI socket layer initialized
[    3.770150] Bluetooth: L2CAP socket layer initialized
[    3.770154] Bluetooth: SCO socket layer initialized
[    3.804435] Bluetooth: HCI UART driver ver 2.3
[    3.805197] Bluetooth: HCI UART protocol H4 registered
[    3.805962] Bluetooth: HCI UART protocol BCSP registered
[    3.806735] Bluetooth: HCI UART protocol LL registered
[    3.807493] Bluetooth: HCI UART protocol ATH3K registered
[    3.808240] Bluetooth: HCI UART protocol Three-wire (H5) registered
[    3.812446] Bluetooth: HCI UART protocol Intel registered
[    3.813273] Bluetooth: HCI UART protocol BCM registered
[    3.813995] Bluetooth: HCI UART protocol QCA registered
[    3.814698] Bluetooth: HCI UART protocol AG6XX registered
[    4.497332] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[    4.498109] Bluetooth: BNEP filters: protocol multicast
[    4.498889] Bluetooth: BNEP socket layer initialized
[    5.804182] Bluetooth: hci0: Reading Intel version information failed (-110)
[    5.805204] Bluetooth: hci0 command tx timeout
[ 1004.068826] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 1004.074621] Bluetooth: hci0 command tx timeout

Comment 1 Bastien Nocera 2016-10-10 11:50:23 UTC
Not a gnome-bluetooth problem.

Comment 2 747500 2016-10-21 15:37:53 UTC
after long full poweroff it starts working till next reboot

Comment 3 747500 2016-10-21 15:57:03 UTC
(In reply to 747500 from comment #2)
> after long full poweroff it starts working till next reboot
BIOS' "Fast Boot"

Comment 4 George Sapkin 2016-11-18 21:14:17 UTC
Same issue and same symptoms here on F25 x64 down to needing a long poweroff for Bluetooth to start working again. I have a different BT adapter though.

# dmesg
[   22.201160] usb 1-1.8: new full-speed USB device number 7 using ehci-pci
[   22.281070] usb 1-1.8: New USB device found, idVendor=13d3, idProduct=3375
[   22.281073] usb 1-1.8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[   22.281075] usb 1-1.8: Product: Bluetooth USB Host Controller
[   22.281076] usb 1-1.8: Manufacturer: Atheros Communications
[   22.281078] usb 1-1.8: SerialNumber: Alaska Day 2006

Comment 5 Justin M. Forbes 2017-04-11 14:50:59 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 6 Justin M. Forbes 2017-04-28 17:28:31 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.