> Date: Mon, 8 Mar 2021 10:15:35 +0100 > From: Stefan Sperling <[email protected]> > > On Sun, Mar 07, 2021 at 05:14:08PM -0800, Greg Steuck wrote: > > I had an iwx working fine (modulo known issues) for a bit on amd64 current: > > > > iwx0 at pci0 dev 20 function 3 "Intel Wi-Fi 6 AX201" rev 0x00, msix > > iwx0: hw rev 0x350, fw ver 48.1335886879.0, address xxx > > > > Then for no discernible reason the kernel started saying: > > "Intel Wi-Fi 6 AX201" rev 0x00 at pci0 dev 20 function 3 not configured > > > > At first I blamed a kernel change, but booting into an old kernel didn't > > help. > > > > What did bring the device back is booting Linux kernel which had this to > > say: > > > > iwlwifi 0000:00:14.3: enabling device (0000 -> 0002) > > iwlwifi 0000:00:14.3: Direct firmware load for > > iwlwifi-QuZ-a0-hr-b0-56.ucode failed with error -2 > > iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver > > iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 65.3.35.22 > > iwlwifi 0000:00:14.3: Found debug destination: EXTERNAL_DRAM > > iwlwifi 0000:00:14.3: Found debug configuration: 0 > > iwlwifi 0000:00:14.3: loaded firmware version 55.d9698065.0 > > QuZ-a0-hr-b0-55.ucode op_mode iwlmvm > > iwlwifi 0000:00:14.3: Direct firmware load for iwl-debug-yoyo.bin failed > > with error -2 > > iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354 > > iwlwifi 0000:00:14.3: base HW address: xxx > > iwlwifi 0000:00:14.3 wlp0s20f3: renamed from wlan0 > > > > Maybe the "enabling device (0000 -> 0002)" part is what fixed the issue? > > > > Anyway, I got my iwx back though I still am curious why it went away. > > I don't know why this could happen. I would try to ask a PCI expert.
I think this can only happen if for some reason the subsystem ID match fails. So something corrupted that. Could be firmware or our driver code.
