Intel Corporation Cannon Point-LP CNVi [Wireless-AC] [8086:9df0] (rev 30) Subsystem [8086:0034] Kernel 4.19+: Bluetooth not working; Ubuntu 20.04

[mm]

New bug report for kernel:
After testing Ubuntu 20.04 on my Intel NUC (NUC8i3BEH) I found out, that Bluetooth (LE) [hardware: Intel Wireless-AC 9560] isn't working; hcitool lescan reports:
hcitool lescan
Set scan parameters failed: Input/output error

When the error occurs, btmon is reporting:
> HCI Event: Command Complete (0x0e) plen 4 #4 [hci0] 20:22:26.130058
      LE Set Scan Enable (0x08|0x000c) ncmd 1
        Status: Command Disallowed (0x0c)

Beside the following error messages, there are no clues in the syslog concerning the error as far as I can tell:
[ 138.152718] debugfs: File 'le_min_key_size' in directory 'hci0' already present!
[ 138.152722] debugfs: File 'le_max_key_size' in directory 'hci0' already present!

After testing the Ubuntu kernels I found out that this Bluetooth LE scanning works just fine with Kernel 4.15 (Ubuntu 18.04 up to date standard kernel) and Kernel 4.18 (Ubuntu 18.04.1 HWE EOL kernel).
The problem starts from kernel version 5.0 (Ubuntu 18.04.2 HWE kernel) and is reproducible with the current Ubuntu 20.04 standard kernel.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu26
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: lightdm 5081 F.... pulseaudio
CasperMD5CheckResult: skip
DistroRelease: Ubuntu 20.04
InstallationDate: Installed on 2020-04-01 (8 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Beta amd64 (20200331)
Lsusb:
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 003: ID 0463:ffff MGE UPS Systems UPS
 Bus 001 Device 002: ID 0658:0200 Sigma Designs, Inc. Aeotec Z-Stick Gen5 (ZW090) - UZB
 Bus 001 Device 004: ID 8087:0aaa Intel Corp.
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Intel(R) Client Systems NUC8i3BEH
Package: linux (not installed)
ProcFB:

ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-5.4.0-21-generic root=/dev/mapper/vgcs2ubct-root ro
ProcVersionSignature: Ubuntu 5.4.0-21.25-generic 5.4.27
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.4.0-21-generic N/A
 linux-backports-modules-5.4.0-21-generic N/A
 linux-firmware 1.187
Tags: focal
Uname: Linux 5.4.0-21-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

_MarkForUpload: True
dmi.bios.date: 03/09/2020
dmi.bios.vendor: Intel Corp.
dmi.bios.version: BECFL357.86A.0078.2020.0309.1538
dmi.board.name: NUC8BEB
dmi.board.vendor: Intel Corporation
dmi.board.version: J72693-306
dmi.chassis.type: 35
dmi.chassis.vendor: Intel Corporation
dmi.chassis.version: 2.0
dmi.modalias: dmi:bvnIntelCorp.:bvrBECFL357.86A.0078.2020.0309.1538:bd03/09/2020:svnIntel(R)ClientSystems:pnNUC8i3BEH:pvrJ72753-305:rvnIntelCorporation:rnNUC8BEB:rvrJ72693-306:cvnIntelCorporation:ct35:cvr2.0:
dmi.product.family: Intel NUC
dmi.product.name: NUC8i3BEH
dmi.product.sku: BOXNUC8i3BEH
dmi.product.version: J72753-305
dmi.sys.vendor: Intel(R) Client Systems

[mm (mtl-0)]

I can confirm that 4.19 mainline kernel has got the error:

Linux xxx 4.19.114-0419114-generic #202004021037 SMP Thu Apr 2 14:42:12 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
hcitool lescan
Set scan parameters failed: Input/output error

@ RAW Open: hcitool (privileged) version 2.22 {0x0004} [hci0] 20:54:57.660407
< HCI Command: LE Set Scan Parameters (0x08|0x000b) plen 7 #1 [hci0] 20:54:57.660419
        Type: Active (0x01)
        Interval: 10.000 msec (0x0010)
        Window: 10.000 msec (0x0010)
        Own address type: Public (0x00)
        Filter policy: Accept all advertisement (0x00)
> HCI Event: Command Complete (0x0e) plen 4 #2 [hci0] 20:54:57.779936
      LE Set Scan Parameters (0x08|0x000b) ncmd 1
        Status: Command Disallowed (0x0c)
@ RAW Close: hcitool

4.18 mainline kernel works:
Linux xxx 4.18.20-041820-generic #201812030624 SMP Mon Dec 3 11:25:55 UTC 2018 x86_64 x86_64 x86_64 GNU/Linux

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1872122

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[mm (mtl-0)]

5.6 mainline kernel also does not work.

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[mm (mtl-0)]

apport information

[Oleg B (f00bar)]

Currently, unable to use the Bluetooth device at all. In the UI, the scanning stuck with a spinning loader.

The journal reports the same error reported by the author.

```
lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 20.04 LTS
Release: 20.04
Codename: focal
```

```
uname -a
Linux n552vw 5.4.0-37-generic #41-Ubuntu SMP Wed Jun 3 18:57:02 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

```

[You-Sheng Yang (vicamo)]

First, hcitool has been deprecated for a long time. Please use btmgmt instead.

Second, please do a complete shutdown, unplug power cable for a while and power on. Attach system journal log of this boot for it will contain firmware loading information that is necessary to take further investigation.

[mm (mtl-0)]

Clean boot log attached.

[mm (mtl-0)]

So, the main problem has been identified:
In kernel v < 4.19 the "normal" BLE commands work.
In kernel v > 4.19 only the BLE extended (BT 5.0) commands work.

When software relies on the "normal" BLE commands, issues arise when kernel v > 4.19 is being used.

[You-Sheng Yang (vicamo)]

So it doesn't seem to be an issue in kernel. If you think there is still something wrong in the software (bluez?), please add the affected projects.

[Wes (wes234234)]

> In kernel v < 4.19 the "normal" BLE commands work.
> In kernel v > 4.19 only the BLE extended (BT 5.0) commands work.
..
> So it doesn't seem to be an issue in kernel

What? That indicates it is a problem with the kernel, doesn't it? The desired behaviour exists in previous versions but is broken in current versions where the only component changing is the kernel version. I too am seeing this and specifically with the AC 9560's Bluetooth's BLE on a 4.19 kernel - I am unable to scan or query any BLE devices with this hw and kernel now.

[Maarten Fonville (maarten-fonville)]

I am receiving a similar error with my Microsoft Surface bluetooth mouse after upgrading to the latest kernel. You check the details in my comment on the Kernel bugzilla: https://bugzilla.kernel.org/show_bug.cgi?id=204765#c10