[Solved] Bluetooth down and hciconfig hci0 up timeout

rlevArch · 2013-10-14 19:54:34

Hello,

I don't normally use bluetooth on my computer, but decided to give it a try today to get it working with my bluetooth headphones. It worked like a charm, but after I rebooted my computer I haven't been able to access my bluetooth card at all.

In particular, on boot I get this error. (The last two messages pop up at my login shell)

$ dmesg | grep Blue                                                                                                                                                                                                                        
[    5.776516] Bluetooth: Core ver 2.16
[    5.776533] Bluetooth: HCI device and connection manager initialized
[    5.776540] Bluetooth: HCI socket layer initialized
[    5.776543] Bluetooth: L2CAP socket layer initialized
[    5.776547] Bluetooth: SCO socket layer initialized
[    7.844683] Bluetooth: hci0 command 0x0c03 tx timeout
[   15.838488] Bluetooth: hci0 sending initial HCI reset command failed (-110)

I've tried googling the error codes and haven't come up with anything that works. Most suggestions are to make sure the device is up. Mine says it is down, but any commands sent to bring it up timeout.

$ hciconfig -a hci0                                                                                                                                                                                                                        
hci0:   Type: BR/EDR  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:12 acl:0 sco:0 commands:4 errors:0

And when I try to bring it up:

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

Here is some other possibly relevant information:

$ sc status bluetooth                                                                                                                                                                                                                      
bluetooth.service - Bluetooth service
   Loaded: loaded (/usr/lib/systemd/system/bluetooth.service; enabled)
   Active: active (running) since Mon 2013-10-14 22:00:06 IDT; 47min ago
     Docs: man:bluetoothd(8)
 Main PID: 3404 (bluetoothd)
   Status: "Running"
   CGroup: /system.slice/bluetooth.service
           └─3404 /usr/lib/bluetooth/bluetoothd

Oct 14 22:00:06 pollux bluetoothd[3404]: Bluetooth daemon 5.9
Oct 14 22:00:06 pollux systemd[1]: Started Bluetooth service.
Oct 14 22:00:06 pollux bluetoothd[3404]: Starting SDP server
Oct 14 22:00:06 pollux bluetoothd[3404]: Bluetooth management interface 1.3 initialized

$ pacman -Qs blue                                                                                                                                                                                                                          
local/bluez 5.9-1
    Daemons for the bluetooth protocol stack
local/bluez-libs 5.9-1
    Deprecated libraries for the bluetooth protocol stack
local/bluez-utils 5.9-1
    Development and debugging utilities for the bluetooth protocol stack
local/gnome-bluetooth 3.10.0-1
    The GNOME Bluetooth Subsystem
local/sbc 1.1-1
    Bluetooth Subband Codec (SBC) library

$ lsmod | grep -i blue                                                                                                                                                                                                                     
bluetooth             308340  7 bnep,btusb
rfkill                 15698  4 cfg80211,bluetooth
crc16                   1359  2 ext4,bluetooth

$ rfkill list                                                                                                                                                                                                                              
0: phy0: Wireless LAN
        Soft blocked: no
        Hard blocked: no
1: hci0: Bluetooth
        Soft blocked: no
        Hard blocked: no

$ lspci                                                                                                                                                                                                                                    
00:00.0 Host bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor DRAM Controller (rev 06)
00:01.0 PCI bridge: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor PCI Express x16 Controller (rev 06)
00:02.0 VGA compatible controller: Intel Corporation 4th Gen Core Processor Integrated Graphics Controller (rev 06)
00:03.0 Audio device: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller (rev 06)
00:14.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI (rev 04)
00:16.0 Communication controller: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 (rev 04)
00:1a.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 (rev 04)
00:1b.0 Audio device: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller (rev 04)
00:1c.0 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 (rev d4)
00:1c.2 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #3 (rev d4)
00:1c.3 PCI bridge: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 (rev d4)
00:1d.0 USB controller: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 (rev 04)
00:1f.0 ISA bridge: Intel Corporation HM86 Express LPC Controller (rev 04)
00:1f.2 SATA controller: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] (rev 04)
00:1f.3 SMBus: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller (rev 04)
01:00.0 3D controller: NVIDIA Corporation GK107M [GeForce GT 750M] (rev a1)
03:00.0 Network controller: Intel Corporation Wireless 7260 (rev 63)
04:00.0 Unassigned class [ff00]: Realtek Semiconductor Co., Ltd. Device 5289 (rev 01)
04:00.2 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168 PCI Express Gigabit Ethernet controller (rev 0a)

The device itself is embedded in my Intel Corporation Wireless 7260 card. It's not a separate dongle. Please let me know if you any other information is needed. Thank you!

Last edited by rlevArch (2013-10-20 12:08:47)

rlevArch · 2013-10-14 19:59:14

The thing that gets me is that it was WORKING perfectly for a good few hours -- and now it's completely unresponsive. I'd be really happy if it would just show me some signs of life!

I also thought I'd show a couple more bits of output:

# bluetoothctl -a                                                                                                                                                                                                                     
Agent registered
[bluetooth]# show
No default controller available

and

$ hcitool dev                                                                                                                                                                                                                              
Devices:

rlevArch · 2013-10-20 12:10:34

A few restarts later it started working again.

I think I need to have it completely shut off for a while instead of just doing a straight reboot.

If I shutdown my computer without first typing "power off" in bluetoothctl, I get locked out again unless I shut off and then turn on my computer again.

I'm still not 100% on whether this is the actual problem, and it seems finnicky, but I can get it to work now, which is all I was hoping for.

jsrobson10 · 2019-08-14 03:00:19

This sounds like a similar issue to my issue on Pop OS. It sometimes works, sometimes doesn't. I think it might be a hardware issue on my system, because the same thing is happening with the WiFi, and it seems to be problematic when I'm moving my laptop a-lot. Does the same thing happen with the WiFi? Are there periods of time that it works well/doesn't work at all? You could try debugging it by booting with a live Linux USB to see if it works/doesn't work there, but only assuming it used to work in the live USB/CD.

Here's some command outputs:

[bluetooth]# show
No default controller available

josua@pop-os:~$ sudo service bluetooth status 
● bluetooth.service - Bluetooth service
   Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor preset: enabled)
   Active: active (running) since Wed 2019-08-14 12:30:11 AEST; 5s ago
     Docs: man:bluetoothd(8)
 Main PID: 14057 (bluetoothd)
   Status: "Running"
    Tasks: 1 (limit: 4915)
   Memory: 988.0K
   CGroup: /system.slice/bluetooth.service
           └─14057 /usr/lib/bluetooth/bluetoothd

Aug 14 12:30:11 pop-os systemd[1]: Starting Bluetooth service...
Aug 14 12:30:11 pop-os bluetoothd[14057]: Bluetooth daemon 5.50
Aug 14 12:30:11 pop-os systemd[1]: Started Bluetooth service.
Aug 14 12:30:11 pop-os bluetoothd[14057]: Starting SDP server
Aug 14 12:30:11 pop-os bluetoothd[14057]: Bluetooth management interface 1.14 initialized
Aug 14 12:30:11 pop-os bluetoothd[14057]: Endpoint registered: sender=:1.326 path=/MediaEndpoint/A2DPSource
Aug 14 12:30:11 pop-os bluetoothd[14057]: Endpoint registered: sender=:1.326 path=/MediaEndpoint/A2DPSink
Aug 14 12:30:14 pop-os bluetoothd[14057]: Loading LTKs timed out for hci0

josua@pop-os:~$ hciconfig hci0
Can't get device info: No such device

rharter · 2021-02-04 17:27:47

I have been running into the same issue on Pop_OS! 20.10. I've found a Stack Exchange answer that seems to offer reasonable temporary relief without restarting, and can hopefully help lead to a more permanent solution. I also wrote about my detailed investigation on the Pop_OS! subreddit, in case that's helpful.

The long and short of it is in the btusb kernel module:

hciconfig hci0 down
rmmod btusb
modprobe btusb
hciconfig hci0 up

That seems to resolve the issue for me, at least at this 30 minute mark after having done it.

nullpointer13 · 2022-10-20 04:04:34

I had the same problem, reading here i solved my problem.

[ 4.666945] Bluetooth: hci0: command 0xfc05 tx timeout
[ 4.666961] Bluetooth: hci0: Reading Intel version command failed (-110)

this did the job:

rmmod btusb
modprobe btusb

Arch Linux

#1 2013-10-14 19:54:34

[Solved] Bluetooth down and hciconfig hci0 up timeout

#2 2013-10-14 19:59:14

Re: [Solved] Bluetooth down and hciconfig hci0 up timeout

#3 2013-10-20 12:10:34

Re: [Solved] Bluetooth down and hciconfig hci0 up timeout

#4 2019-08-14 03:00:19

Re: [Solved] Bluetooth down and hciconfig hci0 up timeout

#5 2021-02-04 17:27:47

Re: [Solved] Bluetooth down and hciconfig hci0 up timeout

#6 2022-10-20 04:04:34

Re: [Solved] Bluetooth down and hciconfig hci0 up timeout

Board footer