Received-SPF: pass (google.com: domain of linux-wireless+bounces-4065-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45d1:ec00::1 as permitted sender) client-ip=2604:1380:45d1:ec00::1;
Message-ID: <9edf7003715cfdda3c794f3adbaeac5f36ada8ee.camel@sipsolutions.net>
Subject: Re: "iwlwifi: probe of 0000:00:14.3 failed with error -22"
From: Johannes Berg <johannes@sipsolutions.net>
To: Harald Dunkel <harald.dunkel@aixigo.com>, linux-wireless@vger.kernel.org
Date: Tue, 27 Feb 2024 10:21:13 +0100
In-Reply-To: <dd1e2440-bb05-48d7-9f68-29bae758110d@aixigo.com>
References: <dd1e2440-bb05-48d7-9f68-29bae758110d@aixigo.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.50.4 (3.50.4-1.fc39) 
Precedence: bulk
MIME-Version: 1.0

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
>=20
> [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 co=
unters, 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 f=
rom crf id 0x504
> [Mon Feb 26 13:21:23 2024] iwlwifi: No config found for PCI dev 51f1/0000=
, rev=3D0x370, rfid=3D0x1010c000
> [Mon Feb 26 13:21:23 2024] iwlwifi: probe of 0000:00:14.3 failed with err=
or -22

Are you saying that it used to work with that same kernel, or are you
saying that it worked with an older kernel?

In either case, do you have a working log?

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?

johannes