From: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
To: Miri Korenblit <miriam.rachel.korenblit@intel.com>,
Colin Ian King <colin.i.king@gmail.com>
Cc: linux-wireless@vger.kernel.org, linux-kernel@vger.kernel.org,
regressions@lists.linux.dev
Subject: Re: iwlwifi stopped working with AX200 (6.16-rc3 regression)
Date: Fri, 27 Jun 2025 16:32:28 +0200 [thread overview]
Message-ID: <aF6rfM-RFrwFyoEw@mail-itl> (raw)
In-Reply-To: <aF35tbqxHtyj9fJO@mail-itl>
[-- Attachment #1: Type: text/plain, Size: 914 bytes --]
On Fri, Jun 27, 2025 at 03:53:57AM +0200, Marek Marczykowski-Górecki wrote:
> On Fri, Jun 27, 2025 at 03:51:18AM +0200, Marek Marczykowski-Górecki wrote:
> > I see the only change there between rc2 and rc3 is fixing that WARN_ON
> > condition. Unfortunately, I don't know what cmd_ver value I have there,
> > but apparently it's outside of that range (and yet, the driver worked
> > fine before).
> >
> > The device is:
> > 02:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
> > Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
> >
> > #regzbot introduced: v6.16-rc2..v6.16-rc3
>
> Oh, I see it might be already fixed by
> https://lore.kernel.org/linux-wireless/20250623111351.1819915-1-miriam.rachel.korenblit@intel.com/,
> I'll test it.
Yes, it does fix the issue.
--
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-06-27 14:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 1:51 iwlwifi stopped working with AX200 (6.16-rc3 regression) Marek Marczykowski-Górecki
2025-06-27 1:53 ` Marek Marczykowski-Górecki
2025-06-27 14:32 ` Marek Marczykowski-Górecki [this message]
2025-07-16 17:37 ` Bjorn Helgaas
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=aF6rfM-RFrwFyoEw@mail-itl \
--to=marmarek@invisiblethingslab.com \
--cc=colin.i.king@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=miriam.rachel.korenblit@intel.com \
--cc=regressions@lists.linux.dev \
/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.