Received-SPF: pass (google.com: domain of linux-wireless+bounces-4175-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Message-ID: <b9b2224a-f021-483a-8606-6aed94c5f6f9@aixigo.com>
Date: Wed, 28 Feb 2024 11:23:04 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Betterbird (Linux)
Subject: Re: "iwlwifi: probe of 0000:00:14.3 failed with error -22"
To: Johannes Berg <johannes@sipsolutions.net>, linux-wireless@vger.kernel.org
References: <dd1e2440-bb05-48d7-9f68-29bae758110d@aixigo.com>
 <9edf7003715cfdda3c794f3adbaeac5f36ada8ee.camel@sipsolutions.net>
From: Harald Dunkel <harald.dunkel@aixigo.com>
Content-Language: en-US
In-Reply-To: <9edf7003715cfdda3c794f3adbaeac5f36ada8ee.camel@sipsolutions.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

On 2024-02-27 10:21:13, Johannes Berg wrote:
> On Tue, 2024-02-27 at 09:12 +0100, Harald Dunkel wrote:
>> The Intel Wifi hardware of a colleague's Tuxedo laptop (running Debian 12,
>> kernel 6.1.76) isn't found at boot time anymore. It doesn't come back on a
>> reboot. The kernel log shows
>>
>> [Mon Feb 26 13:21:23 2024] Intel(R) Wireless WiFi driver for Linux
>> [Mon Feb 26 13:21:23 2024] RAPL PMU: API unit is 2^-32 Joules, 3 fixed counters, 655360 ms ovfl timer
>> [Mon Feb 26 13:21:23 2024] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
>> [Mon Feb 26 13:21:23 2024] iwlwifi 0000:00:14.3: Adding cdb to rf id
>> [Mon Feb 26 13:21:23 2024] iwlwifi 0000:00:14.3: Detected RF 0x1010c000 from crf id 0x504
>> [Mon Feb 26 13:21:23 2024] iwlwifi: No config found for PCI dev 51f1/0000, rev=0x370, rfid=0x1010c000
>> [Mon Feb 26 13:21:23 2024] iwlwifi: probe of 0000:00:14.3 failed with error -22
> 
> Are you saying that it used to work with that same kernel, or are you
> saying that it worked with an older kernel?
> 

It used to work with the same kernel. We had configured 5 identical laptops
in the office, including wifi. After some time this one laptop showed the
problem. AFAIU it crashed first, but I have no records about this.

My colleague turned off the laptop for a power off reset over night (if this
is possible for a laptop with a batter). Next morning Wifi was back. Seems
to be some reset issue.

> In either case, do you have a working log?
> 

This is what we get for the new (6.5.10, Debian backports) kernel now:

```
root@ppcl013:~# dmesg -T | egrep -i wifi\|00:14.3
[Tue Feb 27 09:43:54 2024] pci 0000:00:14.3: [8086:51f1] type 00 class 0x028000
[Tue Feb 27 09:43:54 2024] pci 0000:00:14.3: reg 0x10: [mem 0x601d174000-0x601d177fff 64bit]
[Tue Feb 27 09:43:54 2024] pci 0000:00:14.3: PME# supported from D0 D3hot D3cold
[Tue Feb 27 09:43:54 2024] pci 0000:00:14.3: Adding to iommu group 8
[Tue Feb 27 09:44:51 2024] Intel(R) Wireless WiFi driver for Linux
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: Detected crf-id 0x1300504, cnv-id 0x80400 wfpm id 0x80000030
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: PCI dev 51f1/0074, rev=0x370, rfid=0x10a100
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: firmware: direct-loading firmware iwlwifi-so-a0-hr-b0-83.ucode
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.41
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: firmware: failed to load iwl-debug-yoyo.bin (-2)
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: loaded firmware version 83.e8f84e98.0 so-a0-hr-b0-83.ucode op_mode iwlmvm
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x370
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[Tue Feb 27 09:44:51 2024] iwlwifi 0000:00:14.3: base HW address: e4:0d:xx:xx:xx:xx
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: Registered PHC clock: iwlwifi-PTP, with index: 0
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WRT: Invalid buffer destination
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WFPM_UMAC_PD_NOTIFICATION: 0x20
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WFPM_LMAC2_PD_NOTIFICATION: 0x1f
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: WFPM_AUTH_KEY_0: 0x90
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: CNVI_SCU_SEQ_DATA_DW9: 0x10
[Tue Feb 27 09:44:52 2024] iwlwifi 0000:00:14.3: RFIm is deactivated, reason = 4
[Tue Feb 27 09:47:12 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
[Tue Feb 27 09:47:12 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
[Tue Feb 27 09:47:12 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
[Wed Feb 28 09:47:03 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
[Wed Feb 28 09:47:03 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
[Wed Feb 28 09:47:03 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
[Wed Feb 28 09:47:03 2024] iwlwifi 0000:00:14.3: Unhandled alg: 0x703
```

Hope this helps.

> If you really have subdevice ID 0000 then something went wrong and you
> have a blank OTP (now), which seems very strange.
> 
> This is an integrated NIC where part of the NIC is integrated into the
> platform, and other parts are on the companion RF (CRF), so could also
> be that the CRF module isn't seated well any more in the slot and it
> just cannot access the data properly?
> 

You mean there could be a problem with the wifi card not being plugged in
properly? We will check when my colleague is in the office.


Regards
Harri