[KARMIC] Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout) (Broadcom dongle)

Bug #493747 reported by Fernando D.
50
This bug affects 9 people
Affects Status Importance Assigned to Milestone
Bluez Utilities
New
Undecided
Unassigned
bluez (Ubuntu)
Confirmed
Undecided
Unassigned
Nominated for Karmic by Fernando D.
Nominated for Lucid by Fernando D.

Bug Description

Hi:

I can't transfer files or browse them through Bluetooth. On Ubuntu 9.04 it worked fine, but now with the new 9.10 (fresh install, not distro-upgrade) doesn't work anymore. I've read other posts with the same problem, but in previous versions, so apparently not everybody have this problem with Karmic and bluetooth.

Here are the technical info about this bug.

$ cat /proc/version_signature
Ubuntu 2.6.31-16.52-generic

$ uname -a
Linux pcfdb 2.6.31-16-generic #52-Ubuntu SMP Thu Dec 3 22:07:16 UTC 2009 x86_64 GNU/Linux

$ sudo dpkg -l | grep bluez
ii bluez 4.51-0ubuntu2 Bluetooth tools and daemons
ii bluez-alsa 4.51-0ubuntu2 Bluetooth audio support
ii bluez-cups 4.51-0ubuntu2 Bluetooth printer driver for CUPS
rc bluez-gnome 1.8-1ubuntu1 Bluetooth utilities for GNOME
ii bluez-gstreamer 4.51-0ubuntu2 Bluetooth GStreamer support
ii bluez-hcidump 1.42-1build1 Analyses Bluetooth HCI packets
rc bluez-utils 4.51-0ubuntu2 Transitional package
ii python-bluez 0.16-1ubuntu1 Python wrappers around BlueZ for rapid bluet

1) I connect my bluetooth dongle:

SYSLOG events covering this:
Dec 7 20:50:06 pcfdb kernel: [36922.071276] usb 6-1: new full speed USB device using uhci_hcd and address 2
Dec 7 20:50:17 pcfdb kernel: [36932.292306] usb 6-1: configuration #1 chosen from 1 choice
Dec 7 20:50:17 pcfdb kernel: [36932.368437] Bluetooth: Generic Bluetooth USB driver ver 0.5
Dec 7 20:50:17 pcfdb kernel: [36932.368617] usbcore: registered new interface driver btusb
Dec 7 20:50:17 pcfdb bluetoothd[19624]: Bluetooth daemon 4.51
Dec 7 20:50:17 pcfdb bluetoothd[19625]: Starting SDP server
Dec 7 20:50:17 pcfdb bluetoothd[19625]: Can't load plugin /usr/lib/bluetooth/plugins/netlink.so: /usr/lib/bluetooth/plugins/netlink.so: undefined symbol: debug
Dec 7 20:50:17 pcfdb kernel: [36932.475955] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
Dec 7 20:50:17 pcfdb kernel: [36932.475961] Bluetooth: BNEP filters: protocol multicast
Dec 7 20:50:17 pcfdb bluetoothd[19625]: bridge pan0 created
Dec 7 20:50:17 pcfdb NetworkManager: SCPlugin-Ifupdown: devices added (path: /sys/devices/virtual/net/pan0, iface: pan0)
Dec 7 20:50:17 pcfdb NetworkManager: SCPlugin-Ifupdown: device added (path: /sys/devices/virtual/net/pan0, iface: pan0): no ifupdown configuration found.
Dec 7 20:50:17 pcfdb NetworkManager: <WARN> device_creator(): /sys/devices/virtual/net/pan0: couldn't determine device driver; ignoring...
Dec 7 20:50:17 pcfdb kernel: [36932.506482] Bridge firewalling registered
Dec 7 20:50:17 pcfdb bluetoothd[19625]: HCI dev 0 registered
Dec 7 20:50:17 pcfdb bluetoothd[19625]: HCI dev 0 up
Dec 7 20:50:17 pcfdb bluetoothd[19625]: Starting security manager 0
Dec 7 20:50:17 pcfdb bluetoothd[19625]: Parsing /etc/bluetooth/serial.conf failed: No such file or directory
Dec 7 20:50:17 pcfdb bluetoothd[19625]: Adapter /org/bluez/19624/hci0 has been enabled

2) Querying bluetooth service status
$ sudo /etc/init.d/bluetooth status
 * bluetooth is running

3) Getting info about the bluetooth dongle
$ sudo hciconfig -a
hci0: Type: USB
 BD Address: 00:1A:7D:0A:BA:8F ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:664 acl:0 sco:0 events:18 errors:0
 TX bytes:77 acl:0 sco:0 commands:20 errors:0
 Features: 0xff 0xff 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)

4) Trying to scan devices
$ sudo hcitool scan
Scanning ...
Inquiry failed: Connection timed out

5) Now I repeat the tests but with bluetooth service down:
$ sudo /etc/init.d/bluetooth stop

6) Querying bluetooth service status:
$ sudo /etc/init.d/bluetooth status
 * bluetooth is not running

7) Querying hci status:
$ sudo hciconfig -a
hci0: Type: USB
 BD Address: 00:1A:7D:0A:BA:8F ACL MTU: 377:10 SCO MTU: 16:0
 DOWN
 RX bytes:664 acl:0 sco:0 events:18 errors:0
 TX bytes:86 acl:0 sco:0 commands:22 errors:0
 Features: 0xff 0xff 0x0d 0x38 0x08 0x08 0x00 0x00
 Packet type: DM1 DM3 DM5 DH1 DH3 DH5 HV1 HV2 HV3
 Link policy:
 Link mode: SLAVE ACCEPT

8) Starting up the device:
$ sudo hciconfig hci0 up

9) Querying hci status again (more info is showed now):
$ sudo hciconfig -a
hci0: Type: USB
 BD Address: 00:1A:7D:0A:BA:8F ACL MTU: 377:10 SCO MTU: 16:0
 UP RUNNING
 RX bytes:1012 acl:0 sco:0 events:29 errors:0
 TX bytes:124 acl:0 sco:0 commands:33 errors:0
 Features: 0xff 0xff 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.1 (0x1) HCI Rev: 0x3 LMP Ver: 1.1 (0x1) LMP Subver: 0x800
 Manufacturer: Broadcom Corporation (15)

10) Trying to scan devices
$ sudo hcitool scan
Scanning ...
 00:17:5C:DD:6A:AD GX29_Fer

11) If I startup the bluetooth service again, then the history repeats again from step 2

MORE INFO:
The bluetooth icon that appears when I connect my dongle, don't save the value when I check the option "Make visible" (it's not grayed out, just don't save the value and disappears next time I open the bluetooth interface)
Scanning blutooth devices on the interface don't work either (obviously)

If there is any information you want, please tell me how to get it.

Thanks.

ProblemType: Bug
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: fdbozzo 2598 F.... pulseaudio
 /dev/snd/pcmC0D0p: fdbozzo 2598 F...m pulseaudio
 /dev/snd/pcmC0D0c: fdbozzo 2598 F...m pulseaudio
CRDA: Error: [Errno 2] No existe el fichero ó directorio
Card0.Amixer.info:
 Card hw:0 'Intel'/'HDA Intel at 0xf9ff8000 irq 22'
   Mixer name : 'Realtek ALC883'
   Components : 'HDA:10ec0883,1043829f,00100002'
   Controls : 35
   Simple ctrls : 20
Date: Mon Dec 7 20:39:42 2009
DistroRelease: Ubuntu 9.10
HibernationDevice: RESUME=UUID=547d9742-58b3-4fa8-86f6-a3e188efd551
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
IwConfig:
 lo no wireless extensions.

 eth0 no wireless extensions.

 vboxnet0 no wireless extensions.
MachineType: System manufacturer P5K
NonfreeKernelModules: nvidia
Package: linux-image-2.6.31-16-generic 2.6.31-16.52
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.31-16-generic root=UUID=a1b18398-9d96-4f54-8e5b-79acebf8df58 ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-16.52-generic
RelatedPackageVersions:
 linux-backports-modules-2.6.31-16-generic N/A
 linux-firmware 1.26
RfKill:

SourcePackage: linux
Uname: Linux 2.6.31-16-generic x86_64
WifiSyslog:
 Dec 7 17:18:37 pcfdb kernel: [24232.614993] __ratelimit: 6 callbacks suppressed
 Dec 7 17:18:37 pcfdb kernel: [24232.615001] npviewer.bin[18944]: segfault at ff99cd48 ip 00000000ff99cd48 sp 00000000ffa73aec error 14
 Dec 7 17:22:13 pcfdb kernel: [24448.711727] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)
 Dec 7 17:22:20 pcfdb kernel: [24455.519150] device eth0 entered promiscuous mode
dmi.bios.date: 10/14/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1201
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5K
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1201:bd10/14/2008:svnSystemmanufacturer:pnP5K:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5K:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5K
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer

Revision history for this message
Fernando D. (fdbozzo) wrote :
Revision history for this message
Fernando D. (fdbozzo) wrote :

Forgot to put DMESG info:

$ dmesg | grep usb
[ 0.345865] usbcore: registered new interface driver usbfs
[ 0.345865] usbcore: registered new interface driver hub
[ 0.345865] usbcore: registered new device driver usb
[ 0.690158] usb usb1: configuration #1 chosen from 1 choice
[ 0.710130] usb usb2: configuration #1 chosen from 1 choice
[ 0.710529] usb usb3: configuration #1 chosen from 1 choice
[ 0.710792] usb usb4: configuration #1 chosen from 1 choice
[ 0.711039] usb usb5: configuration #1 chosen from 1 choice
[ 0.711288] usb usb6: configuration #1 chosen from 1 choice
[ 0.711565] usb usb7: configuration #1 chosen from 1 choice
[ 0.711814] usb usb8: configuration #1 chosen from 1 choice
[ 1.350019] usb 4-1: new low speed USB device using uhci_hcd and address 2
[ 1.534015] usb 4-1: configuration #1 chosen from 1 choice
[ 1.610923] usbcore: registered new interface driver hiddev
[ 1.611032] usbcore: registered new interface driver usbhid
[ 1.611036] usbhid: v2.6:USB HID core driver
[ 1.630063] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.0/input/input3
[ 1.630249] logitech 0003:046D:C517.0001: input,hidraw0: USB HID v1.10 Keyboard [Logitech USB Receiver] on usb-0000:00:1a.1-1/input0
[ 1.662593] input: Logitech USB Receiver as /devices/pci0000:00/0000:00:1a.1/usb4/4-1/4-1:1.1/input/input4
[ 1.662723] logitech 0003:046D:C517.0002: input,hiddev96,hidraw1: USB HID v1.10 Mouse [Logitech USB Receiver] on usb-0000:00:1a.1-1/input1
[ 1.811317] usb 4-2: new full speed USB device using uhci_hcd and address 3
[ 2.047730] usb 4-2: configuration #1 chosen from 1 choice
[ 13.682717] usbcore: registered new interface driver pac7311
[36922.071276] usb 6-1: new full speed USB device using uhci_hcd and address 2
[36932.292306] usb 6-1: configuration #1 chosen from 1 choice
[36932.368617] usbcore: registered new interface driver btusb
[38503.540072] usb 6-1: USB disconnect, address 2
[38503.540634] btusb_intr_complete: hci0 urb ffff8800660e5cc0 failed to resubmit (19)
[38503.540648] btusb_bulk_complete: hci0 urb ffff8800660e5f00 failed to resubmit (19)
[38503.541633] btusb_bulk_complete: hci0 urb ffff8800660e56c0 failed to resubmit (19)
[38503.541800] btusb_send_frame: hci0 urb ffff8800464da3c0 submission failed
[39073.860038] usb 6-1: new full speed USB device using uhci_hcd and address 3
[39084.072287] usb 6-1: configuration #1 chosen from 1 choice

Revision history for this message
Michalxo (michalxo) wrote :

Similar problem here on i386, kernel 2.6.31-16. In liveCD 2.6.31-14 BT works flawlessly, but here on 32-16 it says that my adapter is not present at all. Weird bug. I am trying to install 31-14 back to see if it will work again.

Revision history for this message
Michalxo (michalxo) wrote :

No, I were not right. I've just tried booting to 31-14,31-16, karmic liveCD (31-14) and lucid liveCD (32-xx) and my BT did not show up at all. It's probably odds when BT comes up or not :-/

affects: ubuntu → bluez (Ubuntu)
Revision history for this message
Michael Hackett (at217) wrote :

I am seeing the same behaviour here, with a Keyspan USB dongle with a Broadcom 2033 chip. Everything worked before upgrading from Jaunty. I found bug #156133 and applied the karmic-proposed package but it still behaves the same.

lsusb:
Bus 002 Device 004: ID 0a5c:2001 Broadcom Corp. Bluetooth Device

Here's what I see in syslog when I try to do a device search from the task bar applet:

Jan 7 13:49:38 mhackett bluetoothd[985]: HCI dev 0 down
Jan 7 13:49:38 mhackett bluetoothd[985]: Adapter /org/bluez/973/hci0 has been disabled
Jan 7 13:49:38 mhackett bluetoothd[985]: Stopping security manager 0
Jan 7 13:49:41 mhackett bluetoothd[985]: HCI dev 0 up
Jan 7 13:49:41 mhackett bluetoothd[985]: Starting security manager 0
Jan 7 13:49:41 mhackett bluetoothd[985]: Adapter /org/bluez/973/hci0 has been enabled
Jan 7 13:49:58 mhackett bluetoothd[985]: Discovery session 0xaf2730 with :1.66 activated
Jan 7 13:49:58 mhackett kernel: [ 3027.668359] hci_cmd_task: hci0 command tx timeout

Revision history for this message
Fernando D. (fdbozzo) wrote :

Work OK on Ubuntu 9.04, fails in 9.10 and 10.04 alpha. Theese are similar bug reports: 492747, 453885, 424225, 494172

Revision history for this message
Tony Shadwick (numbski+bugs-launchpad-net) wrote :

Just mentioning that I can confirm this behavior. Karmic, x86-64 and a D-Link dongle with broadcom chipset. Precisely as the original poster reported.

Fernando D. (fdbozzo)
Changed in bluez (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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