> -----Original Message----- > From: Chris Bainbridge <chris.bainbridge@xxxxxxxxx> > Sent: Friday, 28 March 2025 3:37 > To: Grumbach, Emmanuel <emmanuel.grumbach@xxxxxxxxx> > Cc: linux-wireless@xxxxxxxxxxxxxxx; kvalo@xxxxxxxxxx; Korenblit, Miriam Rachel > <miriam.rachel.korenblit@xxxxxxxxx>; Berg, Johannes > <johannes.berg@xxxxxxxxx>; benjamin@xxxxxxxxxxxxxxxx; > regressions@xxxxxxxxxxxxxxx > 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@xxxxxxxxx> > 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@xxxxxxxxx> > Reviewed-by: Johannes Berg <johannes.berg@xxxxxxxxx> > Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@xxxxxxxxx> > Link: > https://patch.msgid.link/20250205145347.1ba406c538a5.I6e24123f60a764aedf > eaaac8768c26e136c320cf@changeid > Signed-off-by: Johannes Berg <johannes.berg@xxxxxxxxx> > > #regzbot introduced: 75a3313f52b7e08e7e73746f69a68c2b7c28bb2b Hi Chris, thanks for the report. We have a fix for that which will be sent soon. Thanks, Miri
