Dell bluetooth adapters don't return to HCI mode after suspend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OEM Priority Project |
Fix Released
|
Undecided
|
Unassigned | ||
bluez (Ubuntu) |
Fix Released
|
Undecided
|
Mario Limonciello | ||
Jaunty |
Fix Released
|
Undecided
|
Mario Limonciello | ||
udev (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned | ||
udev-extras (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Jaunty |
Invalid
|
Undecided
|
Unassigned |
Bug Description
--Impact--
Newer dell bluetooth adapters don't work after flipping on/off the hardware switch or after S3
--Addressing--
The development branch for karmic hasn't been opened yet, but this patch will be forward-ported when it is. The patch is to a file in debian/ so it doesn't need to go upstream.
--Test Case--
1) Find a machine with one of the following devices on the USB bus:
Vendor ID / Product ID / Model
0x413c / 0x8154 / Dell BT 410
0x413c / 0x8158 / Dell BT 370
0x413c / 0x8162 / Dell BT 365
2) Attempt to suspend to RAM. When resuming, observe that there is no bluetooth icon in the tray.
3) Upgrade to the proposed package
4) If the bluetooth icon isn't in the tray to start (depending on if the bluetooth service got restarted during the package upgrade) run
$ sudo hid2hci --tohci
to get it in the right state.
5) Attempt to suspend to RAM. When resuming, observe that there is now a bluetooth icon still in the tray.
--Regression Potential--
None. This rule is only used on Dell BT adapters, and the existing rule does not work w/ the udev in Jaunty.
description: | updated |
description: | updated |
Changed in oem-priority: | |
status: | New → Fix Released |
tags: |
added: verification-done removed: verification-needed |
Changed in udev-extras (Ubuntu Jaunty): | |
status: | New → Invalid |
Changed in bluez (Ubuntu): | |
status: | Fix Released → In Progress |
status: | In Progress → Fix Committed |
Changed in oem-priority: | |
status: | Fix Released → Confirmed |
Changed in somerville: | |
status: | New → Invalid |
no longer affects: | dell |
I get the following dmesg when disabling the hardware switch:
[ 790.570143] iwlagn: Radio Frequency Kill Switch is On:
[ 790.570149] Kill switch must be turned off for wireless networking to work.
[ 790.792348] usb 1-1: USB disconnect, address 10
[ 790.792356] usb 1-1.1: USB disconnect, address 11
[ 790.804352] usb 1-1.2: USB disconnect, address 12
[ 793.897099] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
[ 793.897114] mac80211-phy0: failed to remove key (0, 02:10:18:01:00:01) from hardware (-5)
[ 793.897215] wlan0: disassociating by local choice (reason=3)
[ 793.927564] iwlagn: Error sending REPLY_ADD_STA: enqueue_hcmd failed: -5
[ 793.927577] mac80211-phy0: failed to remove key (1, ff:ff:ff:ff:ff:ff) from hardware (-5)
And this when enabling: pci0000: 00/0000: 00:1a.0/ usb1/1- 1/1-1.1/ 1-1.1:1. 0/input/ input19 8157.0008: input,hidraw1: USB HID v1.11 Keyboard [HID 413c:8157] on usb-0000: 00:1a.0- 1.1/input0 pci0000: 00/0000: 00:1a.0/ usb1/1- 1/1-1.2/ 1-1.2:1. 0/input/ input20 8158.0009: input,hidraw2: USB HID v1.11 Mouse [HID 413c:8158] on usb-0000: 00:1a.0- 1.2/input0 NETDEV_ UP): wlan0: link is not ready NETDEV_ CHANGE) : wlan0: link becomes ready
[ 835.612312] usb 1-1: new full speed USB device using uhci_hcd and address 13
[ 835.793465] usb 1-1: configuration #1 chosen from 1 choice
[ 835.796747] hub 1-1:1.0: USB hub found
[ 835.799049] hub 1-1:1.0: 3 ports detected
[ 836.083190] usb 1-1.1: new full speed USB device using uhci_hcd and address 14
[ 836.209624] usb 1-1.1: configuration #1 chosen from 1 choice
[ 836.229575] input: HID 413c:8157 as /devices/
[ 836.265034] generic-usb 0003:413C:
[ 836.347700] usb 1-1.2: new full speed USB device using uhci_hcd and address 15
[ 836.475948] usb 1-1.2: configuration #1 chosen from 1 choice
[ 836.514721] input: HID 413c:8158 as /devices/
[ 836.525117] generic-usb 0003:413C:
[ 838.730578] Registered led device: iwl-phy0:radio
[ 838.730618] Registered led device: iwl-phy0:assoc
[ 838.730655] Registered led device: iwl-phy0:RX
[ 838.730690] Registered led device: iwl-phy0:TX
[ 838.747892] ADDRCONF(
[ 838.753048] wlan0: direct probe to AP 00:1e:2a:23:e4:c6 try 1
[ 838.911655] wlan0 direct probe responded
[ 838.911667] wlan0: authenticate with AP 00:1e:2a:23:e4:c6
[ 839.071618] wlan0: authenticated
[ 839.071629] wlan0: associate with AP 00:1e:2a:23:e4:c6
[ 839.231864] wlan0: RX AssocResp from 00:1e:2a:23:e4:c6 (capab=0x401 status=0 aid=1)
[ 839.231872] wlan0: associated
[ 839.233877] phy0: failed to restore operational channel after scan
[ 839.234341] ADDRCONF(
[ 839.234551] wlan0: disassociating by local choice (reason=3)
[ 849.896074] wlan0: no IPv6 routers present
[ 866.107266] wlan0: authenticate with AP 02:10:18:01:00:01
[ 866.109267] wlan0: authenticate with AP 02:10:18:01:00:01
[ 866.111478] wlan0: authenticated
[ 866.111485] wlan0: associate with AP 02:10:18:01:00:01
[ 866.114943] wlan0: RX AssocResp from 02:10:18:01:00:01 (capab=0x411 status=0 aid=3)
[ 866.114950] wlan0: associated
Now if I run hcitool scan I have this output:
Device is not available: No such device
When I do a /etc/init. d/bluetooth restart I get this dmesg:
[ 964.529392] usb 1-1.2: ...