Bluetooth: can't load firmware, may not work correctly

[uellue]

Bluetooth does not work. The tray icon appears, but none of the functionality is available. Probable cause:
The firmware for Bus 001 Device 003: ID 0a5c:21e6 Broadcom Corp. BCM20702 Bluetooth 4.0 [ThinkPad] does not load. The message in dmesg is "Bluetooth: can't load firmware, may not work correctly". The problem appeared after upgrading from the previous LTS version (12.04?).

ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: linux-image-3.13.0-44-generic 3.13.0-44.73
ProcVersionSignature: Ubuntu 3.13.0-44.73-generic 3.13.11-ckt12
Uname: Linux 3.13.0-44-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: weber 2408 F.... pulseaudio
                      weber 2744 F.... pulseaudio
CurrentDesktop: KDE
Date: Sat Dec 27 22:58:37 2014
HibernationDevice: RESUME=UUID=4dd72213-9a42-4532-aa22-2ccc72d46062
InstallationDate: Installed on 2012-07-21 (889 days ago)
InstallationMedia: Kubuntu 12.04 LTS "Precise Pangolin" - Release amd64 (20120423)
MachineType: LENOVO 2320CTO
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.13.0-44-generic root=UUID=a58cd4c1-52b5-4b88-b5a8-3bf530c20c4a ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.13.0-44-generic N/A
 linux-backports-modules-3.13.0-44-generic N/A
 linux-firmware 1.127.11
SourcePackage: linux
UpgradeStatus: Upgraded to trusty on 2014-12-26 (1 days ago)
dmi.bios.date: 05/24/2012
dmi.bios.vendor: LENOVO
dmi.bios.version: G2ET31WW (1.11 )
dmi.board.asset.tag: Not Available
dmi.board.name: 2320CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Not Available
dmi.modalias: dmi:bvnLENOVO:bvrG2ET31WW(1.11):bd05/24/2012:svnLENOVO:pn2320CTO:pvrThinkPadX230:rvnLENOVO:rn2320CTO:rvrNotAvailable:cvnLENOVO:ct10:cvrNotAvailable:
dmi.product.name: 2320CTO
dmi.product.version: ThinkPad X230
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[uellue (dieter-uellue)]

Hi Christopher,

the behavior is unchanged after the BIOS upgrade.

sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
G2ETA2WW (2.62 )
09/12/2014

I did the BIOS upgrade with the Windows utility. Other than not having any noticeable effect on Bluetooth, it worked.

Just a question, what is the reason behind setting the importance to low? This bug makes an important feature of my computer unusable after an upgrade from one LTS version to another. If it was broken before, I'd understand. But Bluetooth used to work perfectly before. I am quite frustrated about this bug because I've been using Bluetooth quite a bit.

[penalvch (penalvch)]

uellue, could you please test the latest upstream kernel available from the very top line at the top of the page (the release names are irrelevant for testing, and please do not test the daily folder) following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue.

If the test did not allow you to test to the issue (ex. you couldn't boot into the OS) please make a comment in your report about this, and continue to test the next most recent kernel version until you can test to the issue. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested exactly shown as:
kernel-fixed-upstream-3.19-rc1

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description.

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

[Brad Figg (brad-figg)]

This change was made by a bot.

[uellue (dieter-uellue)]

Hi Christopher,

With kernel 3.19-rc1, Bluetooth still does not work. However, the behavior changed. This is what dmesg shows after unloading and loading btusb:

[ 1058.704086] usbcore: deregistering interface driver btusb
[ 1058.752148] usbcore: registered new interface driver btusb
[ 1058.761677] bluetooth hci0: Direct firmware load for brcm/BCM20702A0-0a5c-21e6.hcd failed with error -2
[ 1058.761683] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e6.hcd not found

I've also installed the latest firmware package https://launchpad.net/ubuntu/+source/linux-firmware/1.140/+build/6640596

[penalvch (penalvch)]

uellue, just to advise, it is most difficult to analyze the results when one changes more than what was requested (in this case both the kernel version and firmware).

Hence, could you please test 3.19-rc1 (with the default firmware) and then advise to the results?

[uellue (dieter-uellue)]

Hi Christopher,

the behavior is the same with both versions of linux-firmware.

[penalvch (penalvch)]

uellue, could you please advise the kernel version you were using when this was not reproducible in Precise (ex. 3.2.x, 3.5.x, 3.8.x, 3.11.x, or 3.13.x)?

[uellue (dieter-uellue)]

Hi Christopher,

the kernel version was 3.2.0-75-generic

Greetings,
Dieter

[penalvch (penalvch)]

uellue, if you boot back into 3.2.0-75-generic does bluetooth begin to work again?

[uellue (dieter-uellue)]

Hi Christopher,

with the old kernel it works even less: It doesn't find the device anymore and the btusb kernel module is somehow blocked so that I cannot unload it. With the new kernel it finds the device, but no operation works on it.

Greetings,
Dieter

[penalvch (penalvch)]

uellue, ok, so this indicates that this isn't a linux (Ubuntu) kernel regression, but in some other package. Next, could you please return back to the default kernel, install the firmware from Precise (1.79.18, or whichever earlier version from that you know worked), and advise if the bluetooth begins to work?

[uellue (dieter-uellue)]

Hi Christopher,

I have a feeling that the bluetooth device can preserve state when rebooting, unless I take out the battery for a moment. In particular, it can lock up. I have a feeling that firmware problems can cause that.

As a crosscheck, I've confirmed that everything works on Windows.

Changing the version of linux-firmware leads to the following result:

- Bluetooth GUI does not find the bluetooth device anymore

dmesg shows

[ 3003.856473] usbcore: deregistering interface driver btusb
[ 3003.858704] Bluetooth: hci0 urb ffff8800afd83cc0 failed to resubmit (2)
[ 3003.876244] usbcore: registered new interface driver btusb
[ 3003.876290] usb 1-1.4: Direct firmware load failed with error -2
[ 3003.876299] usb 1-1.4: Falling back to user helper
[ 3003.878871] Bluetooth: can't load firmware, may not work correctly

 I've reverted back to the current firmware. Unloading and loading the btusb module yields the same result. Then I've power-cycled the computer including taking out the battery. The device is displayed again in the GUI. This is now the log entry when unloading and loading btusb:

[ 339.399902] usbcore: deregistering interface driver btusb
[ 339.415214] usb 1-1.4: Direct firmware load failed with error -2
[ 339.415221] usb 1-1.4: Falling back to user helper
[ 339.415319] usbcore: registered new interface driver btusb
[ 339.416192] Bluetooth: can't load firmware, may not work correctly

This is the log message when stopping and starting bluetoothd with sudo service bluetooth restart, does that tell you something?

Dec 29 09:52:03 herb bluetoothd[2824]: Terminating
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSink
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSink
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/A2DPSource
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/A2DPSource
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/HFPAG
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.67 path=/MediaEndpoint/HFPHS
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/HFPAG
Dec 29 09:52:03 herb bluetoothd[2824]: Endpoint unregistered: sender=:1.57 path=/MediaEndpoint/HFPHS
Dec 29 09:52:03 herb bluetoothd[2824]: Stopping SDP server
Dec 29 09:52:03 herb bluetoothd[2824]: Exit
Dec 29 09:52:03 herb NetworkManager[868]: <info> BT device 00:1E:A3:DA:C5:BF removed
Dec 29 09:52:03 herb NetworkManager[868]: <info> (00:1E:A3:DA:C5:BF): device state change: disconnected -> unmanaged (reason 'removed') [30 10 36]
Dec 29 09:52:03 herb NetworkManager[868]: <info> (00:1E:A3:DA:C5:BF): cleaning up...
Dec 29 09:52:03 herb NetworkManager[868]: <info> (00:1E:A3:DA:C5:BF): taking down device.
Dec 29 09:52:03 herb bluez: Stopping uarts
Dec 29 09:52:03 herb bluez: Stopping rfcomm
Dec 29 09:52:03 herb bluetoothd[3010]: Bluetooth daemon 4.101
Dec 29 09:52:03 herb bluetoothd[3010]: Starting SDP server
Dec 29 09:52:03 herb bluetoothd[3010]: DIS cannot...

[penalvch (penalvch)]

uellue, if it works in Windows, then it clearly would be a Ubuntu versus a hardware fault. As well, if you have to play all these games of pulling out a battery, rebooting, etc. to get it to work in Ubuntu, it would appear to be some wonky timing issue.

Despite this, in order to further narrow the offending package (ex. is this an issue occurring with a specific kernel, firmware, and userspace combination) would it be possible for you to create another partition, install Precise 12.04.1 via http://old-releases.ubuntu.com/releases/12.04.1/ubuntu-12.04.1-desktop-amd64.iso , and fully update (be sure not to upgrade the kernel as per the enablement stack upgrade outlined in https://wiki.ubuntu.com/Kernel/LTSEnablementStack), and advise if the bluetooth still works?

If so, could you please install just the firmware from Trusty to see if it still works?

[uellue (dieter-uellue)]

Dear Christopher,

thank you for your patience and help. If I need to install an old Ubuntu version in another partition to (maybe) fix this bug, I found actually an easier way to use Bluetooth on my laptop: I am switching to Windows 7 as the primary operating system and put Ubuntu or maybe another distribution in a virtual machine. In that sense, the bug is fixed for me now.

Best regards,
Dieter

[penalvch (penalvch)]

Not Fix Released as outlined in https://wiki.ubuntu.com/Bugs/Status .

[Lorn Potter (lorn-potter)]

I updated yesterday and this bug effects me (lenovo x1 carbon 1st gen). I have no bluetooth now.

dmesg:

[ 73.111498] usb 1-1.4: new full-speed USB device number 7 using ehci-pci
[ 73.207595] usb 1-1.4: New USB device found, idVendor=0a5c, idProduct=21e6
[ 73.207604] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 73.207608] usb 1-1.4: Product: BCM20702A0
[ 73.207612] usb 1-1.4: Manufacturer: Broadcom Corp
[ 73.207616] usb 1-1.4: SerialNumber: 8056F2FFB1FA
[ 73.209867] bluetooth hci0: Direct firmware load failed with error -2
[ 73.209878] bluetooth hci0: Falling back to user helper
[ 73.212195] Bluetooth: hci0: BCM: patch brcm/BCM20702A0-0a5c-21e6.hcd not found
[ 73.300017] Bluetooth: HIDP (Human Interface Emulation) ver 1.2
[ 73.300028] Bluetooth: HIDP socket layer initialized
[ 73.426930] usb 1-1.4: USB disconnect, device number 7

[penalvch (penalvch)]

Lorn Potter, thank you for your comment. So your issue may be dealt with as soon as possible, and so your hardware may be tracked by having necessary debugging information automatically attached, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu repository kernel via:
ubuntu-bug linux

For more on why this is most helpful, please read the official Ubuntu documentation from the respective Ubuntu developer groups, and triage teams:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies
https://wiki.ubuntu.com/Kernel/Policies/DuplicateBugs
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

[Yota (me-michaschwab)]

I've been affected by this exact bug for over a year and have not been able to use bluetooth.
dmesg:

[ 3.353578] Bluetooth: Core ver 2.21
[ 3.353593] Bluetooth: HCI device and connection manager initialized
[ 3.353596] Bluetooth: HCI socket layer initialized
[ 3.353598] Bluetooth: L2CAP socket layer initialized
[ 3.353605] Bluetooth: SCO socket layer initialized
[ 3.363019] Bluetooth: hci0: BCM: chip id 63
[ 3.379130] Bluetooth: hci0: BCM20702A
[ 3.380049] Bluetooth: hci0: BCM20702A1 (001.002.014) build 0000
[ 3.386656] bluetooth hci0: Direct firmware load for brcm/BCM20702A1-0a5c-216f.hcd failed with error -2
[ 3.386659] Bluetooth: hci0: BCM: Patch brcm/BCM20702A1-0a5c-216f.hcd not found
[ 4.637831] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.637834] Bluetooth: BNEP filters: protocol multicast
[ 4.637839] Bluetooth: BNEP socket layer initialized

[penalvch (penalvch)]

Yota, it will help immensely if you filed a new report with the Ubuntu repository kernel (not mainline/upstream) via a terminal:
ubuntu-bug linux

Please feel free to subscribe me to it.

For more on why this is helpful, please see https://wiki.ubuntu.com/ReportingBugs.