Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)

Bug #268502 reported by _oOMOo_ on 2008-09-10
746
This bug affects 126 people
Affects Status Importance Assigned to Milestone
Genesi EfikaMX Support Project
Undecided
Unassigned
Linux
In Progress
Medium
bluez (Debian)
Fix Released
Unknown
bluez (Ubuntu)
Undecided
Unassigned
Nominated for Hardy by Eddy
Nominated for Karmic by Fernando D.
Nominated for Lucid by Fernando D.
Intrepid
Undecided
Unassigned
Jaunty
Undecided
Unassigned
bluez-utils (Debian)
New
Unknown
linux (Fedora)
Fix Released
High
linux (Ubuntu)
Medium
Unassigned
Nominated for Hardy by Eddy
Nominated for Karmic by Fernando D.
Nominated for Lucid by Fernando D.
Intrepid
Medium
Unassigned
Jaunty
Medium
Brian Rogers

Bug Description

SRU justification:

Impact: A series of bluetooth dongles [1] do not work properly with the new
        btusb driver which replaced usb_hci. This has been fixed upstream
        (2.6.29-rc3). The required changes are all local to the btusb driver.

Fix: The following three patches are required to fix this (two as prerequisite
     and one for the actual fix). The fix deviates from upstream by the change
     of a version number and the missing resume part which does not exist for
     Intrepid nor Jaunty.

Test: Fix has been tested by bug reporters.

---

Bluetooth doesn't work for at least the following devices:
ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
ID 1131:1004 Integrated System Solution Corp. Bluetooth Device
ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
ID 0a5c:200a Broadcom Corp. Bluetooth dongle

They don't work properly with the newer btusb driver, which replaced hci_usb by default in 2.6.27. This hasn't been fixed upstream as of v2.6.29-rc3.

Original message below:

Association with Bluetooth works using kernel 2.6.26, since the updates to 2.6.27 (both -1 and -2) association fails. I can scan and see bluetooth devices but not pair.

Using my phone, I start the association process, the phone asks for a passkey, and in 2.6.26 the popup window appears normally allowing me to enter the passkey. In 2.6.27 the dialog box never appears.

If I use hcitool:

:~$ sudo hcitool cc 00:1B:59:96:A6:DD
:~$ sudo hcitool auth 00:1B:59:96:A6:DD
HCI authentication request failed: Connection timed out

the dialog box appears very very briefly then vanishes.

dmesg shows a couple of problems:

[25791.306170] btusb_intr_complete: hci0 urb ffff88004dd0fb40 failed to resubmit (19)
[25791.315446] btusb_send_frame: hci0 urb ffff880048542840 submission failed

and the syslog shows that there was an attempt to associate:

Sep 23 08:16:59 charlie hcid[5903]: link_key_request (sba=00:11:67:9C:59:B5, dba=00:1B:59:96:A6:DD)
Sep 23 08:16:59 charlie hcid[5903]: pin_code_request (sba=00:11:67:9C:59:B5, dba=00:1B:59:96:A6:DD)

_oOMOo_ (hermann-blaxhall) wrote :

Output of lsusb

:~$ lsusb
Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 148f:2573 Ralink Technology, Corp. RT2501USB Wireless Adapter
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Changed in linux:
assignee: nobody → ubuntu-kernel-team
importance: Undecided → Medium
status: New → Triaged
Luca Zorzi (lucazorzi91) wrote :

I had the same problem with Intrepid Alpha 5, then I tried to send a photo from my Nokia N70 to the PC (no problem with that), then tried to associate again my Bluetooth headset and it worked!
I use a D-Link DBT-120.

_oOMOo_ (hermann-blaxhall) wrote :

No change with 2.6.27-4

description: updated
_oOMOo_ (hermann-blaxhall) wrote :

Have clean installed Intrepid Beta, and updated now to 2.6.27-6, and the problem persists.

Danny Wood (danwood76) wrote :

I can confirm this bug with the same bluetooth controller.
I'm wondering if it is a specific bug with this controller?

danny@danny-laptop:~$ lsusb
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

Alexander Butenko (avb) wrote :

seems #281949 is a duplicate of this one but assigned to a wrong package.

Alexander Butenko (avb) wrote :

i have the same issue. Mine usb adapter is dlink dbt-122.

Here is a snip of dmesg:
[138209.665630] Bluetooth: Generic Bluetooth USB driver ver 0.3
[138209.666632] usbcore: registered new interface driver btusb
[138214.844410] hci_cmd_task: hci0 command tx timeout
[138219.848340] hci_cmd_task: hci0 command tx timeout
[138224.853676] hci_cmd_task: hci0 command tx timeout
[138229.856417] hci_cmd_task: hci0 command tx timeout
[138234.860719] hci_cmd_task: hci0 command tx timeout
[138239.960585] hci_cmd_task: hci0 command tx timeout
[138240.464277] bluetoothd[5133]: segfault at 3 ip b7e39938 sp bfb8fcc8 error 4 in libc-2.8.90.so[b7dc8000+158000]

# lsusb
..
Bus 004 Device 007: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter
..

Carlo (gentuser) wrote :

Same Problem:
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 0a5c:200a Broadcom Corp. Bluetooth dongle
Dmesg :
[ 55.092421] hci_cmd_task: hci0 command tx timeout
[ 60.096506] hci_cmd_task: hci0 command tx timeout
[ 65.100369] hci_cmd_task: hci0 command tx timeout
[ 70.104358] hci_cmd_task: hci0 command tx timeout
[ 75.108196] hci_cmd_task: hci0 command tx timeout
[ 80.112996] hci_cmd_task: hci0 command tx timeout

It works with regression of these package :
'bluez-utils_3.26-0ubuntu6_i386.deb'
'bluez-hcidump_1.40-0ubuntu1_i386.deb'
'bluez-cups_3.26-0ubuntu6_i386.deb'
'bluez-audio_3.26-0ubuntu6_i386.deb'
'bluetooth_3.26-0ubuntu6_all.deb'
No other solution found.

tielie (mike-tielie) wrote :

I confirm this as a bug Bus 004 Device 003: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

does not work on mine system to :-/

Intrepid with Linux 2.6.27-7

If I boot with old linux 2.6.26-* it works. So its probadly kernel problem. or maybe bluez related...

_oOMOo_ (hermann-blaxhall) wrote :

I have been able to pair (intermittently) from phone to computer using a different phone, an LG rather than a Sony Ericsson. The LG allows me to enter the passcode much more quickly than the Sony (which normally thinks for about 25 seconds before asking me to choose a passcode). Is this a timeout issue?

Having said that, even when paired I am still unable to browse files on the LG.

tielie (mike-tielie) wrote :

its not a time only a timerissue in the bluz stack its seems to be an KY-BT100 driver issue or/and the ehci/uhci_hsd as far as I could understand it when reading some mailinglists.

My other bt adapter ( 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)) works nicely.

psernetz (patrick-sernetz-com) wrote :

Same problem on my site.

 ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

It's a no name device which worked in hardy but not in intrepid.

It seems my problem is more severe...

I have 2 different bluetooth dongles (Kensington & Ambicom). They both used to work fine in Hardy, but all I'm showing is timeout errors since I upgraded to Ibex. I can't pair, I can't search devices, obex... Anything.

At first, the BT icon didn't even show, but after installing a few packages through Synaptic and rebooting, that problem went away.

Another weird thing is that the timeout errors occur within a second of attempting any kind of interaction with bluetoothd.

Let me know if you guys need any extra info, and I'll try to post it up ASAP.

Syl21 (sylvain-gargasson) wrote :

The same problem for me with the final 8.10 intrepid ibex and a D-Link DBT-122.

Blink green power and link and nothing more...

lsusb:
Bus 006 Device 003: ID 2001:f111 D-Link Corp. [hex] DBT-122 Bluetooth adapter

lsmod | grep bt:
btusb 21912 3
bluetooth 70820 15 btusb,rfcomm,sco,bnep,l2cap
usbcore 175376 8 btusb,snd_usb_audio,uvcvideo,snd_usb_lib,usbhid,ehci_hcd,uhci_hcd

If I plus and unplus my key I have a normal dmesg like:
[ 851.624013] usb 5-1: new full speed USB device using uhci_hcd and address 3
[ 851.857750] usb 5-1: configuration #1 chosen from 1 choice
[ 923.456037] usb 5-1: USB disconnect, address 3

but the first time I plus and unplug, I have it:
[ 359.864020] usb 6-1: new full speed USB device using uhci_hcd and address 3
[ 360.060177] usb 6-1: configuration #1 chosen from 1 choice
[ 365.196166] hci_cmd_task: hci0 command tx timeout
[ 370.200185] hci_cmd_task: hci0 command tx timeout
[ 375.204223] hci_cmd_task: hci0 command tx timeout
[ 380.208153] hci_cmd_task: hci0 command tx timeout
[ 385.212186] hci_cmd_task: hci0 command tx timeout
[ 390.216194] hci_cmd_task: hci0 command tx timeout
[ 437.128037] usb 6-1: USB disconnect, address 3
[ 437.129858] btusb_intr_complete: hci0 urb ffff88006289cd80 failed to resubmit (19)
[ 437.130126] btusb_send_frame: hci0 urb ffff880062522a80 submission failed
[ 437.130161] __ratelimit: 3 callbacks suppressed
[ 437.130164] bluetoothd[5470]: segfault at 100000007 ip 00007f165b228339 sp 00007fff64096490 error 4 in libc-2.8.90.so[7f165b1ae000+169000]

Thanks in advance...

Syl21 (sylvain-gargasson) wrote :

Suite of my post, I have forget my kernel "uname -a":
Linux syl21-desktop 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64 GNU/Linux

How as in other users my D-Link DBT-122 not work in 8.10 Untrepid Ibex Release.
--------------------
"uname -a":
Linux leolik-komp 2.6.27-7-generic #1 SMP Thu Oct 30 04:12:22 UTC 2008 x86_64 GNU/Linux

hara (harak-iitm) wrote :

I see this problem when I hibernate... It also vomits other errors as i have included a bug i opened
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/293115

olnabe (waspee) wrote :

I also have this problem with kernel 2.6.27.4.

hci_cmd_task: hci0 command tx timeout
btusb_intr_complete: hci0 urb failed to resubmit (19)

Things like that.

After replacing the bluetooth subsystem with the codes from 2.6.26.7
and recompiling the kernel, the problem is solved. My bluetooth mouse
works again on "2.6.27.4".

My adapter is a KY-BT100 one.

Stiff (stiff.ru) wrote :

I have the same problem. If i request authentification from my phone, it works. But i cant pair device from computer.
hcitool scan scans devices good, but i cant connect to phone via obex or rfcomm. sdptool outputs connetion timeout.
string from lsusb:

Bus 002 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

Syl21 (sylvain-gargasson) wrote :

We are lot of people having loosing our Bluetooth connection... Thanks in Advance.

Changed in linux:
status: Triaged → Confirmed
Krugger (krugger-gmail) wrote :

Same problem with 2 bluetooth adapters, this one is from my usb dongle:

Bus 001 Device 006: ID 1131:1004 Integrated System Solution Corp. Bluetooth Device

And the error on dmesg:

[ 235.132015] hci_cmd_task: hci0 command tx timeout

I can see (and pair) the devices, but any other activity fails.

Same here, seems another kernel regression....

kylea (kylea) wrote :

I can pair nearly at will - but what happens to me is that the bluetooth connection will not "stick". I have been getting intermittent syncing and file file transferring to work for two days then it stops for a 3 or 4 and then it will work for 8 hours and then stop.

Here is a log from the last week

1/12/2008 21:45 | kyle Amadio
      Nope that does not seem to make any difference.
      Can send files between my phone and wifes.

01/12/2008 21:37 | kyle Amadio
      Monday morning 1/12/2008 - went to work, started PC - interestingly the Dell Bluetooth switch was not on.
      Noticed this well after the PC had booted. Turned on the switch and the sync process and other Bluetooth functions worked.
     Have now returned home and 5 hours after leaving work. Bluetooth has stopped working.
     Will see if the Dell bluetooth switch being off make during the boot process makes any difference.

30/11/2008 21:03 | kyle Amadio
     Ok its Sunday 30th still not syncing - have tried a variety of things, resetting phone, re-pairing, restarting PC bluetooth.
     I can send images and music files between my 6233 and my wifes successfully, both ways.

29/11/2008 08:07 | kyle Amadio
    Shutdown - went to bed - 8 hours later - it works.
    Changed nothing on the phone

28/11/2008 22:48 | kyle Amadio
    Ok - did a shutdown and reboot. Syncing / Bluetooth stopped working.

28/11/2008 22:36 | kyle Amadio
       Well- went home and syncing is all good again.

28/11/2008 12:15 | kyle Amadio
      Syncing worked fine for two days - failed this morning (Fri 28th).

n0PxN0p (n0pxn0p) wrote :

Same problem, i tried 2 different bt usb-dongles (based on different chipsets), but no luck.
Everything works for me, when i start up with 2.6.24-21 stable kernel from array.org ^_^
_________________
root@gazenwagen:~# rfcomm connect 0
Can't connect RFCOMM socket: Operation now in progress

root@gazenwagen:~# hciconfig dev
hci0: Type: USB
BD Address: 00:11:67:C6:F0:6B ACL MTU: 1021:4 SCO MTU: 48:10
UP RUNNING
RX bytes:2180 acl:0 sco:0 events:85 errors:0
TX bytes:890 acl:0 sco:0 commands:70 errors:0

root@gazenwagen:~# dmesg|tail
[ 2876.984143] hci_cmd_task: hci0 command tx timeout
[ 4710.928544] usb 1-2: USB disconnect, address 5
[ 4710.928742] btusb_intr_complete: hci0 urb e4f5d200 failed to resubmit (19)
[ 4710.928742] btusb_bulk_complete: hci0 urb e4c30780 failed to resubmit (19)
[ 4710.929414] btusb_bulk_complete: hci0 urb e4c30b80 failed to resubmit (19)
[ 4710.940056] btusb_send_frame: hci0 urb e4ee4980 submission failed
[ 4710.952039] __set_isoc_interface: hci0 setting interface failed (19)
[ 4727.752273] usb 1-2: new full speed USB device using uhci_hcd and address 6
[ 4737.927583] usb 1-2: configuration #1 chosen from 1 choice
[ 4990.780188] hci_cmd_task: hci0 command tx timeout
_________________

BrowneR (chris-scotland) wrote :

I just built 2.6.28-rc7-git2 from kernel.org and I have the same problems with bluetooth so this is obviously not something that has been addressed upstream.

Is it worth reporting this upstream?

BrowneR (chris-scotland) wrote :

Bug 288613 seems related (https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/288613) and interestingly the reporter claims bluetooth worked fine in beta but not when the first intrepid RC was released. What changed kernel wise?

kylea (kylea) wrote :

Ok : here is what I think is going: (I have a Dell E6500 laptop)

IF I have my Bluetooth radio switch turned OFF during the Boot Up process and only turn it ON AFTER Gnome is fully loaded and all processes are finished THEN Bluetooth processes work.

Have proven this with repeated tests:

IF the Bluetooth radio switch is ON during the boot up then Bluetooth will not work.

SO what is going on - surely this is enough for you guys to make a search now. Can we change the load sequence of the Bluetooth daemon to load last ?

Jamie Lokier (jamie-shareable) wrote :

kylea, I usually boot with the Bluetooth radio off. It's USB internally and disconnected when I boot, then I switch it on after logging in.

I still have this pairing problem every time with 2.6.27 kernels.
So changing the load sequence wouldn't fix it.

The information we need may be to bisect between the last kernel which works reliably and the one after, trying it on someone's machine until the change which breaks it is identified. Alas I don't have the time for it, so I just run old kernels with Intrepid.

Carlo (gentuser) wrote :

In the same pc on Ubuntu with 2.6.27-7 bluez doesn't pair with any device, with gentoo 2.6.27-r1 bluez-3.36 it does...
I don't know is a kernel problem or what else, but with regression of bluez association works well

Carlo (gentuser) wrote :

Update: ubuntu kernel 2.6.27-10 doesn't solve my problem

n0PxN0p (n0pxn0p) wrote :

it doesn't solve my problem too )

New kernel @ Jaunty, 2.6.28 series fixes my problem.
Now I got my bluetooth headset working on Skype....finally.

Intrepid remains "unpreant" release for me, it was still fine with Hardy.

I too have just tried the Jaunty kernel.
I added this line to my apt/sources.list

deb http://gb.archive.ubuntu.com/ubuntu/ jaunty main restricted multiverse universe

and first of all just upgraded the bluez related packages to 4.21-0ubuntu1.

Now when I try to pair with my phone it immediately fails and gives an error message rather than timing out like before. I then downgraded these packages back to the intrepid version and installed the Jaunty kernel packages (2.6.28). Rebooted the new kernel. Bluetooth still wont work.

I then upgrade the bluez packages again and try to pair with my phone. Success - I am given a 4 digit password and enter this on my phone and it pairs correctly. I am however unable to do any file transfers or use my phone as an HID remote control or modem. So progress at least but still not fixed.

It seems to be a combination of factors related to bluez and the kernel as each one on its own didn't fix the problem however when they were both upgraded i was able to pair at least...

Tiago Silva (tiagosilva) wrote :

I tested file receiving/sending on my laptop (Compal FT00 VBI) with two Nokia mobile phones: N70 and 6600.
Sending files to the phones was fine. Receiving files doesn't work.

pseudolegolas (pseudolegolas) wrote :

same problem with me..............
have tried everything exept different kernel virsion
will do that today

comp is able to detect devices but cant connect

is some developer listening
SOS

SOS

SOS

Mike (farlo144) wrote :

This seems like a pretty bad bug for no one to look into. Is there a workaround yet? 8.10 released ages ago, and bluetooth is a pretty standard technology. Is someone going to look into why this broke between 8.04 and 8.10? Seems like a lot of stuff broke in 64bit 8.10.

kylea (kylea) wrote :

I don't get - I have paid for support and still cannot get a sensible answer on this.

Just another reason why MS will keep its market share. How can we always be moving towards a new version when the basics don;t work on the majority of the hardware out there.

This behaviour is as bad - in fact worse than MS as the Linux community spends its time rightly bagging MS but then we do the same thing.

I just don't get it, can some of the zealots please explain what is going on here?

Vadim Peretokin (vperetokin) wrote :

No - please keep the bug report on topic. If you paid for Ubuntu commercial support, please contact them - however support implies solving user issues most likely. (at least, the contract that came with ubuntu on my laptop did).

Per a decision made by the Ubuntu Kernel Team, bugs will longer be assigned to the ubuntu-kernel-team in Launchpad as part of the bug triage process. The ubuntu-kernel-team is being unassigned from this bug report. Refer to https://wiki.ubuntu.com/KernelTeamBugPolicies for more information. Thanks.

What does the comment above actually mean then? Does this mean this major bug is not going to be looked at any further? Or assigned to another team? Who should it be assigned to? This is a major flaw and causes extreme disruption particularly to users who rely on services such as calendar/event syncing.

Changed in linux:
status: Unknown → In Progress
description: updated
Changed in linux:
assignee: nobody → brian-rogers
description: updated
Changed in linux:
status: Confirmed → In Progress
Stefan Bader (smb) on 2009-04-01
Changed in linux:
assignee: nobody → stefan-bader-canonical
importance: Undecided → Medium
status: New → Fix Committed
status: In Progress → Fix Committed
description: updated
Changed in linux (Ubuntu Jaunty):
status: Fix Committed → Fix Released
Changed in debian:
status: Unknown → New
Changed in linux (Ubuntu Intrepid):
status: Fix Committed → Confirmed
Changed in linux (Ubuntu Jaunty):
status: Fix Released → Confirmed
Changed in linux (Ubuntu):
status: Fix Released → Confirmed
Changed in linux (Ubuntu Jaunty):
status: Confirmed → Fix Released
Changed in linux (Ubuntu Intrepid):
status: Confirmed → Fix Committed
Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Changed in bluez (Ubuntu):
status: New → Invalid
Changed in bluez (Ubuntu Intrepid):
status: New → Invalid
Changed in bluez (Ubuntu Jaunty):
status: New → Invalid
maximi89 (maximi89) on 2009-05-22
affects: debian → bluez-utils (Debian)
Changed in bluez-utils (Debian):
status: New → Unknown
Changed in bluez (Debian):
status: Unknown → New
Changed in bluez-utils (Debian):
status: Unknown → New
Martin Pitt (pitti) on 2009-06-05
tags: added: verification-needed
Steve Beattie (sbeattie) on 2009-06-16
tags: added: hw-specific
Changed in bluez-utils (Debian):
status: New → Fix Committed
Changed in bluez (Debian):
status: New → Fix Committed
Philip (hallo9999) on 2009-08-16
Changed in linux (Ubuntu Jaunty):
status: Fix Released → Fix Committed
status: Fix Committed → New
Changed in linux (Ubuntu Jaunty):
status: New → Fix Released
273 comments hidden view all 353 comments

Thanks for taking time to review this bug.

I'm in the process of installing a box with F12 Alpha, I'll have new comments about this bug as soon as I can update it and groupinstall gnome desktop.

Also works with Kensington model #33348 dongle, id 047d:105e

I have the same problem with 2.6.29.6-217.2.16.fc11.x86_64. And a very similar bluetooth dongle.

If more information is needed just ask for it.

Thanks in advance.

(In reply to comment #7)
> I have the same problem with 2.6.29.6-217.2.16.fc11.x86_64. And a very similar
> bluetooth dongle.
>
> If more information is needed just ask for it.
>
> Thanks in advance.

Just add it is a:

Bus 002 Device 005: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Running Fedora 12 Alpha updated till today:

2.6.31-0.204.rc9.fc12.i686.PAE

bluez-libs-4.52-1.fc12.i686
bluez-cups-4.52-1.fc12.i686
gnome-bluetooth-2.27.90-2.fc12.i686
gnome-bluetooth-libs-2.27.90-2.fc12.i686
bluez-4.52-1.fc12.i686

[root@utopia ~]# hciconfig -a
hci0: Type: USB
 BD Address: 00:1F:81:00:02:50 ACL MTU: 1021:4 SCO MTU: 180:1
 UP RUNNING PSCAN
 RX bytes:972 acl:0 sco:0 events:28 errors:0
 TX bytes:361 acl:0 sco:0 commands:29 errors:2
 Features: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

Sep 7 21:07:35 utopia kernel: hci_cmd_task: hci0 command tx timeout

lsusb:
Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Regarding the last error message from hciconfig, Can't read local name on hci0:, I tried this:

[root@utopia ~]# hciconfig hci0 name utopia
Can't change local name on hci0: Connection timed out (110)

I tried some hciconfig options:

[root@utopia ~]# hciconfig hci0 down

Prompt resumes, seems down.

[root@utopia ~]# hciconfig hci0 up

Prompt doesn't resume. Ctrl-C or Ctrl-Z doesn't work. Kill -9 doesn't work either. /var/log/messages says this:

Sep 7 21:21:33 utopia bluetoothd[1062]: HCI dev 0 down
Sep 7 21:21:33 utopia bluetoothd[1062]: Adapter /org/bluez/1059/hci0 has been disabled
Sep 7 21:21:33 utopia bluetoothd[1062]: Stopping security manager 0
Sep 7 21:21:42 utopia kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 2
Sep 7 21:21:42 utopia kernel: btusb 4-2:1.0: no reset_resume for driver btusb?
Sep 7 21:21:42 utopia kernel: btusb 4-2:1.1: no reset_resume for driver btusb?

More hciconfig options:

[root@utopia ~]# hciconfig hci0 reset
[root@utopia ~]# hciconfig -a
hci0: Type: USB
 BD Address: 00:1F:81:00:02:50 ACL MTU: 1021:4 SCO MTU: 180:1
 UP RUNNING PSCAN
 RX bytes:2224 acl:0 sco:0 events:61 errors:0
 TX bytes:733 acl:0 sco:0 commands:59 errors:2
 Features: 0xff 0x3e 0x0d 0x76 0x80 0x01 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT
 Name: 'Accel-OB2'
 Class: 0x4a0104
 Service Classes: Networking, Capturing, Telephony
 Device Class: Computer, Desktop workstation
 HCI Ver: 2.0 (0x3) HCI Rev: 0x3 LMP Ver: 2.0 (0x3) LMP Subver: 0x3
 Manufacturer: Cambridge Silicon Radio (10)

After the hciconfig reset, this adaptor has never stopped working. Do I really have to issue hciconfig hci0 reset each boot for bluetooth to work? Is this still a kernel related problem?

Changed in linux (Ubuntu Intrepid):
status: Fix Committed → Fix Released

Last day update solved the problem. Bluetooth is working now.

Changed in bluez (Debian):
status: Fix Committed → New
Changed in bluez-utils (Debian):
status: Fix Committed → New

Tested with Fedora 12 Beta and is working for my bluetooth dongle now.

I recommend anyone previously getting the "hci_cmd_task: hci0 command tx timeout" give the live cd Beta a shot.

lively (doratheexplorer) on 2009-11-03
Changed in linux (Ubuntu Jaunty):
status: Fix Released → Confirmed
status: Confirmed → Fix Released

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

tags: added: iso-testing

I still hit this bug. I'm running F12 fully updated till today.

I get this in /var/log/messages upon inserting the bluetooth dongle:

Jan 6 15:52:34 desktop kernel: usb 4-1: new full speed USB device using uhci_hcd and address 6
Jan 6 15:52:34 desktop kernel: usb 4-1: New USB device found, idVendor=0a12, idProduct=0001
Jan 6 15:52:34 desktop kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Jan 6 15:52:34 desktop kernel: usb 4-1: configuration #1 chosen from 1 choice
Jan 6 15:52:34 desktop bluetoothd[687]: HCI dev 0 registered
Jan 6 15:52:34 desktop bluetoothd[687]: HCI dev 0 up
Jan 6 15:52:34 desktop bluetoothd[687]: Starting security manager 0
Jan 6 15:52:39 desktop bluetoothd[687]: Can't read version info for /org/bluez/686/hci0: Connection timed out (110)
Jan 6 15:52:50 desktop bluetoothd[687]: bridge pan0 removed
Jan 6 15:52:50 desktop bluetoothd[687]: Stopping SDP server
Jan 6 15:52:50 desktop bluetoothd[687]: Exit
Jan 6 15:52:50 desktop obex-data-server: sdp_send_req_w4_rsp: Error sending data:Broken pipe
Jan 6 15:52:50 desktop obex-data-server: sdp_send_req_w4_rsp: Error sending data:Broken pipe

Changed in bluez (Ubuntu Jaunty):
status: Invalid → Fix Committed
Steve Langasek (vorlon) on 2010-01-21
Changed in bluez (Ubuntu Jaunty):
status: Fix Committed → Invalid
Stefan Bader (smb) on 2010-02-11
Changed in linux (Ubuntu Intrepid):
assignee: Stefan Bader (stefan-bader-canonical) → nobody

Removing myself from CC because works-for-me.

KeithG (grider-4) on 2010-03-27
Changed in linux (Ubuntu):
status: Fix Released → Fix Committed
Steve Langasek (vorlon) on 2010-03-27
Changed in linux (Ubuntu):
status: Fix Committed → Fix Released
Changed in linux (Ubuntu):
assignee: Brian Rogers (brian-rogers) → nobody
Download full text (3.1 KiB)

I hit very similar problem. I cannot enable my usb bluetooth adapter, it's visible in lsusb:

...
Bus 004 Device 002: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter
...

hciconfig:
hci0: Type: 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:0 acl:0 sco:0 commands:4 errors:0
==============
Here's how it looks in /var/log/messages

Apr 18 14:06:59 moj kernel: Bluetooth: Core ver 2.15
Apr 18 14:06:59 moj kernel: NET: Registered protocol family 31
Apr 18 14:06:59 moj kernel: Bluetooth: HCI device and connection manager initialized
Apr 18 14:06:59 moj kernel: Bluetooth: HCI socket layer initialized
Apr 18 14:07:02 moj kernel: usb 1-6: USB disconnect, address 3
Apr 18 14:07:06 moj kernel: usb 4-2: new full speed USB device using uhci_hcd and address 2
Apr 18 14:07:16 moj kernel: usb 4-2: New USB device found, idVendor=1131, idProduct=1001
Apr 18 14:07:16 moj kernel: usb 4-2: New USB device strings: Mfr=1, Product=2, SerialNumber=0
Apr 18 14:07:16 moj kernel: usb 4-2: Product: ISSCBTA
Apr 18 14:07:16 moj kernel: usb 4-2: configuration #1 chosen from 1 choice
Apr 18 14:07:16 moj kernel: Bluetooth: Generic Bluetooth USB driver ver 0.6
Apr 18 14:07:16 moj kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 2
Apr 18 14:07:16 moj kernel: btusb 4-2:1.0: no reset_resume for driver btusb?
Apr 18 14:07:16 moj kernel: btusb 4-2:1.1: no reset_resume for driver btusb?
Apr 18 14:07:16 moj kernel: usbcore: registered new interface driver btusb
Apr 18 14:07:17 moj bluetoothd[2811]: Bluetooth daemon 4.58
Apr 18 14:07:17 moj bluetoothd[2812]: Starting SDP server
Apr 18 14:07:17 moj kernel: Bluetooth: L2CAP ver 2.14
Apr 18 14:07:17 moj kernel: Bluetooth: L2CAP socket layer initialized
Apr 18 14:07:17 moj bluetoothd[2812]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
Apr 18 14:07:17 moj kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Apr 18 14:07:17 moj kernel: Bluetooth: BNEP filters: protocol multicast
Apr 18 14:07:17 moj bluetoothd[2812]: bridge pan0 created
Apr 18 14:07:17 moj kernel: Bridge firewalling registered
Apr 18 14:07:17 moj bluetoothd[2812]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Apr 18 14:07:17 moj bluetoothd[2812]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Apr 18 14:07:17 moj NetworkManager: <WARN> device_creator(): /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
Apr 18 14:07:17 moj bluetoothd[2812]: HCI dev 0 registered
Apr 18 14:07:17 moj kernel: Bluetooth: SCO (Voice Link) ver 0.6
Apr 18 14:07:17 moj kernel: Bluetooth: SCO socket layer initialized
Apr 18 14:07:27 moj bluetoothd[2824]: Can't init device hci0: Connection timed out (110)
=================
When trying to do hcicontrol hci0 up or reset i got timeout error on the console
"Can't init device hci0: Connection timed out (110)"

and in /var/logmessages

...
Apr 18 14:07:38 moj kernel: usb 4-2: reset full speed USB device using uhci_hcd and address 2
...
================
last know working kernel is 2.6.31.5-127 (the one shipped on F12 f...

Read more...

I'm also hit with this issue ...

[root@cygn ~]# uname -r
2.6.32.11-99.fc12.i686.PAE

[root@cygn ~]# lsusb
Bus 004 Device 006: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

[[root@cygn ~]# hciconfig hci0 down
[root@cygn ~]# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)
[root@cygn ~]# hciconfig hci0 reset
Can't init device hci0: Connection timed out (110)

dmesg:
usb 4-1: USB disconnect, address 5
usb 4-1: new full speed USB device using uhci_hcd and address 6
usb 4-1: New USB device found, idVendor=1131, idProduct=1001
usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
usb 4-1: Product: ISSCBTA
usb 4-1: configuration #1 chosen from 1 choice
usb 4-1: reset full speed USB device using uhci_hcd and address 6
btusb 4-1:1.0: no reset_resume for driver btusb?
btusb 4-1:1.1: no reset_resume for driver btusb?
hci_cmd_task: hci0 command tx timeout
usb 4-1: reset full speed USB device using uhci_hcd and address 6
usb 4-1: reset full speed USB device using uhci_hcd and address 6

Hi,

I can confirm it (same kernel version and BT device). It was working fine running with the latest F11 kernel (kernel-PAE-2.6.30.10-105.2.23.fc11.i686).

(In reply to comment #20)
The following device works perfectly, though (again with kernel version 2.6.32.11-99.fc12.i686.PAE):

# lsusb
...
Bus 006 Device 008: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)
...

I have a similar problem - noticed it connecting to my iPhone over bluetooth for tethering. It work previously under F12 however has recently stopped. I get the laptop and phone paired and then the connection drops.

...
May 26 00:52:48 neathway kernel: btusb_intr_complete: hci0 urb ef044600 failed to resubmit (1)
May 26 00:52:48 neathway kernel: btusb_bulk_complete: hci0 urb ef044180 failed to resubmit (1)
May 26 00:52:48 neathway kernel: btusb_bulk_complete: hci0 urb ef044d80 failed to resubmit (1)
May 26 00:52:55 neathway kernel: btusb_intr_complete: hci0 urb f6bc1500 failed to resubmit (1)

...

$ uname -a
Linux neathway 2.6.32.12-115.fc12.i686.PAE #1 SMP Fri Apr 30 20:14:08 UTC 2010 i686 i686 i386 GNU/Linux

I too have an ISSC KY-BT100 BT adaptor, and the kernel messages I get are the same as in comment 19.

Bus 007 Device 005: ID 1131:1001 Integrated System Solution Corp. KY-BT100 Bluetooth Adapter

This adaptor used to work under Fedora.

I appear to be having the same problem with a CSR bluetooth dongle.

hci0: Type: BR/EDR Bus: USB
 BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
 UP RUNNING PSCAN ISCAN
 RX bytes:1046 acl:0 sco:0 events:35 errors:0
 TX bytes:371 acl:0 sco:0 commands:31 errors:3
 Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy: RSWITCH HOLD SNIFF PARK
 Link mode: SLAVE ACCEPT

Jul 2 09:07:28 localhost kernel: hci_cmd_task: hci0 command tx timeout
Jul 2 09:14:44 localhost kernel: hci_cmd_task: hci0 command tx timeout

Linux ninja 2.6.33.5-124.fc13.i686.PAE #1 SMP Fri Jun 11 09:42:24 UTC 2010 i686 i686 i386 GNU/Linux

I inserted the the dongle and it was recognized, but the I got the tx timeout right away when I tried to use it. I was slightly more successful when I rebooted the system with the dongle connected. I attempted to pair my phone and it started the process, but got a tx timeout in the middle of the pairing transaction. After that it wouldn't communicate at all.

It seems this issue is fixed for me in 2.6.34 kernels. Kernels I've tried:
  - kernel-2.6.34.1-9.fc13.i686
  - kernel-2.6.34.1-15.fc13.i686

and bluetooth works as it should, it can be hot/coldplugged, hciconfig shows proper device information:

hci0: Type: BR/EDR Bus: USB
        BD Address: 00:11:67:0E:CC:76 ACL MTU: 678:8 SCO MTU: 48:10
        UP RUNNING PSCAN
        RX bytes:2883 acl:0 sco:0 events:79 errors:0
        TX bytes:1071 acl:0 sco:0 commands:79 errors:0

and I can send files, access phone with Wammu with no problems.

Problem still persists for me with 2.6.34.6-54.fc13.i686.PAE
When I insert the dongle I get:
Sep 9 13:49:14 ninja kernel: usb 4-1: new full speed USB device using uhci_hcd and address 2
Sep 9 13:49:14 ninja kernel: usb 4-1: New USB device found, idVendor=0a12, idProduct=0001
Sep 9 13:49:14 ninja kernel: usb 4-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Sep 9 13:49:14 ninja kernel: Bluetooth: Core ver 2.15
Sep 9 13:49:14 ninja kernel: NET: Registered protocol family 31
Sep 9 13:49:14 ninja kernel: Bluetooth: HCI device and connection manager initialized
Sep 9 13:49:14 ninja kernel: Bluetooth: HCI socket layer initialized
Sep 9 13:49:14 ninja kernel: Bluetooth: Generic Bluetooth USB driver ver 0.6
Sep 9 13:49:14 ninja kernel: usbcore: registered new interface driver btusb
Sep 9 13:49:14 ninja bluetoothd[2766]: Bluetooth daemon 4.64
Sep 9 13:49:14 ninja bluetoothd[2767]: Starting SDP server
Sep 9 13:49:14 ninja kernel: Bluetooth: L2CAP ver 2.14
Sep 9 13:49:14 ninja kernel: Bluetooth: L2CAP socket layer initialized
Sep 9 13:49:14 ninja bluetoothd[2767]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
Sep 9 13:49:14 ninja kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 9 13:49:14 ninja kernel: Bluetooth: BNEP filters: protocol multicast
Sep 9 13:49:14 ninja bluetoothd[2767]: bridge pan0 created
Sep 9 13:49:14 ninja bluetoothd[2767]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Sep 9 13:49:14 ninja bluetoothd[2767]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Sep 9 13:49:14 ninja kernel: Bridge firewalling registered
Sep 9 13:49:14 ninja bluetoothd[2767]: HCI dev 0 registered
Sep 9 13:49:14 ninja kernel: Bluetooth: SCO (Voice Link) ver 0.6
Sep 9 13:49:14 ninja kernel: Bluetooth: SCO socket layer initialized
Sep 9 13:49:14 ninja NetworkManager[1385]: <warn> /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
Sep 9 13:49:14 ninja bluetoothd[2767]: HCI dev 0 up
Sep 9 13:49:14 ninja bluetoothd[2767]: Starting security manager 0
Sep 9 13:49:14 ninja bluetoothd[2767]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Sep 9 13:49:14 ninja kernel: Bluetooth: RFCOMM TTY layer initialized
Sep 9 13:49:14 ninja kernel: Bluetooth: RFCOMM socket layer initialized
Sep 9 13:49:14 ninja kernel: Bluetooth: RFCOMM ver 1.11
Sep 9 13:49:14 ninja bluetoothd[2767]: Adapter /org/bluez/2766/hci0 has been enabled
Sep 9 13:49:20 ninja bluetoothd[2767]: Sending read scan enable command failed: Connection timed out (110)
Sep 9 13:49:58 ninja bluetoothd[2767]: Discovery session 0x1c6f068 with :1.75 activated
Sep 9 13:49:58 ninja kernel: hci_cmd_task: hci0 command tx timeout

The last message repeats if I try to do much of anything else.

I'd say this isn't really fixed in 2.34.1 or we're looking at two different issues.

Download full text (3.6 KiB)

Just to add my report, this occurs for me with 2.6.34.7-56.fc13.x86_64 in FC13.

/var/log/messages from plugin to attempted discovery:

Sep 24 10:22:37 lip06jcs-desktop kernel: usb 5-2: new full speed USB device using uhci_hcd
 and address 2
Sep 24 10:22:37 lip06jcs-desktop kernel: usb 5-2: New USB device found, idVendor=0a12, idP
roduct=0001
Sep 24 10:22:37 lip06jcs-desktop kernel: usb 5-2: New USB device strings: Mfr=0, Product=0
, SerialNumber=0
Sep 24 10:22:37 lip06jcs-desktop kernel: Bluetooth: Core ver 2.15
Sep 24 10:22:37 lip06jcs-desktop kernel: NET: Registered protocol family 31
Sep 24 10:22:37 lip06jcs-desktop kernel: Bluetooth: HCI device and connection manager initialized
Sep 24 10:22:37 lip06jcs-desktop kernel: Bluetooth: HCI socket layer initialized
Sep 24 10:22:38 lip06jcs-desktop kernel: Bluetooth: Generic Bluetooth USB driver ver 0.6
Sep 24 10:22:38 lip06jcs-desktop kernel: usbcore: registered new interface driver btusb
Sep 24 10:22:38 lip06jcs-desktop bluetoothd[27218]: Bluetooth daemon 4.64
Sep 24 10:22:38 lip06jcs-desktop bluetoothd[27219]: Starting SDP server
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: L2CAP ver 2.14
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: L2CAP socket layer initialized
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: Parsing /etc/bluetooth/network.conf failed: No such file or directory
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: BNEP filters: protocol multicast
Sep 24 10:22:39 lip06jcs-desktop kernel: Bridge firewalling registered
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: bridge pan0 created
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: Parsing /etc/bluetooth/input.conf failed: No such file or directory
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: Parsing /etc/bluetooth/audio.conf failed: No such file or directory
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: SCO (Voice Link) ver 0.6
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: SCO socket layer initialized
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: HCI dev 0 registered
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: HCI dev 0 up
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: Starting security manager 0
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: RFCOMM TTY layer initialized
Sep 24 10:22:39 lip06jcs-desktop bluetoothd[27219]: Adapter /org/bluez/27218/hci0 has been enabled
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: RFCOMM socket layer initialized
Sep 24 10:22:39 lip06jcs-desktop kernel: Bluetooth: RFCOMM ver 1.11
Sep 24 10:22:39 lip06jcs-desktop NetworkManager[1312]: <warn> /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
Sep 24 10:22:44 lip06jcs-desktop bluetoothd[27219]: Sending read scan enable command failed: Connection timed out (110)
Sep 24 10:31:47 lip06jcs-desktop pulseaudio[2526]: ratelimit.c: 592 events suppressed
Sep 24 10:42:22 lip06jcs-desktop kernel: hci_cmd_task: hci0 command tx timeout
Sep 24 10:42:37 lip06jcs...

Read more...

This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 WONTFIX if it remains open with a Fedora
'version' of '12'.

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 prior to Fedora 12's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 12 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.

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.

The process we are following is described here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

fixed for me on 2.6.34.7-61.fc13.x86_64

This is still a problem for me with kernel-PAE-2.6.34.7-61.fc13.i686. I see:

Nov 4 09:08:25 stealth kernel: hci_cmd_task: hci0 command tx timeout
Nov 4 09:08:34 stealth kernel: hci_cmd_task: hci0 command tx timeout
Nov 4 09:10:18 stealth kernel: hci_cmd_task: hci0 command tx timeout

In the logs when I try to do a discovery.

I still hit this bug. Running F14 fully update till today.

Upon insertion of BT dongle:

Nov 24 16:29:20 work kernel: [14024.876104] usb 2-1.2: new full speed USB device using ehci_hcd and address 6
Nov 24 16:29:20 work kernel: [14024.963736] usb 2-1.2: New USB device found, idVendor=0a12, idProduct=0001
Nov 24 16:29:20 work kernel: [14024.963744] usb 2-1.2: New USB device strings: Mfr=0, Product=0, SerialNumber=0
Nov 24 16:29:20 work bluetoothd[1676]: HCI dev 1 registered
Nov 24 16:29:20 work bluetoothd[1676]: HCI dev 1 up
Nov 24 16:29:20 work bluetoothd[1676]: Starting security manager 1
Nov 24 16:29:25 work bluetoothd[1676]: Can't read version info for /org/bluez/1672/hci1: Connection timed out (110)

[root@work ~]# lsusb
Bus 002 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

[root@work ~]# hciconfig
hci1: Type: BR/EDR Bus: USB
 BD Address: XX:XX:XX:XX:XX:XX ACL MTU: 1021:4 SCO MTU: 180:1
 UP RUNNING
 RX bytes:330 acl:0 sco:0 events:8 errors:0
 TX bytes:24 acl:0 sco:0 commands:9 errors:1

( I masked the BD Address )

Same here:
Fedora 14, updated today (Dec. 11 2010)

On Insert:
Dec 11 20:49:55 Overeasy kernel: [16655.639043] usb 3-2: new full speed USB device using ohci_hcd and address 6
Dec 11 20:49:55 Overeasy kernel: [16655.827395] usb 3-2: New USB device found, idVendor=0a12, idProduct=0001
Dec 11 20:49:55 Overeasy kernel: [16655.827408] usb 3-2: New USB device strings: Mfr=0, Product=0, SerialNumber=0

[root@Overeasy ~]# lsusb | grep 0a12
Bus 003 Device 006: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

[root@Overeasy ~]# hciconfig -a
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:0 acl:0 sco:0 commands:0 errors:0

[root@Overeasy ~]# hciconfig hci0 up
[root@Overeasy ~]# hciconfig hci0
hci0: Type: BR/EDR Bus: USB
 BD Address: 00:1F:81:00:01:1C ACL MTU: 1021:4 SCO MTU: 180:1
 UP RUNNING
 RX bytes:322 acl:0 sco:0 events:7 errors:0
 TX bytes:21 acl:0 sco:0 commands:8 errors:1

[root@Overeasy ~]# hcitool scan
Scanning ...
Inquiry failed: Connection timed out

Changed in bluez (Debian):
status: New → Confirmed
Changed in linux:
importance: Unknown → Medium

Related bugs: Ubuntu launchpad #460743, Debian Squeeze #525220, Linux kernel #10126. Tested again using experimental kernel 2.6.38-rc6. The problem does not occur during intial status enquiry, but a timeout occurs, when an attempt is made to activate the bluetooth device:

This appears to still be broken in 2.6.390-rc4:

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

Hi, All

Here is my config (I have Debian Squeeze installed on a Dell D630):

$ uname -a
Linux mrneagu-ro 2.6.32-5-amd64 #1 SMP Mon Mar 7 21:35:22 UTC 2011 x86_64 GNU/Linux
cat /etc/debian_version
6.0.1

'hciconfig hci0' gave me null BT address (00:00:00:00:00:00) and I also could not bring up the Bluetooth module:

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

lsusb gave me someting like this:
Bus 002 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth

My problem occurred when I started VMWare which stole the Bluetooth adapter (usb.autoConnect.device0 = "" and even if usb.generic.autoconnect = "FALSE" it stole my Bluetooth). Then the kernel (on the host) crashed and Gnome asked me to send a report to kernel.org.

As this happened really often, I usually had to reboot to solve the problem, so I was searching for a way to reset the Bluetooth module in place and restart Bluetooth services. I found this post: http://marc.info/?l=linux-usb&m=121459435621262&w=2 to reset the any usb device.

$ sudo usbreset /dev/bus/usb/002/002

After this, every restart would not resolve the problem. Address of the module still null and "Can't init device hci0: Connection timed out (110)". The Bluetooth icon in the upper-right corner of the screen had always a red x-mark on it.

Additionally the Bluetoth module changed from bus 2 to bus 3:
Bus 003 Device 002: ID 413c:8140 Dell Computer Corp. Wireless 360 Bluetooth

Now, I resolved the problem according to this forum: http://ubuntuforums.org/showpost.php?p=8306034&postcount=4 :

I restarted in Windows and used the Bluetooth mouse there and then rebooted back in Debian and it came back by itself. So it seems that Windows somehow knows how to reset the Bluetooth module and Linux doesn't. I don't know if it's a kernel or bluez bug, but I hope this gets resolved because it is very annoying.

Thank you.
Kind Regards.

Isn't is some kind of firmware problem? I had my KY-BT100 USB Bluetooth adapter (ID 1131:1001) working perfectly fine in Fedora 14, with update to F15 it stopped to work again.

Funny thing is, if I boot F14, enable BT then reboot to F15 it works as long as the the adapter stays plugged. Replugging BT makes it unusable again.

My current software is:
kernel-2.6.38.8-32.fc15.i686.PAE
bluez-4.87-5.fc15.i686

test Fedora 14 (stock livecd)
kernel-2.6.35.6-45.fc14.686
bluez-4.71-5.fc14.i686

It turns out that some bluetooth devices that advertise themselves as "Cambridge Silicon Radio" actually use a chipset made by Accel Semiconductor. These devices do not work in Linux, and cause the symptoms described in this bug. Try opening the case on one of the dongles with a screwdriver, and looking for markings on the board. If there is a marking that contains a number beginning "AS3620QA", then this device contains a chip made by Accel Semiconductor. These devices do not work on Linux at this time. I don't know whether or not anyone is working on a driver for these, but the CSR stuff will not work, although it may appear to be partially or intermittently operational.

Mark.

It seems that we have two separate cases here.
  - adapters that never worked properly under linux
  - adapters, for which support has regressed in some particular kernel release.

Mark,

Mine is one of the Accel Semiconductor AS3620QA units, so that explains my blue tooth problems. I'm SOL for now. Luckily they were cheap. :)

(In reply to comment #38)
> It seems that we have two separate cases here.
> - adapters that never worked properly under linux
> - adapters, for which support has regressed in some particular kernel
> release.

Yes, for me this was a regression, as I wrote in Comment #3.

I found one thing that some might find interesting. My laptop (Samsung R522) has 4 USB ports. One of them is chargeable. If I plug BT adapter in this particular port it works properly, I can enable it, pair my phone, browse it content. If I plug BT adapter in any other port (including powered USB hub) device is detected, but permanently in off state.

Bluetooth is worked under F14, but stop to work with F15

[root@ua-dudn00000 bluetooth]# cat /etc/issue
Fedora release 15 (Lovelock)
Kernel \r on an \m (\l)

[root@ua-dudn00000 bluetooth]# uname -r
2.6.40.3-0.fc15.i686.PAE

[root@ua-dudn00000 bluetooth]# hciconfig -a
hci0: Type: BR/EDR Bus: USB
        BD Address: 00:27:13:C4:1A:6A ACL MTU: 1021:8 SCO MTU: 64:1
        DOWN
        RX bytes:493 acl:0 sco:0 events:22 errors:0
        TX bytes:200 acl:0 sco:0 commands:52 errors:1
        Features: 0xff 0xff 0x8f 0xfe 0x9b 0xff 0x79 0x83
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
        Link policy: RSWITCH HOLD SNIFF PARK
        Link mode: SLAVE ACCEPT

[root@ua-dudn00000 bluetooth]# lsusb -v -d 03f0:231d

Bus 001 Device 005: ID 03f0:231d Hewlett-Packard
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 2.00
  bDeviceClass 224 Wireless
  bDeviceSubClass 1 Radio Frequency
  bDeviceProtocol 1 Bluetooth
  bMaxPacketSize0 64
  idVendor 0x03f0 Hewlett-Packard
  idProduct 0x231d
  bcdDevice 3.06
  iManufacturer 1 Broadcom Corp
  iProduct 2 HP Integrated Module
  iSerial 0
  bNumConfigurations 1
...

[root@ua-dudn00000 bluetooth]# hciconfig hci0 up
Can't init device hci0: Connection timed out (110)

[root@ua-dudn00000 bluetooth]# service bluetooth restart
Redirecting to /bin/systemctl restart bluetooth.service
[root@ua-dudn00000 bluetooth]# dmesg
[ 5138.468776] hci_cmd_timer: hci0 command tx timeout
[ 5139.470320] hci_cmd_timer: hci0 command tx timeout
[ 5140.471892] hci_cmd_timer: hci0 command tx timeout
[ 5141.473456] hci_cmd_timer: hci0 command tx timeout

there seem to be a number of different problems reported here, some of which may be fixed in current trees.

Given where f14 is in its lifecycle, it's unlikely to see further fixes beyond security bugs, and easily backported identified changes.

If you are still having problems on f15/f16beta, please file a new bug against the relevant release. Tracking them independently is the only way to really get a handle on this.

Changed in linux (Ubuntu):
assignee: nobody → Chrystalla Mytidou (stalo-my)
assignee: Chrystalla Mytidou (stalo-my) → nobody

Well !

My dongue was functional in fedora 14. After a migration to 15 and PUF !

"can't init device hci0", bla bla bla !

BUT !

Maybe you can see what f17 has made.
I have downloaded a SPIN with GNOME (i use KDE) and my bluetooth is live again.

Look there, into F17, and please, correct the f16 bug.

Changed in bluez (Debian):
status: Confirmed → Fix Released
tags: removed: verification-needed
Changed in linux (Fedora):
importance: Unknown → High
status: Unknown → Fix Released
Displaying first 40 and last 40 comments. View all 353 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Related questions

Remote bug watches

Bug watches keep track of this bug in other bug trackers.