[Bug 219898] New: BLE - Intel AX211 fails to Pair on first attempt but succeeds on second attempt (utilizing software-controlled bluez API via Dbus)

[bugzilla-daemon@kernel.org]

https://bugzilla.kernel.org/show_bug.cgi?id=219898

            Bug ID: 219898
           Summary: BLE - Intel AX211 fails to Pair on first attempt but
                    succeeds on second attempt (utilizing
                    software-controlled bluez API via Dbus)
           Product: Drivers
           Version: 2.5
          Hardware: Intel
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: miller.hunterc@gmail.com
        Regression: No

Created attachment 307860
  --> https://bugzilla.kernel.org/attachment.cgi?id=307860&action=edit
btmon trace using pair method via Dbus API

Attempting to Pair with a BLE device fails on the first Pairing attempt, but
succeeds on the second Pairing attempt when utilizing Bluez Dbus API.

When utilizing bluetoothctl directly, this issue does not occur.

Note that this issue does not arise when using Intel AC 9462, but only arises
utilizing Intel AX211.

From the syslogs, it seems new_long_term_key_callback() is never hit during the
first Pair attempt when utilizing dbus API, but is hit when using bluetoothctl
on the first Pair attempt.

I'm unsure where to go from here, but open to suggestions on how to debug this
issue further.

From the btmon log attached, it seems that LE Start Encryption occurs in # 40
(2.293188), followed by success in # 42 (2.294177). However, after the
supervision timeout of 30s, a disconnect is sent # 86 (32.619238).

In the second pair attempt, LE Start Encryption occurs in # 142 (37.979552),
followed by an Encryption Change event in # 143 (38.157560). Following that, a
new long term key event is notified, and pairing succeeds.

Seems as though the Encryption Change event (0x08) only occurs on the second
attempt.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.