Netdev List
 help / color / mirror / Atom feed
From: Ofir Mano <ofir@xmousse.com>
To: linux-bluetooth@vger.kernel.org
Cc: netdev@vger.kernel.org
Subject: [PATCH 0/1] Bluetooth: add passive-discovery quirk for Intel 9460/9560
Date: Tue, 17 Nov 2026 20:22:37 +0000	[thread overview]
Message-ID: <20261117202632.49924-1-ofir@xmousse.com> (raw)

Hi all,

Intel 9460/9560 (8087:0aaa) controllers stop reporting connectable BLE
advertisements after the first active-scan SCAN_REQ/SCAN_RSP exchange.  The
controller stays silent until it is reset, even though the host scan is
configured correctly.

This breaks WebAuthn hybrid (caBLE) passkeys: the phone advertises a
connectable ADV_IND carrying the FIDO service data, the first operation
succeeds, and every later operation times out until a reboot or a
driver/controller reset.  btmon on a failing attempt shows no advertising
report at all, with `Filter duplicates: Disabled` and the same scan
parameters as the successful attempt, so the loss is below the kernel.

Same machine, same controller, same firmware build: Windows receives the
caBLE advertisement reliably.  A USB HCI capture shows Windows scans
passively (PASSIVE, PUBLIC own address, 1M only, ~10-15% duty and an Intel
0xFC1E vendor command before each scan), while Linux scans actively.

We tested the fix space as module variants in the real flow:
  - stock (active, random address, deferred delivery): 1st works, 2nd fails
  - active with delivery deferral removed: fails
  - active with PUBLIC own address: fails (both attempts)
  - passive: ~1 failure in 18 consecutive operations
So neither the kernel report path nor the scanner's own address is the
cause; the latch is tied to the active-scan exchange itself.

The smallest working fix is therefore to scan passively for this
controller, and to deliver passive reports during discovery.  The latter is
needed because the existing passive filter drops reports that do not have a
pending report action or an advertisement monitor.

The patch adds HCI_QUIRK_PASSIVE_DISCOVERY and sets it for 8087:0aaa only.
**Other controllers keep active scanning**.  The trade-off on the affected
parts is that scan-response-only data (for example device names carried
only in SCAN_RSP) is not available during discovery; that matches how the
vendor stack drives the same hardware.

Testing: Pop!_OS, kernel 7.2.15, Intel 9460/9560 (8087:0aaa), firmware 169
(2024-08-13).  With the quirk, discovery runs PASSIVE with a random address
(verified in btmon) and 18 consecutive hybrid operations produced one
unexplained failure.  The patch applies to a clean tree and builds
bluetooth.ko and btusb.ko.

!!! No regression testing was performed on other controllers; 
the quirk is keyed to this USB ID, so all other devices keep active scanning.

Public reports with the same signature:
  https://bbs.archlinux.org/viewtopic.php?id=298396
    (exact 8087:0aaa; scanning works briefly after rmmod/modprobe btusb,
    then stops again - i.e. a reset clears the latch)
  https://discussion.fedoraproject.org/t/intel-bluetooth-wont-scan-ble-device-works-on-windows-blank-scan-on-linux/196326
    (Intel, kernel 7.1.3; btmon shows the extended scan but the controller
    returns no advertising reports; Windows works on the same laptop)
  https://issues.chromium.org/issues/41485480
    (caBLE passkey never completes; worked on 6.3, failed on >= 6.4 with an
    AX210; closed as "Not a Chrome issue")

Note on scope: ArchWiki reports that passive scanning is broken on Intel
AX200, so I deliberately did not widen the quirk beyond the tested USB ID.



             reply	other threads:[~2026-11-17 20:27 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-17 20:22 Ofir Mano [this message]
2026-11-17 20:22 ` [PATCH] Bluetooth: add passive-discovery quirk for Intel 9460/9560 Ofir Mano

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=20261117202632.49924-1-ofir@xmousse.com \
    --to=ofir@xmousse.com \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=netdev@vger.kernel.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