Received-SPF: pass (google.com: domain of linux-wireless+bounces-4256-linux.lists.archive=gmail.com@vger.kernel.org designates 139.178.88.99 as permitted sender) client-ip=139.178.88.99;
Message-ID: <88fe8575145bbd78a8207537dae85c81aa4955f0.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: Thu, 29 Feb 2024 16:00:56 +0100
In-Reply-To: <5cd86456-ff2b-4e4a-aa12-1e11e5de92a5@aixigo.com>
References: <dd1e2440-bb05-48d7-9f68-29bae758110d@aixigo.com>
	 <9edf7003715cfdda3c794f3adbaeac5f36ada8ee.camel@sipsolutions.net>
	 <b9b2224a-f021-483a-8606-6aed94c5f6f9@aixigo.com>
	 <795b376aa2c9112527cf135a5176f01c6af69ade.camel@sipsolutions.net>
	 <5cd86456-ff2b-4e4a-aa12-1e11e5de92a5@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

Hi Harald,

> The laptop recovered on a power off reset over night. It worked again
> on the next morning (I was told). I logged in via VPN to upgrade kernel
> and ucode file. My colleague rebooted it once again, and it is still
> working.

Fun :)

Well also good I guess. No idea what could have happened though.

> root@ppcl013:~# grep rfid /var/log/kern.log
> 2024-02-26T09:55:24.858020+01:00 ppcl013 kernel: [   82.527151] iwlwifi: =
No config found for PCI dev 51f1/0000, rev=3D0x370, rfid=3D0x1010c000
> 2024-02-26T13:21:24.361666+01:00 ppcl013 kernel: [   20.136735] iwlwifi: =
No config found for PCI dev 51f1/0000, rev=3D0x370, rfid=3D0x1010c000
> 2024-02-26T15:30:25.639827+01:00 ppcl013 kernel: [   38.203931] iwlwifi 0=
000:00:14.3: PCI dev 51f1/0000, rev=3D0x370, rfid=3D0x3010a100
> 2024-02-26T15:30:25.639828+01:00 ppcl013 kernel: [   38.204862] iwlwifi: =
No config found for PCI dev 51f1/0000, rev=3D0x370, rfid=3D0x3010a100
> 2024-02-26T20:45:28.752692+01:00 ppcl013 kernel: [   21.294757] iwlwifi 0=
000:00:14.3: PCI dev 51f1/0074, rev=3D0x370, rfid=3D0x10a100
> 2024-02-26T20:45:28.752723+01:00 ppcl013 kernel: [   21.813877] iwlwifi 0=
000:00:14.3: Detected RF HR B3, rfid=3D0x10a100
> 2024-02-27T09:11:49.132498+01:00 ppcl013 kernel: [   48.939136] iwlwifi 0=
000:00:14.3: PCI dev 51f1/0074, rev=3D0x370, rfid=3D0x10a100
> 2024-02-27T09:11:49.132582+01:00 ppcl013 kernel: [   49.420458] iwlwifi 0=
000:00:14.3: Detected RF HR B3, rfid=3D0x10a100
> 2024-02-27T09:44:52.740746+01:00 ppcl013 kernel: [   57.435249] iwlwifi 0=
000:00:14.3: PCI dev 51f1/0074, rev=3D0x370, rfid=3D0x10a100
> 2024-02-27T09:44:52.740759+01:00 ppcl013 kernel: [   57.764033] iwlwifi 0=
000:00:14.3: Detected RF HR B3, rfid=3D0x10a100

That's interesting though because at one point it bound to it properly,
but still had a 0000 PCI ID and the (likely wrong) RFID 0x3010a100, vs.
most of the working cases have 0074 PCI ID and 0x10a100 RFID.

So looks like something is not quite stable with this system, but it
still worked most of the time!

> We will check when my colleague is back from home office, but this
> might take some time.

Sure. Seems to work now, so at least that's good, I guess.

I still think this might be an issue here, or maybe the CRF is just
flaky somehow? Don't have any experience with these kind of issues
either, TBH.

Anyway, glad it works again.

johannes