0489:e062 [Sony VAIO SVF1531C5E] Bluetooth adapter does not see BT devices

[Miguel Barrio Orsikowsky]

The Bluetooth adapter is detected and apparently working but, when choosing "Configure a new device", the device list is always empty (it cannot see any BT device around).

But, if I boot into Windows 8 just before booting into Ubuntu, the adapter works perfectly and it sees all BT devices. It seems the Windows 8 driver is performing some activation to the BT adapter.

Test case:
Step 1: power on the Sony VAIO SVF1531C5E and boot into Ubuntu 14.04.1.
Step 2: type "dmesg | grep Bluetooth" and look at the output. Notice the timeout error shown at the end:
[ 15.691891] Bluetooth: Core ver 2.19
[ 15.691912] Bluetooth: HCI device and connection manager initialized
[ 15.691918] Bluetooth: HCI socket layer initialized
[ 15.691920] Bluetooth: L2CAP socket layer initialized
[ 15.691926] Bluetooth: SCO socket layer initialized
[ 19.571783] Bluetooth: RFCOMM TTY layer initialized
[ 19.571794] Bluetooth: RFCOMM socket layer initialized
[ 19.571799] Bluetooth: RFCOMM ver 1.11
[ 19.619432] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.619435] Bluetooth: BNEP filters: protocol multicast
[ 19.619442] Bluetooth: BNEP socket layer initialized
[ 21.772160] Bluetooth: hci0 command 0x1003 tx timeout

Step 3: try to list BT devices by clicking on the bluetooth icon at the top right of the screen and then selecting "Configure a new device". The device's list will be empty: it should list all bluetooth-enabled devices around.
Step 4: reboot the laptop and boot into a Windows partition (mine is Windows 8.1).
Step 5: wait until it is completely booted, then just reboot.
Step 6: boot into Ubuntu again.
Step 7: type "dmesg | grep Bluetooth" and look at the output. This time there is no "hci0 command 0x1003 tx timeout" message at the end:
[ 15.569891] Bluetooth: Core ver 2.19
[ 15.569911] Bluetooth: HCI device and connection manager initialized
[ 15.569918] Bluetooth: HCI socket layer initialized
[ 15.569921] Bluetooth: L2CAP socket layer initialized
[ 15.569930] Bluetooth: SCO socket layer initialized
[ 19.571790] Bluetooth: RFCOMM TTY layer initialized
[ 19.571801] Bluetooth: RFCOMM socket layer initialized
[ 19.571806] Bluetooth: RFCOMM ver 1.11
[ 19.719275] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 19.719278] Bluetooth: BNEP filters: protocol multicast
[ 19.719285] Bluetooth: BNEP socket layer initialized

Step 8: try to list BT devices around by clicking on the bluetooth icon at the top right of the screen, and then selecting "Configure a new device". The device's list will have all the bluetooth devices around, and you will be able to pair them perfectly.

---
ApportVersion: 2.14.1-0ubuntu3.6
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC1: miguel 2186 F.... pulseaudio
 /dev/snd/controlC0: miguel 2186 F.... pulseaudio
CurrentDesktop: Unity
DistroRelease: Ubuntu 14.04
HibernationDevice: RESUME=UUID=19591455-b4a8-4b36-bc7b-49e40cf355c6
InstallationDate: Installed on 2014-05-02 (240 days ago)
InstallationMedia: Ubuntu 14.04 LTS "Trusty Tahr" - Release amd64 (20140417)
MachineType: Sony Corporation SVF1531C5E
NonfreeKernelModules: wl
Package: linux (not installed)
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-28-generic.efi.signed root=UUID=1a77fe11-c859-4770-9521-cfdd15c24c84 ro quiet splash vt.handoff=7
ProcVersionSignature: Ubuntu 3.16.0-28.38~14.04.1-generic 3.16.7-ckt1
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-28-generic N/A
 linux-backports-modules-3.16.0-28-generic N/A
 linux-firmware 1.127.10
Tags: trusty
Uname: Linux 3.16.0-28-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo vboxusers
_MarkForUpload: True
dmi.bios.date: 11/18/2013
dmi.bios.vendor: Insyde Corp.
dmi.bios.version: R0210DB
dmi.board.asset.tag: N/A
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.asset.tag: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnInsydeCorp.:bvrR0210DB:bd11/18/2013:svnSonyCorporation:pnSVF1531C5E:pvrC10JZZKE:rvnSonyCorporation:rnVAIO:rvrN/A:cvnSonyCorporation:ct10:cvrN/A:
dmi.product.name: SVF1531C5E
dmi.product.version: C10JZZKE
dmi.sys.vendor: Sony Corporation

[penalvch (penalvch)]

Miguel Barrio Orsikowsky, thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command, as it will automatically gather debugging information, in a terminal:
apport-collect 1406106

[Miguel Barrio Orsikowsky (megamik79)]

This issue is also present when booting an up-to-date Ubuntu 14.04.1 official kernel (version 3.13).

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[Miguel Barrio Orsikowsky (megamik79)]

apport information

[penalvch (penalvch)]

Miguel Barrio Orsikowsky, 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-rc2

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.

[Miguel Barrio Orsikowsky (megamik79)]

I have tested this issue against the latest upstream kernel available and it is still NOT fixed:

Kernel packages installed and used:

linux-headers-3.19.0-031900rc2_3.19.0-031900rc2.201412290135_all.deb
linux-headers-3.19.0-031900rc2-generic_3.19.0-031900rc2.201412290135_amd64.deb
linux-image-3.19.0-031900rc2-generic_3.19.0-031900rc2.201412290135_amd64.deb

miguel@vaio:~$ uname -a
Linux vaio 3.19.0-031900rc2-generic #201412290135 SMP Mon Dec 29 01:36:54 UTC 2014 x86_64 x86_64 x86_64 GNU/Linux

[penalvch (penalvch)]

Miguel Barrio Orsikowsky, could you please unplug all USB devices from your computer, plug in only the problematic USB device, immediately place the following in a terminal and attach the uncompressed and untarred results:
lsusb -v > lsusb-v.txt
usb-devices -v > usb-devices.txt

[Miguel Barrio Orsikowsky (megamik79)]

BT adapter part of lsusb -v output:

T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2 Spd=12 MxCh= 0
D: Ver= 2.00 Cls=ff(vend.) Sub=01 Prot=01 MxPS=64 #Cfgs= 1
P: Vendor=0489 ProdID=e062 Rev=01.12
S: Manufacturer=Broadcom Corp
S: Product=BCM43142A0
S: SerialNumber=3C77E6DC7494
C: #Ifs= 4 Cfg#= 1 Atr=e0 MxPwr=0mA
I: If#= 0 Alt= 0 #EPs= 3 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 1 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=01 Prot=01 Driver=btusb
I: If#= 2 Alt= 0 #EPs= 2 Cls=ff(vend.) Sub=ff Prot=ff Driver=(none)
I: If#= 3 Alt= 0 #EPs= 0 Cls=fe(app. ) Sub=01 Prot=01 Driver=(none)

[Miguel Barrio Orsikowsky (megamik79)]

I made a mistake in my last comment: the pasted text was not from lsusb -v output but from usb-devices instead.

[penalvch (penalvch)]

Miguel Barrio Orsikowsky, the issue you are reporting is an upstream one. Could you please report this problem to the appropriate mailing list (linux-bluetooth) by following the instructions verbatim at https://wiki.ubuntu.com/Bugs/Upstream/kernel ?

Please provide a direct URL to your e-mail to the mailing list once you have made it so that it may be tracked via http://vger.kernel.org/vger-lists.html . It can take a day for the new e-mail to show up in the respective archive.

Thank you for your understanding.

[Miguel Barrio Orsikowsky (megamik79)]

This is the thread in linux-bluetooth mail list:

http://www.spinics.net/lists/linux-bluetooth/msg57488.html

[penalvch (penalvch)]

Miguel Barrio Orsikowsky, please ensure you respond to the followup information requested noted in http://www.spinics.net/lists/linux-bluetooth/msg57489.html . They are looking for the results of:
sudo cat /sys/kernel/debug/usb/devices

[Miguel Barrio Orsikowsky (megamik79)]

It is actually responded, but the web page seems to take a day or two to catch up.

[Jeremy (wa113y3s)]

From the windows bcbtums-win8x64-brcm.inf file the .hex file you need is BCM43142A0_001.001.011.0197.0201.hex
and you need the hex2hcd from git clone git://github.com/jessesung/hex2hcd.git to convert the hex to a hcd file that may need to be /lib/firmware/fw-0489_e062.hcd

[Miguel Barrio Orsikowsky (megamik79)]

Thank you for your advice, Jeremy. After some research (please look at http://www.spinics.net/lists/linux-bluetooth/msg57515.html) I end up with the firmware correctly loaded from a file called BCM43142A0-0489-e062.hcd. But even this way, I need to reboot Linux several times in order to get the BT adapter fully working. Sometimes I get lucky and it works at the very first try, but it does not happen very often.

Marcel Holtmann (kernel maintainer for the BT module) suggests in http://www.spinics.net/lists/linux-bluetooth/msg57523.html that I can try increasing HCI_INIT_TIMEOUT in the kernel, but unfortunately I have no time to do more experiments by now.