All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 219898] BLE - Intel AX211 fails to Pair on first attempt but succeeds on second attempt (utilizing software-controlled bluez API via Dbus)
Date: Wed, 19 Mar 2025 14:53:08 +0000	[thread overview]
Message-ID: <bug-219898-62941-QMWqH4L7VM@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-219898-62941@https.bugzilla.kernel.org/>

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

--- Comment #1 from Hunter M (miller.hunterc@gmail.com) ---
Created attachment 307861
  --> https://bugzilla.kernel.org/attachment.cgi?id=307861&action=edit
Btmon trace using bluetoothctl

Attached is a btmon log file when using bluetoothctl to pair. It looks as
though the LE Start Encryption on # 48 (8.710910) is followed by the Encryption
Change event on # 49 (8.888913). Following that, the new long term key event
occurs and pairing succeeds.

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

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

  reply	other threads:[~2025-03-19 14:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-19 14:51 [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
2025-03-19 14:53 ` bugzilla-daemon [this message]
2025-03-19 14:55 ` [Bug 219898] " bugzilla-daemon
2025-03-19 14:56 ` bugzilla-daemon
2025-03-19 15:02 ` bugzilla-daemon
2025-03-20 20:22 ` bugzilla-daemon
2025-03-20 20:23 ` bugzilla-daemon
2025-03-20 20:41 ` [Bug 219898] BLE - Intel AX211 fails to Pair on first attempt but succeeds on second attempt bugzilla-daemon
2025-03-20 21:09 ` bugzilla-daemon

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=bug-219898-62941-QMWqH4L7VM@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@kernel.org \
    --cc=linux-bluetooth@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.