Bluetooth: hci0: request failed to create LE connection: status 0x0c (Intel 9462/9560)

Bug #1829737 reported by You-Sheng Yang
16
This bug affects 2 people
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)
          Connection latency: 0 (0x0000)
          Supervision timeout: 420 msec (0x002a)
          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 29a536a02cadb75b84c6c0b5d7af22d34d278563, firmware release version 21.10.0.6. With that firmware blob placed under /lib/firmware/intel and a cold boot, dmesg gives updated revision and device pairing works as expected:

  Firmware revision 0.1 build 184 week 15 2019

You-Sheng Yang (vicamo)
tags: added: originate-from-1828968 somerville
You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu):
status: New → In Progress
Revision history for this message
You-Sheng Yang (vicamo) wrote :

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.

Changed in linux-firmware (Ubuntu Bionic):
status: New → In Progress
assignee: nobody → You-Sheng Yang (vicamo)
You-Sheng Yang (vicamo)
description: updated
Revision history for this message
You-Sheng Yang (vicamo) wrote :
You-Sheng Yang (vicamo)
Changed in linux-firmware (Ubuntu):
importance: Undecided → Critical
Changed in linux-firmware (Ubuntu Bionic):
importance: Undecided → Critical
Seth Forshee (sforshee)
description: updated
Changed in linux-firmware (Ubuntu Bionic):
status: In Progress → Fix Committed
Changed in linux-firmware (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Timo Aaltonen (tjaalton) wrote : Please test proposed package

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/1.173.7 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Revision history for this message
Timo Aaltonen (tjaalton) wrote :

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into bionic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/1.173.8 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested and change the tag from verification-needed-bionic to verification-done-bionic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-bionic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Timo Aaltonen (tjaalton)
tags: added: verification-needed-bionic
You-Sheng Yang (vicamo)
tags: added: verification-done-bionic
removed: verification-needed-bionic
Revision history for this message
Adam Conrad (adconrad) wrote : Update Released

The verification of the Stable Release Update for linux-firmware has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux-firmware - 1.173.8

---------------
linux-firmware (1.173.8) bionic; urgency=medium

  * add firmware and topology file for sound sof driver [cml/cnl]
    (LP: #1833405)
    - SAUCE: add firmware and topology for cml/cnl sof driver

  * Intel WiFi (CNVi) module has no function on Comet Lake [8086:02f0]
    (LP: #1833065)
    - iwlwifi: add new firmwares for integrated 22000 series

linux-firmware (1.173.7) bionic; urgency=medium

  * Add Intel CyclonePeak wifi firmware (LP: #1828133)
    - iwlwifi: add firmware for 22260 and update 9000 series -46 firmwares
    - iwlwifi: update -46 firmwares for 22260 and 9000 series

  * Bluetooth: hci0: request failed to create LE connection: status 0x0c
    (LP: #1829737)
    - linux-firmware: Update firmware file for Intel Bluetooth 9560

  * Add firmware for RTL8822BE and RTL8822CE (LP: #1831833)
    - rtw88: Add firmware file for driver rtw88
    - rtw88: RTL8822C: update rtw8822c_fw.bin to v5.0

 -- Seth Forshee <email address hidden> Mon, 24 Jun 2019 15:56:43 -0500

Changed in linux-firmware (Ubuntu Bionic):
status: Fix Committed → Fix Released
Changed in hwe-next:
status: New → Fix Released
Revision history for this message
Warren Baird (wjbaird) wrote :

I believe I'm impacted by this same issue. I have an ASUS ZenBook 14 - UX433FA - which based on this - https://www.notebookcheck.net/ASUS-ZenBook-14-UX433FA-Core-i5-8265U-SSD-FHD-Laptop-Review.403541.0.html - I believe has an Intel 9560 chipset (I am not sure how to independently verify this).
With kernels older than 4.20 I can successfully pair my bluetooth mouse (Logitech MX Master) - but with newer kernels I get "Bluetooth: hci0: request failed to create LE connection: status 0x0c" messages.

I'm running Linux Mint 19.1

I tried installing linux-firmware 1.173.8, and it didn't seem to help - I also downloaded 1.173.9 proposed from here: https://launchpad.net/ubuntu/bionic/amd64/linux-firmware/1.173.9 and that also didn't seem to help.

Both after a cold reboot and a warm reboot I see
[ 14.724438] Bluetooth: hci0: Firmware revision 0.1 build 201 week 49 2017

in my dmesg output.

If it's better to open a new bug to track this, let me know...

Revision history for this message
Seth Forshee (sforshee) wrote :

@Warren - If you still experience the issue with linux-firmware 1.173.8 then it must not be exactly the same issue, so please open a new bug.

Revision history for this message
Warren Baird (wjbaird) wrote :

Will do - thanks...

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.