All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Bainbridge <chris.bainbridge@gmail.com>
To: "Grumbach, Emmanuel" <emmanuel.grumbach@intel.com>
Cc: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	"kvalo@kernel.org" <kvalo@kernel.org>,
	"Korenblit, Miriam Rachel" <miriam.rachel.korenblit@intel.com>,
	"Berg, Johannes" <johannes.berg@intel.com>,
	"benjamin@sipsolutions.net" <benjamin@sipsolutions.net>,
	"regressions@lists.linux.dev" <regressions@lists.linux.dev>
Subject: [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22
Date: Fri, 28 Mar 2025 00:36:38 +0000	[thread overview]
Message-ID: <Z-XvFvGigpY7JYFn@debian.local> (raw)

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

             reply	other threads:[~2025-03-28  0:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-28  0:36 Chris Bainbridge [this message]
2025-03-30  4:12 ` [REGRESSION] iwlwifi: probe with driver iwlwifi failed with error -22 Korenblit, Miriam Rachel
2025-04-23 15:06   ` Chris Bainbridge
2025-04-23 15:20     ` Johannes Berg
2025-07-16 18:42 ` Bjorn Helgaas
2025-07-16 20:34   ` Johannes Berg
2025-07-21 21:49   ` Chris Bainbridge

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=Z-XvFvGigpY7JYFn@debian.local \
    --to=chris.bainbridge@gmail.com \
    --cc=benjamin@sipsolutions.net \
    --cc=emmanuel.grumbach@intel.com \
    --cc=johannes.berg@intel.com \
    --cc=kvalo@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.