From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 221339] AX200 -19 errors on boot after firmware 20260313-1.1
Date: Fri, 10 Apr 2026 09:21:05 +0000 [thread overview]
Message-ID: <bug-221339-62941-4ZrIIO7G7Z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221339-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=221339
--- Comment #4 from pallaswept@proton.me ---
Sorry Paul I'm not very experienced with filing kernel bugs but I'll keep it in
mind for next time.
Yes I have confirmed that it was that file, if I roll back to the previous
version the issues are resolved.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2026-04-10 9:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-09 16:53 [Bug 221339] New: AX200 -19 errors on boot after firmware 20260313-1.1 bugzilla-daemon
2026-04-10 7:36 ` [Bug 221339] " bugzilla-daemon
2026-04-10 9:16 ` bugzilla-daemon
2026-04-10 9:18 ` bugzilla-daemon
2026-04-10 9:21 ` bugzilla-daemon [this message]
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-221339-62941-4ZrIIO7G7Z@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