From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221426] Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen
Date: Mon, 27 Apr 2026 20:25:49 +0000 [thread overview]
Message-ID: <bug-221426-62941-Ra87UMfHyS@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221426-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221426
Luiz Von Dentz (luiz.dentz@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |luiz.dentz@gmail.com
--- Comment #6 from Luiz Von Dentz (luiz.dentz@gmail.com) ---
(In reply to Paul Menzel from comment #2)
> Thank you for your report. Do you know if it’s a regression, that means, did
> it work with earlier Linux versions?
>
> What firmware is used?
>
> The BlueZ issue template has some more commands helping to collect things
> aiding in debugging.
>
>
> [1]: https://github.com/bluez/bluez/tree/master/.github/ISSUE_TEMPLATE
It might be a good idea to file the issue directly in github if there is a
btmon trace then btsnoop-analyzer is used to analyze it, that said I suspect
this is firmware related if it is really generating a hardware error.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next prev parent reply other threads:[~2026-04-27 20:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-27 16:32 [Bug 221426] New: Intel AX211 Bluetooth hci0 hardware error 0x0c with HID/HOG failures on 6.19.14-zen bugzilla-daemon
2026-04-27 16:32 ` [Bug 221426] " bugzilla-daemon
2026-04-27 17:26 ` bugzilla-daemon
2026-04-27 19:12 ` bugzilla-daemon
2026-04-27 20:08 ` bugzilla-daemon
2026-04-27 20:15 ` bugzilla-daemon
2026-04-27 20:25 ` bugzilla-daemon [this message]
2026-04-27 20:27 ` bugzilla-daemon
2026-04-28 6:53 ` 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-221426-62941-Ra87UMfHyS@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox