I had a similar problem after upgrading to a kernel that uses btusb
instead of hci_usb.
Symptoms were, BT adapter would go up in syslog, then hci0: timeout tx,
then it goes down. stopping bluetoothd and manually setting it "up"
things like scan inq work.
In my case the IBM Bluetooth IV module... I suspect that the handling of
OCF_READ_DEFAULT_LINK_POLICY is different , hci_usb seemed to be ok if
adapter didn't support it, but btusb times out if BT adapter doesn't
support it, causing bluetoothd to fail and take down the interface... my
BT adapter doesn't support the command. I patched my bluetooth
userspace to not send the command, now things work.
In IRC one maintainer was unsure if BT version ( shown in hciconfig -a),
supported commands, or supported features would be the most reliable way
to detect support of this command. If several people have success, and
report the following info, then there should be a basis for how to fix
things in bluez upstream.
Can you check your adapter's support of this command:
# lsusb
... (so we know what device you have)
Bus 002 Device 003: ID 0a5c:2101 Broadcom Corp. A-Link BlueUsbA2 Bluetooth
# hciconfig -a
hci0: Type: USB
...
Features: 0xff 0xff 0x8d 0xfe 0x9b 0xf9 0x00 0x80
....
HCI Ver: 2.0 (0x3) HCI Rev: 0x200a LMP Ver: 2.0 (0x3) LMP Subver: 0x4127
Manufacturer: Broadcom Corporation (15)
# hciconfig hci0 commands
hci0: Type: USB
BD Address: 00:02:72:CE:3A:F5 ACL MTU: 1017:8 SCO MTU: 64:8
Commands: Octet 0 = 0xff (Bit 0 1 2 3 4 5 6 7)
...etc...
'Write Link Policy Settings' ---> 'Read Default Link Policy Settings'
<---
---> 'Write Default Link Policy Settings' <--- 'Flow Specification'
if your adapter is missing those (likely due to older spec), try this
patch and things should improve.
** Attachment added: "force disable DEFAULT_LINK_POLICY to diagnose bluetooth
problem"
http://launchpadlibrarian.net/36947405/no_default_link_policy.patch
--
[D-Link DBT-122] Bluetooth doesn't work (hci_cmd_task: hci0 command tx timeout)
https://bugs.launchpad.net/bugs/377225
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
