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

[Mark Hobley <markhobley@yahoo.co.uk>]

I upgraded the kernel to 2.6.39-1 from experimental and rebooted the system. Initially, After typing hcitool inq, the system showed that my mobile phone was present, so it appeared as though bluetooth was at least momentarily partially working. However, from the mobile phone, the computer was not listed, as if the computer was somehow hidden.

I upgraded bluez to version 4.93-1 from Debian experimental, in the hope that this might fix the visibility problem.

However, bluetooth now appears to be broken again. Following a reboot of the computer:

hciconfig -a
                                                                 
hci0:   Type: BR/EDR  Bus: USB
        BD Address: 00:1F:81:00:01:1C  ACL MTU: 1021:4  SCO MTU: 180:1
        DOWN 
        RX bytes:59 acl:0 sco:0 events:5 errors:0
        TX bytes:15 acl:0 sco:0 commands:36 errors:31
        Features: 0xff 0x3e 0x09 0x76 0x80 0x01 0x00 0x80
        Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3 
        Link policy: 
        Link mode: SLAVE ACCEPT 

I now try to bring the interface into operational mode, and the timeout
error reoccurs:

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

dmesg shows squillions of errors as follows:

[nnnn.nnnnnn] hci_cmd_timer: hci0 command tx timeout

So it appears that there might also be bugs in bluez which are aggrevating this problem. BLUETOOTH IS NOT OPERATIONAL.

Mark.