FS#27825 - ASUS USB-BT211 bluetooth dongle halts boot (and doesn't work anyway if inserted post boot)

Attached to Project: Arch Linux
Opened by none given (hoban) - Wednesday, 04 January 2012, 16:14 GMT
Last edited by Tobias Powalowski (tpowa) - Wednesday, 12 September 2012, 06:25 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To No-one
Architecture All
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Description:
ASUS USB-BT211 bluetooth dongle halts boot (and doesn't work anyway if inserted post boot).

Additional info:
* package version(s)
Fully up-to-date system including gnome 3.

* config and/or log files etc.
lsusb shows the following:
"Bus 004 Device 002: ID 0cf3:3000 Atheros Communications, Inc. AR3011 Bluetooth (no firmware)"

dmesg shows the following:
"[ 31.004756 < 0.852144>] Bluetooth: Core ver 2.16
[ 31.004782 < 0.000026>] NET: Registered protocol family 31
[ 31.004784 < 0.000002>] Bluetooth: HCI device and connection manager initialized
[ 31.004787 < 0.000003>] Bluetooth: HCI socket layer initialized
[ 31.004788 < 0.000001>] Bluetooth: L2CAP socket layer initialized
[ 31.004796 < 0.000008>] Bluetooth: SCO socket layer initialized
[ 31.019729 < 0.014933>] Bluetooth: Atheros AR30xx firmware driver ver 1.0
[ 36.075359 < 5.055630>] Bluetooth: Can't change to loading configuration err
[ 36.075468 < 0.000109>] ath3k: probe of 4-2:1.0 failed with error -110
[ 36.075494 < 0.000026>] usbcore: registered new interface driver ath3k
"

Disconnecting & reconnecting the dongle shows the following in dmesg (the bluetooth icon appears at this point, but still doesn't detect any usable bluetooth device):
"[ 1366.346593 < 1311.823246>] usb 4-2: USB disconnect, device number 2
[ 1388.743240 < 22.396647>] usb 4-2: new full speed USB device number 3 using uhci_hcd
[ 1389.346623 < 0.603383>] usb 4-2: USB disconnect, device number 3
[ 1390.823235 < 1.476612>] usb 4-2: new full speed USB device number 4 using uhci_hcd
[ 1390.997394 < 0.174159>] Bluetooth: Generic Bluetooth USB driver ver 0.6
[ 1391.022233 < 0.024839>] usbcore: registered new interface driver btusb
"


Steps to reproduce:
1. Stick ASUS USB-BT211 usb bluetooth dongle into PC/laptop/whatever running archlinux
2. Attempt to boot (will hang)

or

1. Boot up system
2. Stick dongle into system (will not initialize properly and consequently doesn't work)
This task depends upon

Closed by  Tobias Powalowski (tpowa)
Wednesday, 12 September 2012, 06:25 GMT
Reason for closing:  Fixed
Comment by none given (hoban) - Wednesday, 04 January 2012, 16:57 GMT
After some more playing around with this, I was able to get the device to be detected after restarting the bluetooth service. After doing so, I still have to manually connect to the trackpad each time.
Full dmesg: http://pastie.org/3125809
Note that the device is no longer being detected as an ath3k device, but rather loads the btusb driver.
There is still a bug here since some guesswork was needed to get it working:
1. Boot PC _without_ dongle inserted
2. Insert dongle
3. Remove dongle
4. Insert dongle
5. Restart bluetooth service
6. Device now shows up in gnome bluetooth applet/configuration window and also via hci* tools

I was able to reboot, then just duplicate steps 5,6 to get a connection with my trackpad but I wonder why steps 1-4 were initially required...
Comment by Allan McRae (Allan) - Saturday, 02 June 2012, 13:04 GMT
Status?
Comment by none given (hoban) - Monday, 04 June 2012, 15:44 GMT
This is still an issue, as described.
After the partial fix detailed above, the boot process no longer halts. However, a bluetooth service restart is still required to activate bluetooth and see other devices, but pairing still fails.
If you'd like any additional details, please let me know.
Thanks.
Comment by Jelle van der Waa (jelly) - Monday, 10 September 2012, 18:37 GMT
Any update?
Comment by none given (hoban) - Tuesday, 11 September 2012, 19:40 GMT
Last time I checked (a couple weeks ago I think), the issue still existed. I've reinstalled that workstation with a different flavor of Linux so I cannot perform further testing at this time.

Loading...