Intel 8260 Bluetooth not working

Bug #1832988 reported by MAshby
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Invalid
Undecided
Unassigned
gnome-shell (Ubuntu)
Invalid
Undecided
Unassigned
linux (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Expected behaviour:
I can enable bluetooth in the system settings, and pair with my other devices.

Actual behaviour:
Always displays as 'off' in the settings dialog, and won't turn on.

Bluetooth worked on the same machine with previous Ubuntu releases (18.10) & no hardware changes.

"dmesg | grep -i bluetooth" reports the following:
```
[ 14.445902] Bluetooth: Core ver 2.22
[ 14.445918] Bluetooth: HCI device and connection manager initialized
[ 14.445921] Bluetooth: HCI socket layer initialized
[ 14.445923] Bluetooth: L2CAP socket layer initialized
[ 14.445929] Bluetooth: SCO socket layer initialized
[ 14.494345] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 14.499050] Bluetooth: hci0: Device revision is 5
[ 14.499052] Bluetooth: hci0: Secure boot is enabled
[ 14.499053] Bluetooth: hci0: OTP lock is enabled
[ 14.499053] Bluetooth: hci0: API lock is enabled
[ 14.499054] Bluetooth: hci0: Debug lock is disabled
[ 14.499055] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38)
[ 15.497805] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 15.497806] Bluetooth: BNEP filters: protocol multicast
[ 15.497810] Bluetooth: BNEP socket layer initialized
```

"lsb_release -rd" reports the following:
```
Description: Ubuntu 19.04
Release: 19.04
```
"cat /proc/version_signature" reports the following:
```
Ubuntu 5.0.0-16.17-generic 5.0.8
```

"apt-cache policy linux-firmware" reports the following:
```
linux-firmware:
  Installed: 1.178.1
  Candidate: 1.178.1
  Version table:
 *** 1.178.1 500
        500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main amd64 Packages
        500 http://gb.archive.ubuntu.com/ubuntu disco-updates/main i386 Packages
        500 http://security.ubuntu.com/ubuntu disco-security/main amd64 Packages
        500 http://security.ubuntu.com/ubuntu disco-security/main i386 Packages
        100 /var/lib/dpkg/status
     1.178 500
        500 http://gb.archive.ubuntu.com/ubuntu disco/main amd64 Packages
        500 http://gb.archive.ubuntu.com/ubuntu disco/main i386 Packages
```

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: linux-image-5.0.0-16-generic 5.0.0-16.17
ProcVersionSignature: Ubuntu 5.0.0-16.17-generic 5.0.8
Uname: Linux 5.0.0-16-generic x86_64
ApportVersion: 2.20.10-0ubuntu27
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: martin 2314 F.... pulseaudio
CurrentDesktop: ubuntu:GNOME
Date: Sun Jun 16 12:31:07 2019
InstallationDate: Installed on 2019-06-02 (13 days ago)
InstallationMedia: Ubuntu 19.04 "Disco Dingo" - Release amd64 (20190416)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 004: ID 1c7a:0603 LighTuning Technology Inc.
 Bus 001 Device 003: ID 5986:066d Acer, Inc
 Bus 001 Device 002: ID 8087:0a2b Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: PC Specialist Limited N15_17RD
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.0.0-16-generic root=/dev/mapper/ubuntu--vg-root ro quiet splash vt.handoff=1
RelatedPackageVersions:
 linux-restricted-modules-5.0.0-16-generic N/A
 linux-backports-modules-5.0.0-16-generic N/A
 linux-firmware 1.178.1
SourcePackage: linux
UpgradeStatus: No upgrade log present (probably fresh install)
dmi.bios.date: 12/25/2015
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1.05.11
dmi.board.asset.tag: Tag 12345
dmi.board.name: N15_17RD
dmi.board.vendor: CLEVO
dmi.board.version: Not Applicable
dmi.chassis.asset.tag: No Asset Tag
dmi.chassis.type: 10
dmi.chassis.vendor: No Enclosure
dmi.chassis.version: N/A
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr1.05.11:bd12/25/2015:svnPCSpecialistLimited:pnN15_17RD:pvrNotApplicable:rvnCLEVO:rnN15_17RD:rvrNotApplicable:cvnNoEnclosure:ct10:cvrN/A:
dmi.product.family: Not Applicable
dmi.product.name: N15_17RD
dmi.product.sku: Not Applicable
dmi.product.version: Not Applicable
dmi.sys.vendor: PC Specialist Limited

Revision history for this message
MAshby (mfashby) wrote :
Revision history for this message
Ubuntu Kernel Bot (ubuntu-kernel-bot) wrote : Status changed to Confirmed

This change was made by a bot.

Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
Daniel van Vugt (vanvugt) wrote : Re: Bluetooth not working

The attached RfKill.txt seems to suggest that Bluetooth is only turned off in software. So maybe this is just a gnome-shell GUI bug, or gnome-bluetooth.

To confirm this, please try turning it on by running this command in a terminal:

  rfkill unblock 0

Changed in gnome-shell (Ubuntu):
status: New → Incomplete
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Changed in gnome-bluetooth (Ubuntu):
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If the above command doesn't work then I would next focus on a possible kernel problem in:

[ 14.503899] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 14.558347] Bluetooth: hci0: Failed to send firmware data (-38)

summary: - Bluetooth not working
+ Intel 8260 Bluetooth not working
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
MAshby (mfashby) wrote :

Hi Daniel & Kei-Heng, thanks for the suggestions.

rfkill doesn't do much
> martin@martin-N15-17RD:~$ rfkill unblock 0
> rfkill: invalid identifier: 0

I'll try the kernel you suggested next.

Revision history for this message
MAshby (mfashby) wrote :

Kai-Heng: thanks for the suggestion, bluetooth now switches on & I can pair with devices.

Output of "dmesg | grep -i bluetooth" looks healthier too:

martin@martin-N15-17RD:~$ dmesg | grep -i bluetooth
[ 18.577708] Bluetooth: Core ver 2.22
[ 18.577724] Bluetooth: HCI device and connection manager initialized
[ 18.577728] Bluetooth: HCI socket layer initialized
[ 18.577730] Bluetooth: L2CAP socket layer initialized
[ 18.577733] Bluetooth: SCO socket layer initialized
[ 18.604676] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 18.609699] Bluetooth: hci0: Device revision is 5
[ 18.609700] Bluetooth: hci0: Secure boot is enabled
[ 18.609701] Bluetooth: hci0: OTP lock is enabled
[ 18.609702] Bluetooth: hci0: API lock is enabled
[ 18.609702] Bluetooth: hci0: Debug lock is disabled
[ 18.609704] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 18.616186] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 20.040219] Bluetooth: hci0: Waiting for firmware download to complete
[ 20.040662] Bluetooth: hci0: Firmware loaded in 1403163 usecs
[ 20.040696] Bluetooth: hci0: Waiting for device to boot
[ 20.051673] Bluetooth: hci0: Device booted in 10735 usecs
[ 20.053532] Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-11-5.ddc
[ 20.057675] Bluetooth: hci0: Applying Intel DDC parameters completed
[ 20.153462] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 20.153463] Bluetooth: BNEP filters: protocol multicast
[ 20.153466] Bluetooth: BNEP socket layer initialized
[ 31.673667] Bluetooth: RFCOMM TTY layer initialized
[ 31.673673] Bluetooth: RFCOMM socket layer initialized
[ 31.673677] Bluetooth: RFCOMM ver 1.11

I guess the next time there's a kernel update for Ubuntu though it will wipe out the one you provided?

Changed in linux (Ubuntu):
assignee: nobody → Kai-Heng Feng (kaihengfeng)
status: Incomplete → Confirmed
Changed in gnome-bluetooth (Ubuntu):
status: Incomplete → Invalid
Changed in gnome-shell (Ubuntu):
status: Incomplete → Invalid
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Before sending my fix upstream, can you test latest linux-firmware?
https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

Revision history for this message
MAshby (mfashby) wrote :

Hi Kai-Heng,
I'd love to try that out, however there's no installation instructions I can see & google isn't being helpful.
Could you direct me to some install instructions?

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/
$ sudo cp linux-firmware/iwlwifi-8000C-36.ucode /lib/firmware/
$ sudo reboot

Revision history for this message
MAshby (mfashby) wrote :

Thanks Kai-Heng,
I installed the latest firmware as you described and bluetooth works.
Please note I didn't uninstall the custom kernel from before. I don't know if this matters.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

The custom kernel has a fix for this particular issue. Please use the default kernel to test latest firmware.

Revision history for this message
MAshby (mfashby) wrote :

I re-installed the default kernel using the following command:
$ sudo apt install --reinstall linux-image-5.0.0-20-generic
then installed the latest linux-firmware as directed above,
and now bluetooth is broken again, same as before. I guess this means that your fix is required Kai-Heng.

Thanks for the assistance

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Changed in linux (Ubuntu):
assignee: Kai-Heng Feng (kaihengfeng) → nobody
Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please boot Ubuntu with default kernel, and with kernel parameter `usbcore.dyndbg=+p`, reproduce the issue, and attach dmesg?

Thanks.

Revision history for this message
MAshby (mfashby) wrote :

Hi, sorry for the very late response.
This now appears to be working with the stock kernel. I'll post version details later

Changed in linux (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Ivan Anishchuk (anishchuk-ia) wrote :

Still failing with the same error on latest Eoan (kernel 5.3.0-40-generic). Dmesg with default kernel and usbcore.dyndbg=+p attached.

Revision history for this message
Ivan Anishchuk (anishchuk-ia) wrote :

As a workaround I'm currently doing rmmod btusb && modprobe btusb after every boot which seem to do the magic. Attaching the dmesg for that just in case.

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Ivan,

Please open a new bug by running:

  ubuntu-bug linux

Revision history for this message
Diego Lineros (diegolineros) wrote :

Hi I am getting Failed to send firmware data (-38), even after cool boot
diego@lfb-Desktop:~$ dmesg | grep -i bluetooth
[ 5.985839] Bluetooth: Core ver 2.22
[ 5.985858] Bluetooth: HCI device and connection manager initialized
[ 5.985864] Bluetooth: HCI socket layer initialized
[ 5.985867] Bluetooth: L2CAP socket layer initialized
[ 5.985872] Bluetooth: SCO socket layer initialized
[ 6.132508] Bluetooth: hci0: Bootloader revision 0.0 build 2 week 52 2014
[ 6.138629] Bluetooth: hci0: Device revision is 5
[ 6.138631] Bluetooth: hci0: Secure boot is enabled
[ 6.138631] Bluetooth: hci0: OTP lock is enabled
[ 6.138632] Bluetooth: hci0: API lock is enabled
[ 6.138632] Bluetooth: hci0: Debug lock is disabled
[ 6.138633] Bluetooth: hci0: Minimum firmware build 1 week 10 2014
[ 6.183029] Bluetooth: hci0: Found device firmware: intel/ibt-11-5.sfi
[ 6.206658] Bluetooth: hci0: Failed to send firmware data (-38)
[ 6.206731] Bluetooth: hci0: Intel reset sent to retry FW download
[ 8.736500] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[ 8.736503] Bluetooth: BNEP filters: protocol multicast
[ 8.736512] Bluetooth: BNEP socket layer initialized
diego@lfb-Desktop:~$ dpkg --status bluez | grep '^Version:'
Version: 5.53-0ubuntu3
diego@lfb-Desktop:~$ lspci -knn | grep Net -A3;lsusb
02:00.0 Network controller [0280]: Intel Corporation Wireless 8260 [8086:24f3] (rev 3a)
 Subsystem: Intel Corporation Dual Band Wireless-AC 8260 [8086:1010]
 Kernel driver in use: iwlwifi
 Kernel modules: iwlwifi
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 002: ID 090c:1000 Silicon Motion, Inc. - Taiwan (formerly Feiya Technology Corp.) Flash Drive
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 010 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 009 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 002: ID 8087:0a2b Intel Corp.
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 006: ID 05e3:0608 Genesys Logic, Inc. Hub
Bus 001 Device 003: ID 03f0:7d11 HP, Inc Photosmart Premium C309g-m
Bus 001 Device 002: ID 045e:0761 Microsoft Corp. LifeCam VX-2000
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 003: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 003: ID 1ea7:0064 SHARKOON Technologies GmbH 2.4G Mouse
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 014 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 013 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 012 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 011 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

Revision history for this message
Kai-Heng Feng (kaihengfeng) wrote :

Can you please attach full dmesg?

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Diego, please open a new bug by running:

  ubuntu-bug linux

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.