Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux-firmware (Ubuntu) |
Fix Released
|
Critical
|
You-Sheng Yang | ||
Bionic |
Fix Released
|
Critical
|
You-Sheng Yang |
Bug Description
SRU Justification
[Impact]
The firmware blob for Intel Bluetooth 9560/9462 is versioned 20.30.0.1 is not compatible with kernel version >= 4.19 and will cause failure to pair BT 4.0 devices.
[Fix]
29a536a02cad linux-firmware: Update firmware file for Intel Bluetooth 9560
Above upstream change contains latest firmware file for Intel Bluetooth 9560 that fixes HID pairing in recent kernel versions.
[Test Case]
Copy ibt-17-16-1.sfi blob to /lib/firmware/intel and do a cold boot to reload firmware. One should find following message in dmesg:
Bluetooth: hci0: Bootloader revision 0.1 build 42 week 52 2015
This indicates firmware reload has been activated. For further warm boots, kernel would dump updated revision:
Bluetooth: hci0: Firmware revision 0.1 build 184 week 15 2019
And perform BT 4.0 device pairing for functional tests.
Tested blob against following kernel versions:
* 5.0.0-1004-oem-osp1
* 5.0.0-15-generic
* 4.18.0-20-generic
* 4.15.0-1038-oem
* 4.15.0-50-generic
[Regression Risk]
Low. This affects only Intel JeffersonPeak Bluetooth chip series, namely 9461/9462/9560, which are the hardware variants to be fixed.
---
For kernel version >= 4.19, it fails to pair with BT4.0 HID devices and leave error messages in syslog:
Bluetooth: hci0: request failed to create LE connection: status 0x0c
Which can be detailed by btmon:
< HCI Command: LE Extended Create Connection (0x08|0x0043) plen 26 #800 [hci0] 30.895622
Filter policy: White list is not used (0x00)
Own address type: Public (0x00)
Peer address type: Random (0x01)
Peer address: DB:DD:51:2D:1C:CC (Static)
Initiating PHYs: 0x01
Entry 0: LE 1M
Scan interval: 60.000 msec (0x0060)
Scan window: 60.000 msec (0x0060)
Min connection interval: 30.00 msec (0x0018)
Max connection interval: 50.00 msec (0x0028)
Min connection length: 0.000 msec (0x0000)
Max connection length: 0.000 msec (0x0000)
> HCI Event: Command Status (0x0f) plen 4 #801 [hci0] 30.896453
LE Extended Create Connection (0x08|0x0043) ncmd 1
Status: Command Disallowed (0x0c)
Indicating this is actually a firmware problem.
Verified this has been fixed at least in upstream linux-firmware commit 29a536a02cadb75
Firmware revision 0.1 build 184 week 15 2019
tags: | added: originate-from-1828968 somerville |
Changed in linux-firmware (Ubuntu): | |
status: | New → In Progress |
description: | updated |
Changed in linux-firmware (Ubuntu): | |
importance: | Undecided → Critical |
Changed in linux-firmware (Ubuntu Bionic): | |
importance: | Undecided → Critical |
description: | updated |
Changed in linux-firmware (Ubuntu Bionic): | |
status: | In Progress → Fix Committed |
Changed in linux-firmware (Ubuntu): | |
status: | In Progress → Fix Released |
tags: | added: verification-needed-bionic |
tags: |
added: verification-done-bionic removed: verification-needed-bionic |
Changed in hwe-next: | |
status: | New → Fix Released |
Affected linux-firmware package series:
* Trusty: N/A
* Xenial: REL0186
* 4.4.0-1480generic (not supported)
* 4.15.0-50-generic (not affected)
* Bionic: REL0201 20.30.0.1
* 4.15.0-1038-oem (not affected)
* 4.15.0-50-generic (not affected)
* 4.18.0-20-generic (not affected)
* 5.0.0-1004-oem-osp1 (affected)
* Cosmic: REL0329 20.70.0.4
* 4.15.0-50-generic (not affected)
* 4.18.0-20-generic (not affected)
* Disco: REL0420 21.0.0.4
* 4.15.0-1038-oem (not affected)
* 5.0.0.0-15-generic (not affected)
* Eoan: REL0420 21.0.0.4
* 4.15.0-1038-oem (not affected)
* 5.0.0.0-15-generic (not affected)
Only Bionic with 5.0.0-1004-oem-osp1 is affected.