From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220306] Updated ibt-18-16-1.sfi is bugged, "Invalid exception type 03" kernel spam
Date: Sat, 05 Jul 2025 11:34:57 +0000 [thread overview]
Message-ID: <bug-220306-62941-GI5srOgFaW@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-220306-62941@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=220306
--- Comment #5 from Artem S. Tashkinov (aros@gmx.com) ---
I haven't seen this error once since I downgraded the firmware.
With the new firmware, I received dozens of messages per hour.
--
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:[~2025-07-05 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-02 6:00 [Bug 220306] New: Updated ibt-18-16-1.sfi is bugged, "Invalid exception type 03" kernel spam bugzilla-daemon
2025-07-02 6:03 ` [Bug 220306] " bugzilla-daemon
2025-07-02 6:04 ` bugzilla-daemon
2025-07-04 6:00 ` bugzilla-daemon
2025-07-04 7:06 ` bugzilla-daemon
2025-07-05 11:34 ` bugzilla-daemon [this message]
2025-07-06 6:39 ` bugzilla-daemon
2025-07-07 3:56 ` bugzilla-daemon
2025-07-07 4:50 ` bugzilla-daemon
2025-07-07 5:26 ` 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-220306-62941-GI5srOgFaW@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