Linux bluetooth development
 help / color / mirror / Atom feed
From: Diego Francio <dfrancio@gmail.com>
To: luiz.dentz@gmail.com, marcel@holtmann.org
Cc: linux-bluetooth@vger.kernel.org
Subject: [PATCH 0/2] Bluetooth: Disable LL Privacy on Intel JfP (8087:0aaa)
Date: Tue, 27 Oct 2026 13:43:57 -0300	[thread overview]
Message-ID: <20261027164359.460369-1-dfrancio@gmail.com> (raw)

Since LL Privacy became always-on in v6.14, the Intel 9460/9462/9560
(JfP, USB 8087:0aaa) firmware crashes with "Hardware error 0x0c" every few
minutes when BLE HID devices are paired, dropping every connection.

Patch 1 adds HCI_QUIRK_BROKEN_LL_PRIVACY, patch 2 sets it for 8087:0aaa.
Other controllers are not affected.

Tested on an Intel 9462 machine running Ubuntu 7.0.0-38: with this series
applied there was no Hardware Error in more than 4 hours with a keyboard
and a mouse connected, versus one every 3-15 minutes before. Forcing LL
Privacy off with a module parameter instead ran for 9 hours without one.
The exact HCI command that crashes the firmware was not identified (no
btmon capture of a crash).

Diego Francio (2):
  Bluetooth: Add HCI_QUIRK_BROKEN_LL_PRIVACY
  Bluetooth: btusb: Disable LL Privacy on Intel JfP (8087:0aaa)

 drivers/bluetooth/btusb_main.c   |  7 ++++++-
 include/net/bluetooth/hci.h      | 10 ++++++++++
 include/net/bluetooth/hci_core.h |  4 +++-
 3 files changed, 19 insertions(+), 2 deletions(-)

-- 
2.53.0


             reply	other threads:[~2026-10-27 16:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-27 16:43 Diego Francio [this message]
2026-10-27 16:43 ` [PATCH 1/2] Bluetooth: Add HCI_QUIRK_BROKEN_LL_PRIVACY Diego Francio
2026-10-27 21:23   ` Bluetooth: Disable LL Privacy on Intel JfP (8087:0aaa) bluez.test.bot
2026-10-27 16:43 ` [PATCH 2/2] Bluetooth: btusb: " Diego Francio

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20261027164359.460369-1-dfrancio@gmail.com \
    --to=dfrancio@gmail.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=luiz.dentz@gmail.com \
    --cc=marcel@holtmann.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox