Bug#525220: Bluetooth Device: hci_cmd_task: hci0 command tx timeout

[Dominique Meeùs <dominique@d-meeus.be>]

Mind the fact that there may be different bug with same (hci0 command tx 
timeout) symptoms. Mind the fact that it maybe (in some cases) a Bluez 
software bug, not necessarily a kernel (btusb) bug.

uname -a : Linux library 2.6.28-11-generic #42-Ubuntu SMP Fri Apr 17 
01:57:59 UTC 2009 i686 GNU/Linux

dpkg -l | grep bluez : ii  bluez 4.35-0ubuntu1

/etc/init.d/bluetooth status :  * bluetooth is running

I plug my dongle : lsusb | grep Blue : Bus 003 Device 002: ID 2001:f111 
D-Link Corp. [hex] DBT-122 Bluetooth adapter

syslog :
Apr 29 21:55:13 library kernel: [11373.440046] usb 3-1: new full speed 
USB device using uhci_hcd and address 2
Apr 29 21:55:14 library kernel: [11373.632545] usb 3-1: configuration #1 
chosen from 1 choice
Apr 29 21:55:14 library bluetoothd[3038]: HCI dev 0 registered
Apr 29 21:55:14 library kernel: [11373.704904] Bluetooth: Generic 
Bluetooth USB driver ver 0.3
Apr 29 21:55:14 library kernel: [11373.705067] usbcore: registered new 
interface driver btusb
Apr 29 21:55:14 library bluetoothd[3038]: HCI dev 0 up
Apr 29 21:55:14 library bluetoothd[3038]: Starting security manager 0
Apr 29 21:55:19 library kernel: [11378.844250] hci_cmd_task: hci0 
command tx timeout
Apr 29 21:55:24 library bluetoothd[3038]: Can't write class of device: 
Connection timed out (110)
Apr 29 21:55:24 library bluetoothd[3038]: Adapter /org/bluez/3038/hci0 
has been enabled
Apr 29 21:55:24 library kernel: [11383.850256] hci_cmd_task: hci0 
command tx timeout
Apr 29 21:55:29 library bluetoothd[3038]: Sending getting name command 
failed: Connection timed out (110)
Apr 29 21:55:29 library kernel: [11388.855433] hci_cmd_task: hci0 
command tx timeout
Apr 29 21:55:34 library bluetoothd[3038]: Can't read class of device on 
hci0: Connection timed out (110)
Apr 29 21:55:34 library kernel: [11393.860292] hci_cmd_task: hci0 
command tx timeout

hciconfig -a
hci0:    Type: USB
   BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
   UP RUNNING
   RX bytes:667 acl:0 sco:0 events:19 errors:0
   TX bytes:591 acl:0 sco:0 commands:24 errors:0
   Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy:
   Link mode: SLAVE ACCEPT
Can't read local name on hci0: Connection timed out (110)

*** Now I stop bluetooth ***
sudo /etc/init.d/bluetooth stop :  * Stopping bluetooth

As a result, hci0 is down : hciconfig :
hci0:    Type: USB
   BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
   DOWN
   RX bytes:673 acl:0 sco:0 events:20 errors:0
   TX bytes:597 acl:0 sco:0 commands:26 errors:0


Let's start it again : sudo hciconfig hci0 up
hciconfig -a
hci0:    Type: USB
   BD Address: 00:13:46:00:55:A0 ACL MTU: 377:10 SCO MTU: 16:0
   UP RUNNING
   RX bytes:1015 acl:0 sco:0 events:30 errors:0
   TX bytes:632 acl:0 sco:0 commands:36 errors:0
   Features: 0xff 0xfe 0x0d 0x38 0x08 0x08 0x00 0x00
   Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
   Link policy:
   Link mode: SLAVE ACCEPT
   Name: 'Broadcom BCM2035'
   Class: 0x000000
   Service Classes: Unspecified
   Device Class: Miscellaneous,
   HCI Ver: 1.2 (0x2) HCI Rev: 0x0 LMP Ver: 1.2 (0x2) LMP Subver: 0x309
   Manufacturer: Broadcom Corporation (15)

*** No more "timed out (110)" with bluetooth stopped ! ***
(In this situation, I can hcitool scan or l2ping, which I can't with 
bluetooth.)
My dongle does work to a certain extent with btusb alone, but not with 
btusb and bluetooth together !