From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 222204] New: Intel AX210 (8087:0032): A2DP audio stalls because the controller stops reporting HCI Number Of Completed Packets, while the ACL link stays up
Date: Tue, 27 Oct 2026 17:19:02 +0000 [thread overview]
Message-ID: <bug-222204-62941@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=222204
Bug ID: 222204
Summary: Intel AX210 (8087:0032): A2DP audio stalls because the
controller stops reporting HCI Number Of Completed
Packets, while the ACL link stays up
Product: Drivers
Version: 2.5
Hardware: AMD
OS: Linux
Status: NEW
Severity: normal
Priority: P3
Component: Bluetooth
Assignee: linux-bluetooth@vger.kernel.org
Reporter: danoomsys@proton.me
Regression: No
Created attachment 311313
--> https://bugzilla.kernel.org/attachment.cgi?id=311313&action=edit
Raw logs and full analysis
The full analysis is in the attached report-kernel-bugzilla.md; raw log
excerpts are in
report-bt-ax210-logs.tar.gz. In short:
Intel AX210 (USB 8087:0032) stops reporting HCI event 0x13 (Number Of Completed
Packets)
for the A2DP headset's ACL handle while the ACL link stays up. Audio goes
silent, BlueZ
still reports the device as connected, L2CAP echo keeps working, and only a
disconnect/reconnect restores playback. Happens 1-3 times per day, during
playback and
while the sink is idle, with SBC at short range. No USB errors and no kernel
warnings.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2026-10-27 17:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 17:19 bugzilla-daemon [this message]
2026-10-27 17:40 ` [Bug 222204] Intel AX210 (8087:0032): A2DP audio stalls because the controller stops reporting HCI Number Of Completed Packets, while the ACL link stays up 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-222204-62941@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.