public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@kernel.org
To: linux-bluetooth@vger.kernel.org
Subject: [Bug 220306] New: Updated ibt-18-16-1.sfi is bugged, "Invalid exception type 03" kernel spam
Date: Wed, 02 Jul 2025 06:00:08 +0000	[thread overview]
Message-ID: <bug-220306-62941@https.bugzilla.kernel.org/> (raw)

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

            Bug ID: 220306
           Summary: Updated ibt-18-16-1.sfi is bugged, "Invalid exception
                    type 03" kernel spam
           Product: Drivers
           Version: 2.5
          Hardware: AMD
                OS: Linux
            Status: NEW
          Severity: high
          Priority: P3
         Component: Bluetooth
          Assignee: linux-bluetooth@vger.kernel.org
          Reporter: aros@gmx.com
        Regression: No

I've updated this file to 

sha256sum ibt-18-16-1.sfi 
3d83c90093885eb110ed1827226297bf5ccf9b0c4aa16de712919081a834c970 
ibt-18-16-1.sfi

and now my dmesg is full of:

[   10.704037] Bluetooth: hci0: Invalid exception type 03
[   13.613626] Bluetooth: RFCOMM TTY layer initialized
[   13.613631] Bluetooth: RFCOMM socket layer initialized
[   13.613656] Bluetooth: RFCOMM ver 1.11
[   18.818070] Bluetooth: hci0: Invalid exception type 03
[   78.989481] Bluetooth: hci0: Invalid exception type 03
[  138.998240] Bluetooth: hci0: Invalid exception type 03
[  198.988335] Bluetooth: hci0: Invalid exception type 03
[  259.008424] Bluetooth: hci0: Invalid exception type 03
[  319.022512] Bluetooth: hci0: Invalid exception type 03
[  379.032608] Bluetooth: hci0: Invalid exception type 03
[  439.032710] Bluetooth: hci0: Invalid exception type 03
[  499.031808] Bluetooth: hci0: Invalid exception type 03
[  559.040907] Bluetooth: hci0: Invalid exception type 03
[  619.035006] Bluetooth: hci0: Invalid exception type 03
[  679.036094] Bluetooth: hci0: Invalid exception type 03
[  739.051204] Bluetooth: hci0: Invalid exception type 03
[  799.042305] Bluetooth: hci0: Invalid exception type 03
[  859.040404] Bluetooth: hci0: Invalid exception type 03
[  919.052508] Bluetooth: hci0: Invalid exception type 03
[  979.052623] Bluetooth: hci0: Invalid exception type 03
[ 1039.059698] Bluetooth: hci0: Invalid exception type 03
[ 1099.078826] Bluetooth: hci0: Invalid exception type 03
[ 1159.096913] Bluetooth: hci0: Invalid exception type 03

My hardware is:

Bus 003 Device 002: ID 8087:0025 Intel Corp. Wireless-AC 9260 Bluetooth Adapter

I've also updated from 6.14 to 6.15 but I feel like this is down to firmware.

-- 
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-07-02  6:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-07-02  6:00 bugzilla-daemon [this message]
2025-07-02  6:03 ` [Bug 220306] Updated ibt-18-16-1.sfi is bugged, "Invalid exception type 03" kernel spam 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
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@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