Lucid + DLink Bluetooth Donge = hci_command_task: hci0 command tx timeout

Bug #627024 reported by Tony Shadwick on 2010-08-30
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Undecided
Unassigned

Bug Description

Strongly suspect this is related to this bug:

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/268502

There was a big push to file new bugs for this since some were fixed, so I'm doing just that.

Please note that there is a bug in linux-firmware-nonfree. In order to get even this far, I had to manually symlink /lib/firmware/bcm2033-fw.bin and /lib/firmware/bcm2033-md.hex to BCM2033-FW.bin and BCM2033-MD.hex. Separate bug, separate issue, but just the same, if you're attempting to reproduce my results, that's something to keep in mind. This also required that I install bluez-compat. The hci device never gets created otherwise:

[260752.445568] Bluetooth: Broadcom Blutonium firmware driver ver 1.2
[260752.445600] usb 1-5.4: firmware: requesting BCM2033-MD.hex
[260752.461661] usb 1-5.4: firmware: requesting BCM2033-FW.bin
[260752.464100] usbcore: registered new interface driver bcm203x
[260753.012646] usb 1-5.4: USB disconnect, address 8
[260753.270167] usb 1-5.4: new full speed USB device using ehci_hcd and address 9
[260753.411283] usb 1-5.4: configuration #1 chosen from 1 choice
[260753.757933] Bluetooth: L2CAP ver 2.14
[260753.757935] Bluetooth: L2CAP socket layer initialized
[260753.810302] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[260753.810305] Bluetooth: BNEP filters: protocol multicast
[260753.852462] Bridge firewalling registered
[260753.937918] Bluetooth: SCO (Voice Link) ver 0.6
[260753.937920] Bluetooth: SCO socket layer initialized
[260754.182674] Bluetooth: RFCOMM TTY layer initialized
[260754.182690] Bluetooth: RFCOMM socket layer initialized
[260754.182692] Bluetooth: RFCOMM ver 1.11
[260793.491079] hci_cmd_task: hci0 command tx timeout
[260842.812029] hci_cmd_task: hci0 command tx timeout
[260871.528140] hci_cmd_task: hci0 command tx timeout
[260895.742432] hci_cmd_task: hci0 command tx timeout
root@shadwickt-desk:/usr/lib/bluetooth/plugins# hciconfig -a
hci0: Type: USB
 BD Address: 00:40:05:D0:C1:AF ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:664 acl:0 sco:0 events:18 errors:0
 TX bytes:98 acl:0 sco:0 commands:23 errors:0
 Features: 0xff 0xfd 0x05 0x00 0x00 0x00 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)
root@shadwickt-desk:/usr/lib/bluetooth/plugins# hcitool dev
Devices:
 hci0 00:40:05:D0:C1:AF
root@shadwickt-desk:/usr/lib/bluetooth/plugins# lsusb | grep -i blue
Bus 001 Device 009: ID 0a5c:2001 Broadcom Corp. Bluetooth Device
Linux shadwickt-desk 2.6.32-24-generic #42-Ubuntu SMP Fri Aug 20 14:21:58 UTC 2010 x86_64 GNU/Linux
root@shadwickt-desk:/usr/lib/bluetooth/plugins# aptitude show bluez
Package: bluez
State: installed
Automatically installed: no
Version: 4.60-0ubuntu8
Priority: optional
Section: admin
Maintainer: Ubuntu Developers <email address hidden>
Uncompressed Size: 1,401k
Depends: libbluetooth3 (>= 4.60-0ubuntu8), libc6 (>= 2.7), libdbus-1-3 (>=
         1.1.1), libglib2.0-0 (>= 2.23.5), libnl1 (>= 1.1), libusb-0.1-4 (>=
         2:0.1.12), module-init-tools, makedev | udev, lsb-base, dbus
Suggests: python-gobject, python-dbus
Conflicts: bluez-utils (<= 3.36-3)
Replaces: bluez-audio, bluez-input, bluez-network, bluez-serial, bluez-utils (<=
          4.9)

Jeremy Foshee (jeremyfoshee) wrote :

Hi Tony,

Please be sure to confirm this issue exists with the latest development release of Ubuntu. ISO CD images are available from http://cdimage.ubuntu.com/daily/current/ . If the issue remains, please run the following command from a Terminal (Applications->Accessories->Terminal). It will automatically gather and attach updated debug information to this report.

apport-collect -p linux 627024

Also, if you could test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-kernel-logs
tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Jeremy Foshee (jeremyfoshee) wrote :

This bug report was marked as Incomplete and has not had any updated comments for quite some time. As a result this bug is being closed. Please reopen if this is still an issue in the current Ubuntu development release http://cdimage.ubuntu.com/daily-live/current/ . Also, please be sure to provide any requested information that may have been missing. To reopen the bug, click on the current status under the Status column and change the status back to "New". Thanks.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: kj-expired
Changed in linux (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers