[Dell Latitude E5550] Atheros Bluetooth [0cf3:e005] gone after suspend

Bug #1381906 reported by Po-Hsu Lin
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
HWE Next
Confirmed
Medium
Adam Lee
linux (Ubuntu)
Confirmed
Medium
Adam Lee

Bug Description

CID: 201406-15271 Dell Latitude E5550

After S3, the Bluetooth indicator will grey out (stays at the "OFF" state), but rfkill show it's not blocked.

Even enable it by changing it to the "ON" state does not help, can't find any device with it, hciconfig return nothing.

Error message could be found in the dmesg output:
[ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906
[ 8996.779570] Bluetooth: Loading sysconfig file failed

More important part is that after reboot, the Bluetooth will disappear as it never exist, won't be listed in lsusb and dmesg.

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-37-generic 3.13.0-37.64
ProcVersionSignature: Ubuntu 3.13.0-37.64-generic 3.13.11.7
Uname: Linux 3.13.0-37-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.5
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: ubuntu 1726 F.... pulseaudio
 /dev/snd/controlC1: ubuntu 1726 F.... pulseaudio
CRDA:
 country TW:
  (2402 - 2472 @ 40), (3, 27)
  (5270 - 5330 @ 40), (3, 17), DFS
  (5735 - 5815 @ 40), (3, 30)
CurrentDesktop: Unity
Date: Thu Oct 16 00:41:31 2014
HibernationDevice: RESUME=UUID=02cbc1f1-a261-484c-8fc2-05b68f73446d
InstallationDate: Installed on 2014-10-09 (6 days ago)
InstallationMedia: Ubuntu 14.04.1 LTS "Trusty Tahr" - Release amd64 (20140722.2)
MachineType: Dell Inc. Latitude E5550
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-37-generic root=UUID=d3b20ae5-9ff8-49b3-b640-1c6a9f264710 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-37-generic N/A
 linux-backports-modules-3.13.0-37-generic N/A
 linux-firmware 1.127.7
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 07/25/2014
dmi.bios.vendor: Dell Inc.
dmi.bios.version: T43
dmi.board.name: 0141B2
dmi.board.vendor: Dell Inc.
dmi.board.version: X02
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrT43:bd07/25/2014:svnDellInc.:pnLatitudeE5550:pvr01:rvnDellInc.:rn0141B2:rvrX02:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E5550
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

After the Bluetooth is gone, boot it with a LiveUSB and reboot normally could bring it back.

Revision history for this message
Brad Figg (brad-figg) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Rik Mills (rikmills) wrote :

[ 8996.779551] Bluetooth: Error in firmware loading err = -110,len = 448, size = 1906
[ 8996.779570] Bluetooth: Loading sysconfig file failed
[ 8996.779587] ath3k: probe of 2-3:1.0 failed with error -110

That is a common problem with a range of these ath3k cards. I have one. Have a search of previous bug reports, but there seems a lack of any real solution for the majority of them.

Some say it can be a conflict on loading od usb3 driver, and/or an alternative firmware loading method is needed but has not been adopted. Bit of a mess really.

Revision history for this message
Anthony Wong (anthonywong) wrote :

@PHLin
This should be the infamous xHCI incompatibility issue.
Can you try the following command as root and verify if it can fix it?
  /usr/bin/setpci -s 00:14 d0.w=0x01db

Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in hwe-next:
status: New → Incomplete
Revision history for this message
Po-Hsu Lin (cypressyew) wrote :

Hello Anthony,
The command can't fix it, tested with the following steps:
1. sudo /usr/bin/setpci -s 00:14 d0.w=0x01db
2. Suspend
3. Wake it up and check the BT status

The Bluetooth indicator will grey out (stays at the "OFF" state), but rfkill show it's not blocked.

rfkill before S3:
ubuntu@201406-15271:~$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no
4: hci0: Bluetooth
 Soft blocked: no
 Hard blocked: no

rfkill after S3:
ubuntu@201406-15271:~$ rfkill list
0: phy0: Wireless LAN
 Soft blocked: no
 Hard blocked: no
1: dell-wifi: Wireless LAN
 Soft blocked: no
 Hard blocked: no
2: dell-bluetooth: Bluetooth
 Soft blocked: no
 Hard blocked: no

Changed in hwe-next:
status: Incomplete → Confirmed
Changed in linux (Ubuntu):
status: Incomplete → Confirmed
Changed in hwe-next:
assignee: nobody → Adam Lee (adam8157)
Changed in linux (Ubuntu):
assignee: Anthony Wong (anthonywong) → Adam Lee (adam8157)
Changed in hwe-next:
importance: Undecided → Medium
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.