Received-SPF: pass (google.com: domain of linux-wireless+bounces-4254-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: <5cd86456-ff2b-4e4a-aa12-1e11e5de92a5@aixigo.com>
Date: Thu, 29 Feb 2024 15:45:41 +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>
 <b9b2224a-f021-483a-8606-6aed94c5f6f9@aixigo.com>
 <795b376aa2c9112527cf135a5176f01c6af69ade.camel@sipsolutions.net>
From: Harald Dunkel <harald.dunkel@aixigo.com>
Content-Language: en-US
In-Reply-To: <795b376aa2c9112527cf135a5176f01c6af69ade.camel@sipsolutions.net>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit

Hi Johannes,

On 2024-02-28 11:30:44, Johannes Berg wrote:
> On Wed, 2024-02-28 at 11:23 +0100, Harald Dunkel wrote:
> 
>> It used to work with the same kernel.
> 
> OK.
> 
>> This is what we get for the new (6.5.10, Debian backports) kernel now:
> 
> But that'd mean it's working - or are you saying that's a different
> machine?
> 

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.


>> [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
> 
> This seems to work, has a proper PCI ID, and shows a different RF ID?
> 

Yes, I would say so.

> You previously showed
> 
> iwlwifi: No config found for PCI dev 51f1/0000, rev=0x370, rfid=0x1010c000
> 
> So I think it'd still be interesting to know this line from the system
> that doesn't work any more, to see if it really was _exactly_ the same,
> as this before and changed, or whatever happened.
> 

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=0x370, rfid=0x1010c000
2024-02-26T13:21:24.361666+01:00 ppcl013 kernel: [   20.136735] iwlwifi: No config found for PCI dev 51f1/0000, rev=0x370, rfid=0x1010c000
2024-02-26T15:30:25.639827+01:00 ppcl013 kernel: [   38.203931] iwlwifi 0000:00:14.3: PCI dev 51f1/0000, rev=0x370, rfid=0x3010a100
2024-02-26T15:30:25.639828+01:00 ppcl013 kernel: [   38.204862] iwlwifi: No config found for PCI dev 51f1/0000, rev=0x370, rfid=0x3010a100
2024-02-26T20:45:28.752692+01:00 ppcl013 kernel: [   21.294757] iwlwifi 0000:00:14.3: PCI dev 51f1/0074, rev=0x370, rfid=0x10a100
2024-02-26T20:45:28.752723+01:00 ppcl013 kernel: [   21.813877] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
2024-02-27T09:11:49.132498+01:00 ppcl013 kernel: [   48.939136] iwlwifi 0000:00:14.3: PCI dev 51f1/0074, rev=0x370, rfid=0x10a100
2024-02-27T09:11:49.132582+01:00 ppcl013 kernel: [   49.420458] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
2024-02-27T09:44:52.740746+01:00 ppcl013 kernel: [   57.435249] iwlwifi 0000:00:14.3: PCI dev 51f1/0074, rev=0x370, rfid=0x10a100
2024-02-27T09:44:52.740759+01:00 ppcl013 kernel: [   57.764033] iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100

> 
>>> 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.
> 
> Yes, that's what I mean.
> 

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


Regards

Harri