All of lore.kernel.org
 help / color / mirror / Atom feed
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:16:59 +0000	[thread overview]
Message-ID: <bug-221339-62941-3iIy0rWuER@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-221339-62941@https.bugzilla.kernel.org/>

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

Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |kiran.k@intel.com,
                   |                            |pmenzel+bugzilla.kernel.org
                   |                            |@molgen.mpg.de

--- Comment #2 from Paul Menzel (pmenzel+bugzilla.kernel.org@molgen.mpg.de) ---
This could be the commit below:

```
commit 81608d9216ce1fe954e205aa867655b1a5bce1c5
Author: Ravindra <ravindra@intel.com>
Date:   Wed Mar 11 15:21:05 2026 +0530

    linux-firmware: Update firmware file for Intel Quasar core

    This patch contains firmware files for
    - Cyclone Peak2 (CcP2) - AX200

    FW Build: BT_Quasar_REL53843_22.180.2607.53843
    FSEQ: 0x89.3.35.37

    Release Version: 24.30.0.4

    Signed-off-by: Ravindra <ravindra@intel.com>

 intel/ibt-20-1-3.sfi | Bin 801016 -> 800036 bytes
 1 file changed, 0 insertions(+), 0 deletions(-)
```

I [commented on the linux-firmware merge
request](https://gitlab.com/kernel-firmware/linux-firmware/-/merge_requests/955#note_3239391259),
but it’d be great if you verified that changed `ibt-20-1-3.sfi` is really the
reason.

-- 
You may reply to this email to add a comment.

You are receiving this mail because:
You are the assignee for the bug.

  parent reply	other threads:[~2026-04-10  9:16 UTC|newest]

Thread overview: 15+ 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 [this message]
2026-04-10  9:18 ` bugzilla-daemon
2026-04-10  9:21 ` bugzilla-daemon
2026-04-14  7:04 ` bugzilla-daemon
2026-04-14  7:16 ` bugzilla-daemon
2026-04-14  7:27 ` bugzilla-daemon
2026-04-18  4:34 ` bugzilla-daemon
2026-04-20 11:36 ` bugzilla-daemon
2026-04-20 11:37 ` bugzilla-daemon
2026-04-20 11:56 ` bugzilla-daemon
2026-04-21  5:07 ` bugzilla-daemon
2026-04-22  8:44 ` bugzilla-daemon
2026-05-01  5:36 ` 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-221339-62941-3iIy0rWuER@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.