Lenovo Y700-17ISK: Bluetooth issues

[aljosa]

After installing and updating Xenial, dmesg notes:
[ 2.253211] Bluetooth: hci0: Failed to send firmware data (-38)
[ 4.250058] Bluetooth: hci0 command 0xfc05 tx timeout
[ 9.135505] Bluetooth: hci0: Reading Intel version information failed (-19)
[ 10.926411] Bluetooth: hci0: Setting Intel event mask failed (-16)

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: linux-image-4.4.0-10-generic 4.4.0-10.25
ProcVersionSignature: Ubuntu 4.4.0-10.25-generic 4.4.3
Uname: Linux 4.4.0-10-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: aljosa 1776 F.... pulseaudio
CurrentDesktop: Unity
Date: Sun Mar 6 11:31:12 2016
HibernationDevice: RESUME=UUID=ac022671-63df-40ae-bffe-66fff3b35125
InstallationDate: Installed on 2016-03-05 (0 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160304)
MachineType: LENOVO 80Q0
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-10-generic.efi.signed root=UUID=aa4325c4-4b4c-4372-b8ca-a66c3e5b2aa6 ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-4.4.0-10-generic N/A
 linux-backports-modules-4.4.0-10-generic N/A
 linux-firmware 1.156
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 01/31/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: CDCN30WW
dmi.board.asset.tag: NO Asset Tag
dmi.board.name: Allsparks 7A
dmi.board.vendor: LENOVO
dmi.board.version: NO DPK
dmi.chassis.asset.tag: NO Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: Lenovo ideapad Y700-17ISK
dmi.modalias: dmi:bvnLENOVO:bvrCDCN30WW:bd01/31/2016:svnLENOVO:pn80Q0:pvrLenovoideapadY700-17ISK:rvnLENOVO:rnAllsparks7A:rvrNODPK:cvnLENOVO:ct10:cvrLenovoideapadY700-17ISK:
dmi.product.name: 80Q0
dmi.product.version: Lenovo ideapad Y700-17ISK
dmi.sys.vendor: LENOVO

[Brad Figg (brad-figg)]

This change was made by a bot.

[Alberto Salvia Novella (es20490446e)]

Please:

1. Edit the report description, so it explains which steps you followed to recreate the bug and which are the consequences of it.
2. Set this report status back to "confirmed".

[penalvch (penalvch)]

aljosa, thank you for reporting this and helping make Ubuntu better.

To clarify, can you actually use bluetooth successfully?

[penalvch (penalvch)]

aljosa, in order to properly scope the impact, could you please test the bluetooth functionality and report back?

[aljosa (aljosa-p)]

Today I turned on my notebook and everything was somehow ok inside dmesg related to bluetooth. After that I turned off-on for some 15 times - every time with bluetooth error.

Bluetooth turned on inside Ubuntu settings:

dmesg | grep -i bluetooth
[ 1.732360] Bluetooth: Core ver 2.21
[ 1.732371] Bluetooth: HCI device and connection manager initialized
[ 1.732373] Bluetooth: HCI socket layer initialized
[ 1.732375] Bluetooth: L2CAP socket layer initialized
[ 1.732380] Bluetooth: SCO socket layer initialized
[ 1.743346] Bluetooth: hci0: Firmware revision 0.0 build 90 week 25 2015
[ 1.848901] Bluetooth: HCI UART driver ver 2.3
[ 1.848904] Bluetooth: HCI UART protocol H4 registered
[ 1.848906] Bluetooth: HCI UART protocol BCSP registered
[ 1.848907] Bluetooth: HCI UART protocol LL registered
[ 1.848908] Bluetooth: HCI UART protocol ATH3K registered
[ 1.848909] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 1.848932] Bluetooth: HCI UART protocol Intel registered
[ 1.848945] Bluetooth: HCI UART protocol BCM registered
[ 1.848946] Bluetooth: HCI UART protocol QCA registered
[ 2.831762] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 2.831764] Bluetooth: BNEP filters: protocol multicast
[ 2.831768] Bluetooth: BNEP socket layer initialized
[ 4.928101] Bluetooth: RFCOMM TTY layer initialized
[ 4.928178] Bluetooth: RFCOMM socket layer initialized
[ 4.928182] Bluetooth: RFCOMM ver 1.11

Bluetooth turned off inside Ubuntu settings:

dmesg | grep -i bluetooth
[ 1.874571] Bluetooth: Core ver 2.21
[ 1.874584] Bluetooth: HCI device and connection manager initialized
[ 1.874587] Bluetooth: HCI socket layer initialized
[ 1.874589] Bluetooth: L2CAP socket layer initialized
[ 1.874596] Bluetooth: SCO socket layer initialized
[ 1.884772] Bluetooth: HCI UART driver ver 2.3
[ 1.884774] Bluetooth: HCI UART protocol H4 registered
[ 1.884775] Bluetooth: HCI UART protocol BCSP registered
[ 1.884776] Bluetooth: HCI UART protocol LL registered
[ 1.884777] Bluetooth: HCI UART protocol ATH3K registered
[ 1.884779] Bluetooth: HCI UART protocol Three-wire (H5) registered
[ 1.884800] Bluetooth: HCI UART protocol Intel registered
[ 1.884811] Bluetooth: HCI UART protocol BCM registered
[ 1.884812] Bluetooth: HCI UART protocol QCA registered
[ 2.018145] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 2.023135] Bluetooth: hci0: Device revision is 5
[ 2.023138] Bluetooth: hci0: Secure boot is enabled
[ 2.023139] Bluetooth: hci0: OTP lock is enabled
[ 2.023140] Bluetooth: hci0: API lock is enabled
[ 2.023140] Bluetooth: hci0: Debug lock is disabled
[ 2.023141] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 2.039100] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 2.063532] Bluetooth: hci0: Failed to send firmware data (-38)
[ 4.066208] Bluetooth: hci0 command 0xfc05 tx timeout
[ 4.225754] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 4.225757] Bluetooth: BNEP filters: protocol multicast
[ 4.225759] Bluetooth: BNEP socket layer initialized
[ 8.944807] Bluetooth: hci0: Reading Intel version i...

[Nathan Grennan (9-ubuntuone-g)]

I am experiencing the same issue my Lenovo P50. It doesn't work most of the time at boot.

workaround:
rmmod btusb ; modprobe btusb

kernel messages when it fails:
[ 8.523061] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 8.525271] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 8.532355] Bluetooth: hci0: Failed to send firmware data (-38)
[ 10.608812] Bluetooth: hci0: Reading Intel version information failed (-110)
[ 10.612778] Bluetooth: hci0 command tx timeout

kernel messages post reload of the btusb module:
[ 712.576916] Bluetooth: hci0: Firmware revision 0.0 build 90 week 25 2015
[ 767.110199] Bluetooth: hci0 urb ffff88073c4c0540 failed to resubmit (2)

[penalvch (penalvch)]

Nathan Grennan, 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.

[aljosa (aljosa-p)]

Hello Christopher,
as you can see, my BIOS is already updated to the latest version:

~$ sudo dmidecode -s bios-version && sudo dmidecode -s bios-release-date
CDCN35WW
03/29/2016

I have now a fresh and totally clean installation of Ubuntu 16.04.
I would say that this is a very slow start result (result for other two older Asus notebooks is arround 9s):

~$ systemd-analyze
Startup finished in 4.008s (firmware) + 17.022s (loader) + 1.491s (kernel) + 1.471s (userspace) = 23.993s

Here's an excerpt from my DMESG which you can find attached to this post:

[ 0.000035] ACPI: Core revision 20150930
[ 0.025040] ACPI Error: [\_SB_.PCI0.XHC_.RHUB.HS11] Namespace lookup failure, AE_NOT_FOUND (20150930/dswload-210)
[ 0.025045] ACPI Exception: AE_NOT_FOUND, During name lookup/catalog (20150930/psobject-227)
[ 0.025084] ACPI Exception: AE_NOT_FOUND, (SSDT:CB-01 ) while loading table (20150930/tbxfload-193)
[ 0.030567] ACPI Error: 1 table load failures, 7 successful (20150930/tbxfload-214)

[ 0.355622] pci 0000:01:00.0: can't claim BAR 6 [mem 0xfff80000-0xffffffff pref]: no compatible bridge window
[ 0.355647] pci 0000:01:00.0: BAR 6: no space for [mem size 0x00080000 pref]
[ 0.355648] pci 0000:01:00.0: BAR 6: failed to assign [mem size 0x00080000 pref]

[ 1.014162] mmc0: Unknown controller version (3). You may experience problems.

[ 1.943569] iwlwifi 0000:08:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[ 1.943596] iwlwifi 0000:08:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[ 1.943603] iwlwifi 0000:08:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[ 1.947507] iwlwifi 0000:08:00.0: Unsupported splx structure

[ 2.752029] Bluetooth: hci0: Failed to send firmware data (-38)

[ 4.755825] Bluetooth: hci0 command 0xfc05 tx timeout
[ 9.634400] usb 1-11: USB disconnect, device number 5
[ 9.634710] Bluetooth: hci0: Reading Intel version information failed (-19)

[ 11.436894] Bluetooth: hci0: Setting Intel event mask failed (-16)

[aljosa (aljosa-p)]

[ 0.858435] [Firmware Bug]: No valid trip found
[ 0.861605] [Firmware Bug]: No valid trip found

This one is most annoying error, it appears on screen during booting:

failure writing sector 0x21c8800 to 'hd0'
press any key to continue...

[penalvch (penalvch)]

aljosa, in order to allow additional upstream developers to examine the issue, at your earliest convenience, could you please test the latest upstream kernel available from http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=N;O=D ? Please keep in mind the following:
1) The one to test is at the very top line at the top of the page (not the daily folder).
2) The release names are irrelevant.
3) The folder time stamps aren't indicative of when the kernel actually was released upstream.
4) Install instructions are available at https://wiki.ubuntu.com/Kernel/MainlineBuilds .

If testing on your main install would be inconvenient, one may:
1) Install Ubuntu to a different partition and then test this there.
2) Backup, or clone the primary install.

If the latest kernel 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 issue is fixed in the mainline kernel, please add the following tags by clicking on the yellow circle with a black pencil icon, next to the word Tags, located at the bottom of the report description:
kernel-fixed-upstream
kernel-fixed-upstream-X.Y-rcZ

Where X, and Y are the first two numbers of the kernel version, and Z is the release candidate number if it exists.

If the mainline kernel does not fix the issue, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-X.Y-rcZ

Please note, an error to install the kernel does not fit the criteria of kernel-bug-exists-upstream.

Also, you don't need to apport-collect further unless specifically requested to do so.

Once testing of the latest upstream kernel is complete, please mark this report Status Confirmed. Please let us know your results.

Thank you for your understanding.

[aljosa (aljosa-p)]

Kernel 4.6-rc7-wily: nothing changes, all above errors are still here (including boot error: failure writing sector 0x21c8800 to 'hd0'/ press any key to continue...). Please find attached my new dmesg.