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

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

A strange thing has just happened. I plugged the dongle in to get some information from it, and when I ran hciconfig, it showed as "up running":

hciconfig -a 
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 
        RX bytes:754 acl:0 sco:0 events:26 errors:0
        TX bytes:368 acl:0 sco:0 commands:25 errors:0
        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 
        Link mode: SLAVE ACCEPT 
        Name: 'Accel-OB2'
        Class: 0x4a0100
        Service Classes: Networking, Capturing, Telephony
        Device Class: Computer, Uncategorized
        HCI Version: 2.0 (0x3)  Revision: 0x44
        LMP Version: 2.0 (0x3)  Subversion: 0x3
        Manufacturer: Cambridge Silicon Radio (10)

I don't know why that has happened. I normally just get a timeout error, so it looks like this problem is not always consistent. I have not updated my system, since I last reported HCI Timeout.

My mobile phone is now temporarily visible to my computer, but I cannot see the computer from the mobile phone, so I am unable to initiate a transfer from the mobile phone. I don't know how to take the device out of invisibility mode, and when I try, it will probably revert back to giving HCI timeout, but hey ... this is the first time I have seen this half working since I upgraded bluez.

Mark.