lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20250716173726.GA2545047@bhelgaas>
Date: Wed, 16 Jul 2025 12:37:26 -0500
From: Bjorn Helgaas <helgaas@...nel.org>
To: Marek Marczykowski-Górecki <marmarek@...isiblethingslab.com>
Cc: Miri Korenblit <miriam.rachel.korenblit@...el.com>,
	Colin Ian King <colin.i.king@...il.com>,
	linux-wireless@...r.kernel.org, linux-kernel@...r.kernel.org,
	regressions@...ts.linux.dev
Subject: Re: iwlwifi stopped working with AX200 (6.16-rc3 regression)

On Fri, Jun 27, 2025 at 04:32:28PM +0200, Marek Marczykowski-Górecki wrote:
> 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.

The patch you mention appears to have been merged and appears in
v6.16-rc4:

  https://git.kernel.org/linus/93598167dcb6 ("wifi: iwlwifi: mvm: assume '1' as the default mac_config_cmd version")

so perhaps this entry in the regression tracker can be closed?  Maybe
a response including this would do the trick?

  #regzbot fix: 93598167dcb6 ("wifi: iwlwifi: mvm: assume '1' as the default mac_config_cmd version")

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ