[REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Chris Bainbridge]

Hi,

Laptop: Lenovo Legion 7 16ACHg6.
Wifi: Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)

Wifi stopped working in recent kernel builds:

[   20.907824] Intel(R) Wireless WiFi driver for Linux
[   20.907955] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
[   20.912024] ee1004 2-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
[   20.913666] NET: Registered PF_BLUETOOTH protocol family
[   20.913670] Bluetooth: HCI device and connection manager initialized
[   20.913806] Bluetooth: HCI socket layer initialized
[   20.913810] Bluetooth: L2CAP socket layer initialized
[   20.913828] Bluetooth: SCO socket layer initialized
[   20.917455] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
[   20.917674] iwlwifi 0000:04:00.0: PCI dev 2723/1654, rev=0x340, rfid=0x10a100
[   20.917679] iwlwifi: No config found for PCI dev 2723/1654, rev=0x340, rfid=0x10a100
[   20.920126] iwlwifi 0000:04:00.0: probe with driver iwlwifi failed with error -22

Bisect led to:

commit 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b (HEAD)
Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
Date:   Wed Feb 5 14:55:42 2025 +0200

    wifi: iwlwifi: make no_160 more generic

    We'll have devices that are EHT capable but don't support 320 MHz and
    those devices look like the 320 MHz capable devices, but have distinct
    subsystem ID.
    We already had the same type of differentiation for HE devices that
    support 160 MHz or not.
    Enhance that mechanism and now the _IWL_DEV_INFO macro gets an
    indication whether the bandwidth should be limited for that specific
    device.
    The subsystem ID gives a binary answer about the bandwidth limitation
    and iwl_pci_find_dev_info() compares this to the list of _IWL_DEV_INFO
    entries.

    Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
    Reviewed-by: Johannes Berg <johannes.berg@intel.com>
    Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
    Link: https://patch.msgid.link/20250205145347.1ba406c538a5.I6e24123f60a764aedfeaaac8768c26e136c320cf@changeid
    Signed-off-by: Johannes Berg <johannes.berg@intel.com>

#regzbot introduced: 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b

RE: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Korenblit, Miriam Rachel]

> -----Original Message-----
> From: Chris Bainbridge <chris.bainbridge@gmail.com>
> Sent: Friday, 28 March 2025 3:37
> To: Grumbach, Emmanuel <emmanuel.grumbach@intel.com>
> Cc: linux-wireless@vger.kernel.org; kvalo@kernel.org; Korenblit, Miriam Rachel
> <miriam.rachel.korenblit@intel.com>; Berg, Johannes
> <johannes.berg@intel.com>; benjamin@sipsolutions.net;
> regressions@lists.linux.dev
> Subject: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22
> 
> Hi,
> 
> Laptop: Lenovo Legion 7 16ACHg6.
> Wifi: Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
> 04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723]
> (rev 1a)
> 
> Wifi stopped working in recent kernel builds:
> 
> [   20.907824] Intel(R) Wireless WiFi driver for Linux
> [   20.907955] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
> [   20.912024] ee1004 2-0050: 512 byte EE1004-compliant SPD EEPROM, read-
> only
> [   20.913666] NET: Registered PF_BLUETOOTH protocol family
> [   20.913670] Bluetooth: HCI device and connection manager initialized
> [   20.913806] Bluetooth: HCI socket layer initialized
> [   20.913810] Bluetooth: L2CAP socket layer initialized
> [   20.913828] Bluetooth: SCO socket layer initialized
> [   20.917455] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530
> wfpm id 0x80000000
> [   20.917674] iwlwifi 0000:04:00.0: PCI dev 2723/1654, rev=0x340,
> rfid=0x10a100
> [   20.917679] iwlwifi: No config found for PCI dev 2723/1654, rev=0x340,
> rfid=0x10a100
> [   20.920126] iwlwifi 0000:04:00.0: probe with driver iwlwifi failed with error -22
> 
> Bisect led to:
> 
> commit 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b (HEAD)
> Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> Date:   Wed Feb 5 14:55:42 2025 +0200
> 
>     wifi: iwlwifi: make no_160 more generic
> 
>     We'll have devices that are EHT capable but don't support 320 MHz and
>     those devices look like the 320 MHz capable devices, but have distinct
>     subsystem ID.
>     We already had the same type of differentiation for HE devices that
>     support 160 MHz or not.
>     Enhance that mechanism and now the _IWL_DEV_INFO macro gets an
>     indication whether the bandwidth should be limited for that specific
>     device.
>     The subsystem ID gives a binary answer about the bandwidth limitation
>     and iwl_pci_find_dev_info() compares this to the list of _IWL_DEV_INFO
>     entries.
> 
>     Signed-off-by: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
>     Reviewed-by: Johannes Berg <johannes.berg@intel.com>
>     Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
>     Link:
> https://patch.msgid.link/20250205145347.1ba406c538a5.I6e24123f60a764aedf
> eaaac8768c26e136c320cf@changeid
>     Signed-off-by: Johannes Berg <johannes.berg@intel.com>
> 
> #regzbot introduced: 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b

Hi Chris, thanks for the report.
We have a fix for that which will be sent soon.

Thanks,
Miri

Re: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Chris Bainbridge]

On Sun, 30 Mar 2025 at 05:12, Korenblit, Miriam Rachel
<miriam.rachel.korenblit@intel.com> wrote:
>
> Hi Chris, thanks for the report.
> We have a fix for that which will be sent soon.
>
> Thanks,
> Miri

Hi, did this get fixed? v6.15-rc3 appears to still be broken.

Re: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Johannes Berg]

On Wed, 2025-04-23 at 16:06 +0100, Chris Bainbridge wrote:
> On Sun, 30 Mar 2025 at 05:12, Korenblit, Miriam Rachel
> <miriam.rachel.korenblit@intel.com> wrote:
> > 
> > Hi Chris, thanks for the report.
> > We have a fix for that which will be sent soon.
> > 
> > Thanks,
> > Miri
> 
> Hi, did this get fixed? v6.15-rc3 appears to still be broken.
> 

I just merged a couple of reverts into wireless. I guess if I hurry it
could get into -rc4.

johannes

Re: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Bjorn Helgaas]

On Fri, Mar 28, 2025 at 12:36:38AM +0000, Chris Bainbridge wrote:
> Hi,
> 
> Laptop: Lenovo Legion 7 16ACHg6.
> Wifi: Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
> 04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
> 
> Wifi stopped working in recent kernel builds:
> 
> [   20.907824] Intel(R) Wireless WiFi driver for Linux
> [   20.907955] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
> [   20.912024] ee1004 2-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
> [   20.913666] NET: Registered PF_BLUETOOTH protocol family
> [   20.913670] Bluetooth: HCI device and connection manager initialized
> [   20.913806] Bluetooth: HCI socket layer initialized
> [   20.913810] Bluetooth: L2CAP socket layer initialized
> [   20.913828] Bluetooth: SCO socket layer initialized
> [   20.917455] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
> [   20.917674] iwlwifi 0000:04:00.0: PCI dev 2723/1654, rev=0x340, rfid=0x10a100
> [   20.917679] iwlwifi: No config found for PCI dev 2723/1654, rev=0x340, rfid=0x10a100
> [   20.920126] iwlwifi 0000:04:00.0: probe with driver iwlwifi failed with error -22
> 
> Bisect led to:
> 
> commit 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b (HEAD)
> Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> Date:   Wed Feb 5 14:55:42 2025 +0200
> 
>     wifi: iwlwifi: make no_160 more generic

https://git.kernel.org/linus/64dc5d5e341d ("Revert "wifi: iwlwifi:
make no_160 more generic"") appeared in v6.15-rc5 and reverts
75a3313f52b7 ("wifi: iwlwifi: make no_160 more generic"), so it
*looks* like this regression should be fixed, but it still appears in
the tracker at https://linux-regtracking.leemhuis.info/regzbot/mainline/

If it is resolved, can somebody send the appropriate regzbot fix
command?  (See https://linux-regtracking.leemhuis.info/about/#tldr)

Re: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Johannes Berg]

On Wed, 2025-07-16 at 13:42 -0500, Bjorn Helgaas wrote:
> On Fri, Mar 28, 2025 at 12:36:38AM +0000, Chris Bainbridge wrote:
> > Hi,
> > 
> > Laptop: Lenovo Legion 7 16ACHg6.
> > Wifi: Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
> > 04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
> > 
> > Wifi stopped working in recent kernel builds:
> > 
> > [   20.907824] Intel(R) Wireless WiFi driver for Linux
> > [   20.907955] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
> > [   20.912024] ee1004 2-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
> > [   20.913666] NET: Registered PF_BLUETOOTH protocol family
> > [   20.913670] Bluetooth: HCI device and connection manager initialized
> > [   20.913806] Bluetooth: HCI socket layer initialized
> > [   20.913810] Bluetooth: L2CAP socket layer initialized
> > [   20.913828] Bluetooth: SCO socket layer initialized
> > [   20.917455] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
> > [   20.917674] iwlwifi 0000:04:00.0: PCI dev 2723/1654, rev=0x340, rfid=0x10a100
> > [   20.917679] iwlwifi: No config found for PCI dev 2723/1654, rev=0x340, rfid=0x10a100
> > [   20.920126] iwlwifi 0000:04:00.0: probe with driver iwlwifi failed with error -22
> > 
> > Bisect led to:
> > 
> > commit 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b (HEAD)
> > Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> > Date:   Wed Feb 5 14:55:42 2025 +0200
> > 
> >     wifi: iwlwifi: make no_160 more generic
> 
> https://git.kernel.org/linus/64dc5d5e341d ("Revert "wifi: iwlwifi:
> make no_160 more generic"") appeared in v6.15-rc5 and reverts
> 75a3313f52b7 ("wifi: iwlwifi: make no_160 more generic"), so it
> *looks* like this regression should be fixed, but it still appears in
> the tracker at https://linux-regtracking.leemhuis.info/regzbot/mainline/
> 

And for 6.16 it was completely reworked. But I don't really know if
there might still be related issues.

johannes

Re: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22

[Chris Bainbridge]

On Wed, 16 Jul 2025 at 19:42, Bjorn Helgaas <helgaas@kernel.org> wrote:
>
> On Fri, Mar 28, 2025 at 12:36:38AM +0000, Chris Bainbridge wrote:
> > Hi,
> >
> > Laptop: Lenovo Legion 7 16ACHg6.
> > Wifi: Killer(R) Wi-Fi 6 AX1650x 160MHz Wireless Network Adapter (200NGW)
> > 04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
> >
> > Wifi stopped working in recent kernel builds:
> >
> > [   20.907824] Intel(R) Wireless WiFi driver for Linux
> > [   20.907955] iwlwifi 0000:04:00.0: enabling device (0000 -> 0002)
> > [   20.912024] ee1004 2-0050: 512 byte EE1004-compliant SPD EEPROM, read-only
> > [   20.913666] NET: Registered PF_BLUETOOTH protocol family
> > [   20.913670] Bluetooth: HCI device and connection manager initialized
> > [   20.913806] Bluetooth: HCI socket layer initialized
> > [   20.913810] Bluetooth: L2CAP socket layer initialized
> > [   20.913828] Bluetooth: SCO socket layer initialized
> > [   20.917455] iwlwifi 0000:04:00.0: Detected crf-id 0x3617, cnv-id 0x100530 wfpm id 0x80000000
> > [   20.917674] iwlwifi 0000:04:00.0: PCI dev 2723/1654, rev=0x340, rfid=0x10a100
> > [   20.917679] iwlwifi: No config found for PCI dev 2723/1654, rev=0x340, rfid=0x10a100
> > [   20.920126] iwlwifi 0000:04:00.0: probe with driver iwlwifi failed with error -22
> >
> > Bisect led to:
> >
> > commit 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b (HEAD)
> > Author: Emmanuel Grumbach <emmanuel.grumbach@intel.com>
> > Date:   Wed Feb 5 14:55:42 2025 +0200
> >
> >     wifi: iwlwifi: make no_160 more generic
>
> https://git.kernel.org/linus/64dc5d5e341d ("Revert "wifi: iwlwifi:
> make no_160 more generic"") appeared in v6.15-rc5 and reverts
> 75a3313f52b7 ("wifi: iwlwifi: make no_160 more generic"), so it
> *looks* like this regression should be fixed, but it still appears in
> the tracker at https://linux-regtracking.leemhuis.info/regzbot/mainline/
>
> If it is resolved, can somebody send the appropriate regzbot fix
> command?  (See https://linux-regtracking.leemhuis.info/about/#tldr)

Yes, that revert fixed it.

#regzbot fix: 64dc5d5e341d