Where you able to work around this error?
I'm seeing the same sysassert, with a single ax200 and no adaptor.

[    8.812119] iwlwifi 0000:01:00.0: 0x201000A3 | ADVANCED_SYSASSERT

On occassion I've seen sysassert 0x222. In another bug they mention 0x222 could be due to pci timing issues. However I'm using this card in the same slot that used to host another intel wifi card, 7260, for years without a problem.

I bought a single mpcie->ngff adapter and tested that with a single ax200 and still the same failure.  other devices work, intel ax200 does not.

I'm going to let the assignee mark this if they agree, but this is probably a dupe of https://bugzilla.kernel.org/show_bug.cgi?id=204821

This doesn't seem to be related to 204821, but thanks for pointing it out.

We will investigate what is causing this issue.

*** Bug 205499 has been marked as a duplicate of this bug. ***

I'm facing the same issue with Ubuntu Desktop 20.04 (64 bit) with kernel 5.2.21 and 5.4.

My card (Asus PCE-AX58BT) is plugged into a PCIe 3.0 x8 slot.


Kernel 5.2.21-050221:

[    2.045735] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[    2.058883] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-48.ucode failed with error -2
[    2.058891] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-cc-a0-47.ucode failed with error -2
[    2.060354] iwlwifi 0000:02:00.0: loaded firmware version 46.3cfab8da.0 op_mode iwlmvm
[    2.086464] iwlwifi 0000:02:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[    3.110094] iwlwifi 0000:02:00.0: Collecting data: trigger 15 fired.
[    3.110164] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[    3.110166] iwlwifi 0000:02:00.0: Status: 0x00000000, count: 6
[    3.110167] iwlwifi 0000:02:00.0: Loaded firmware version: 46.3cfab8da.0
[    3.110169] iwlwifi 0000:02:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[    3.110175] iwlwifi 0000:02:00.0: 0x002022F0 | trm_hw_status0
[    3.110175] iwlwifi 0000:02:00.0: 0x00000000 | trm_hw_status1
[    3.110176] iwlwifi 0000:02:00.0: 0x004FC308 | branchlink2
[    3.110177] iwlwifi 0000:02:00.0: 0x004E8926 | interruptlink1
[    3.110178] iwlwifi 0000:02:00.0: 0x004E8926 | interruptlink2
[    3.110179] iwlwifi 0000:02:00.0: 0x004F72AE | data1
[    3.110179] iwlwifi 0000:02:00.0: 0x00001000 | data2
[    3.110180] iwlwifi 0000:02:00.0: 0xF0000000 | data3
[    3.110181] iwlwifi 0000:02:00.0: 0x00000000 | beacon time
[    3.110182] iwlwifi 0000:02:00.0: 0x0000CBC9 | tsf low
[    3.110183] iwlwifi 0000:02:00.0: 0x00000000 | tsf hi
[    3.110184] iwlwifi 0000:02:00.0: 0x00000000 | time gp1
[    3.110184] iwlwifi 0000:02:00.0: 0x0000CBC9 | time gp2
[    3.110185] iwlwifi 0000:02:00.0: 0x00000001 | uCode revision type
[    3.110186] iwlwifi 0000:02:00.0: 0x0000002E | uCode version major
[    3.110187] iwlwifi 0000:02:00.0: 0x3CFAB8DA | uCode version minor
[    3.110188] iwlwifi 0000:02:00.0: 0x00000340 | hw version
[    3.110194] iwlwifi 0000:02:00.0: 0x00C89000 | board version
[    3.110196] iwlwifi 0000:02:00.0: 0x8000FD11 | hcmd
[    3.110197] iwlwifi 0000:02:00.0: 0x00020000 | isr0
[    3.110197] iwlwifi 0000:02:00.0: 0x00000000 | isr1
[    3.110198] iwlwifi 0000:02:00.0: 0x08F00002 | isr2
[    3.110199] iwlwifi 0000:02:00.0: 0x00C0000C | isr3
[    3.110200] iwlwifi 0000:02:00.0: 0x00000000 | isr4
[    3.110201] iwlwifi 0000:02:00.0: 0x00000000 | last cmd Id
[    3.110201] iwlwifi 0000:02:00.0: 0x004F72AE | wait_event
[    3.110202] iwlwifi 0000:02:00.0: 0x00000000 | l2p_control
[    3.110203] iwlwifi 0000:02:00.0: 0x00000020 | l2p_duration
[    3.110204] iwlwifi 0000:02:00.0: 0x00000000 | l2p_mhvalid
[    3.110205] iwlwifi 0000:02:00.0: 0x00000000 | l2p_addr_match
[    3.110205] iwlwifi 0000:02:00.0: 0x00000009 | lmpm_pmg_sel
[    3.110206] iwlwifi 0000:02:00.0: 0x16042142 | timestamp
[    3.110209] iwlwifi 0000:02:00.0: 0x0000F81C | flow_handler
[    3.110233] iwlwifi 0000:02:00.0: Start IWL Error Log Dump:
[    3.110233] iwlwifi 0000:02:00.0: Status: 0x00000000, count: 7
[    3.110234] iwlwifi 0000:02:00.0: 0x20100222 | ADVANCED_SYSASSERT
[    3.110235] iwlwifi 0000:02:00.0: 0x00000000 | umac branchlink1
[    3.110236] iwlwifi 0000:02:00.0: 0xC008B1C0 | umac branchlink2
[    3.110237] iwlwifi 0000:02:00.0: 0x8048CE9E | umac interruptlink1
[    3.110238] iwlwifi 0000:02:00.0: 0x00000000 | umac interruptlink2
[    3.110238] iwlwifi 0000:02:00.0: 0xDEADBEEF | umac data1
[    3.110239] iwlwifi 0000:02:00.0: 0xDEADBEEF | umac data2
[    3.110240] iwlwifi 0000:02:00.0: 0xDEADBEEF | umac data3
[    3.110241] iwlwifi 0000:02:00.0: 0x0000002E | umac major
[    3.110242] iwlwifi 0000:02:00.0: 0x3CFAB8DA | umac minor
[    3.110243] iwlwifi 0000:02:00.0: 0x0000CBB2 | frame pointer
[    3.110243] iwlwifi 0000:02:00.0: 0xC0886B04 | stack pointer
[    3.110244] iwlwifi 0000:02:00.0: 0x0000FFFF | last host cmd
[    3.110245] iwlwifi 0000:02:00.0: 0x00000000 | isr status reg
[    3.110250] iwlwifi 0000:02:00.0: Fseq Registers:
[    3.110253] iwlwifi 0000:02:00.0: 0x20000000 | FSEQ_ERROR_CODE
[    3.110255] iwlwifi 0000:02:00.0: 0x80290001 | FSEQ_TOP_INIT_VERSION
[    3.110258] iwlwifi 0000:02:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[    3.110261] iwlwifi 0000:02:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[    3.110263] iwlwifi 0000:02:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[    3.110266] iwlwifi 0000:02:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[    3.110269] iwlwifi 0000:02:00.0: 0x00100530 | FSEQ_CNVI_ID
[    3.110271] iwlwifi 0000:02:00.0: 0x00000532 | FSEQ_CNVR_ID
[    3.110274] iwlwifi 0000:02:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[    3.110279] iwlwifi 0000:02:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[    3.110283] iwlwifi 0000:02:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[    3.110288] iwlwifi 0000:02:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[    3.110305] iwlwifi 0000:02:00.0: SecBoot CPU1 Status: 0x5fb0, CPU2 Status: 0x3
[    3.110306] iwlwifi 0000:02:00.0: Failed to start RT ucode: -110
[    3.110308] iwlwifi 0000:02:00.0: Firmware not running - cannot dump error
[    3.123412] iwlwifi 0000:02:00.0: Failed to run INIT ucode: -110

Some previously suggested that this issue could have something to do with the type of PCIe slot.

In my case (Wifi card: Asus PCE-AX58BT) the Asus support claims that the card will only work in a PCIe x1 slot and will not work in a x4, x8, x16 slot. It should not have anything to do with PCIe gen2 or gen3.
They specifically mentioned that this information came from their Taiwanese colleges. I guess that this information was added to imply that they are closer to the development of that card and have more knowledge.

To me all of this is super strange and does not make sense. PCIe x1 cards should be compatible with x4, x8 and x16.
Since I was stuck with this issue for 5 months I did send the card back and gave up on using Wifi on Linux.

I have no clue what cards other users with this issue have, but I thought I would leave this information here. Maybe it helps in anyway.

I just got a fenvi FV-AX3000 card, which at its core uses an Intel AX200. I was getting the same log from the kernel as above with RT ucode: -110, until I did some more snooping around.

I originally plugged in the card to one of the x16 slots on my motherboard (Gigabyte Z77X-UD5H motherboard, CPU is an Intel i7-3770k), which according to the user manual for the motherboard, due to my current configuration, should now be operating with x4 lanes (8x lanes for my GPU, x4 lanes for a 1x sound card, and x4 lanes for the 1x AX200). These lanes are managed directly by the CPU as far as I can tell, per CPU and motherboard documentation. It was in this configuration that I got the RT ucode errors, and the card refused to work on Windows as well.

As per comment 7, I happened to have one poorly placed 1x PCI-E slot available (right under the GPU..., blocking some airflow to it). I switched the AX200 card to this 1x slot, which is managed by the motherboard's chipset instead of the CPU, and... the card loaded:

[   33.632318] cfg80211: Loading compiled-in X.509 certificates for regulatory database
[   33.633710] cfg80211: Loaded X.509 cert 'sforshee: 00b28ddf47aef9cea7'
[   33.637366] Intel(R) Wireless WiFi driver for Linux
[   33.637367] Copyright(c) 2003- 2015 Intel Corporation
[   33.637397] iwlwifi 0000:06:00.0: enabling device (0100 -> 0102)
[   33.643015] iwlwifi 0000:06:00.0: api flags index 2 larger than supported by driver
[   33.643021] iwlwifi 0000:06:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 68.3.35.22
[   33.643024] iwlwifi 0000:06:00.0: Found debug destination: EXTERNAL_DRAM
[   33.643024] iwlwifi 0000:06:00.0: Found debug configuration: 0
[   33.643197] iwlwifi 0000:06:00.0: loaded firmware version 53.c31ac674.0 cc-a0-53.ucode op_mode iwlmvm
[   33.643211] iwlwifi 0000:06:00.0: Direct firmware load for iwl-debug-yoyo.bin failed with error -2
[   33.654918] iwlwifi 0000:06:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[   33.845091] iwlwifi 0000:06:00.0: base HW address: f8:e4:e3:00:a8:8e
[   33.857641] thermal thermal_zone3: failed to read out thermal zone (-61)
[   33.857974] systemd-udevd[2525]: Using default interface naming scheme 'v245'.
[   33.858295] systemd-udevd[2525]: ethtool: autonegotiation is unset or enabled, the speed and duplex are not writable.
[   33.858372] iwlwifi 0000:06:00.0 wlp6s0: renamed from wlan0
[   33.877736] systemd-udevd[2525]: wlan0: Process 'net.sh wlp6s0 start' failed with exit code 1.
[   37.895263] wlp6s0: authenticate with c2:56:27:6e:77:44
[   37.897414] wlp6s0: send auth to c2:56:27:6e:77:44 (try 1/3)
[   37.922976] wlp6s0: authenticated
[   37.926295] wlp6s0: associate with c2:56:27:6e:77:44 (try 1/3)
[   37.946948] wlp6s0: RX AssocResp from c2:56:27:6e:77:44 (capab=0x431 status=0 aid=2)
[   37.951616] wlp6s0: associated
[   37.964058] IPv6: ADDRCONF(NETDEV_CHANGE): wlp6s0: link becomes ready
[   76.920106] elogind-daemon[1845]: Removed session 2.
[   76.978916] elogind-daemon[1845]: Removed session 3.
[   77.529926] elogind-daemon[1845]: New session 3 of user root.
[   90.962303] elogind-daemon[1845]: Removed session 3.
[   90.971156] elogind-daemon[1845]: New session 4 of user gabriel.
[   92.317347] Bluetooth: RFCOMM TTY layer initialized
[   92.317351] Bluetooth: RFCOMM socket layer initialized
[   92.317352] Bluetooth: RFCOMM ver 1.11
[   92.626219] usb 1-1.3: reset high-speed USB device number 5 using ehci-pci

PCI-E is one of the parts of modern systems I'm less familiar with, but to me it sounds like the problem could be one of the following (or more, these are the ones I can think of):
1. Somehow either the AX200 or the surrounding electronics on the wifi card (I don't think there's much there, so I think it's just the AX200) fails to negotiate the number of lanes it needs properly. (I have another 1x card, an Asus sound card, and that negotiates fine).
2. There's a bug or a hardware defect on the AX200 preventing it from communicating properly with the CPU PCI-E controller. Like I mentioned earlier, I have another 1x PCI-E card connected to one of the ports that connects to the CPU PCI-E controller, and that one works wonderfully.
3. Maybe my CPU is old enough that there's some incompatibility between it and the AX200. Still, the motherboard x1 port works just fine (in fact, I'm submitting this over wifi using the AX200).

Because I can reproduce this reliably, and can work around it, let me know what information you would need from me to debug this, if anything.

Hi,

I'm having the same issue with this card (integrated into the motherboard) and I dug a bit inside the code.

The code in (iwlmvm/fw.c) waits for an alive notification and then times out.
iwl_mvm_load_ucode_wait_alive will runn iwl_wait_notification which times out with err -110.

I don't know exactly how it works but iwlmvm starts the firmware (which does not error) and then waits for the firmware to ping that it's alive so it can continue with the setup. This alive ping is not being received hence it times out.

I've also bought a Fenvi FV-AX3000 card today, based on AX200. It is plugged into the PCIe x16 slot on my Gigabyte H87N-WIFI motherboard.

My kernel is vanilla 5.7.12 with iwlwifi compiled in.
The firmware always crashes at startup with:

> iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
> iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110

Full log attached.

Looking at comment #8, re-plugging the card in an x1 slot could have helped,
but my MB doesn't have any.
The only PCIe slot it has is an x16 intended for the discrete GPU which I don't need anyway.

I guess I may as well throw the card into the garbage bin...
Or is it something that can eventually be fixed on the driver/firmware level?

Created attachment 290711 [details]
Firmware crash log

I can confirm that the AX200 works OK when plugged in a x1 PCIe slot, and does NOT work in a x16 slot. In the later case it generates the before-mentioned 

 "NMI_INTERRUPT_UMAC_FATAL"

followed in the logs by 

 iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
 iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110


My setup is 
* Gigabyte Z97M-DS3H motherboard
* Fenvi FV-AX200 PCIe x1 adapter card with an Intel AX200NGW NGFF M.2 card
* CentOS 7 (stock 3.10.0-1127.19.1.el7 and mainline 5.8.7 kernels tested)

I want to point out that the adapter card works fine in the x16 slot when used with another WiFi module (DELL's DW1820), so the problem clearly lies with the AX200 not negotiating its PCIe configuration with the motherboard/chipset.

The above comment

(In reply to Sebastian Penhouet from comment #7)
> In my case (Wifi card: Asus PCE-AX58BT) the Asus support claims that the card
> will only work in a PCIe x1 slot and will not work in a x4, x8, x16 slot.

is unlikely to be universally applicable to the other AX200 cards.

My WiFi+Bluetooth card Asus PCE-AX3000 Dual Band (which apparently also uses the AX200 chip if we believe the output of lspci) is inserted into the PCIEX16_3 slot of the Asus WS C422 PRO/SE motherboard.  The motherboard has no x1 slots.  I am sending this very message using the aforementioned PCE-AX3000 card in the aforementioned x16 slot and an up-to-date Debian Bullseye with the kernel linux-image-5.10.0-1-amd64.  I can nevertheless complain that I don't get Internet directly when Linux boots but a few minutes later (reason yet unknown).

The card works in Windows, too.

I have recently built a NAS server based on Openmediavault. "uname -a" gives me Debian 5.7.10. My motherboard is an Asus P11C-I and the Wifi PCIe card is an Asus PCE-AX3000 with Intel's AX200 Wifi 6 chip. There's only one PCIe slot available for use. I get the same error as reported above:


[    5.114638] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[    5.114831] iwlwifi 0000:01:00.0: Firmware not running - cannot dump error
[    5.126503] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110

I should also note that I went to kernel git to download what I think may be Intel's latest version of the u-code. But that one throws the same error:

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/

I just experienced this issue after rearranging PCIe adapters in my 0M5DCD board based box (Optiplex 390DT guts turned into Frankenputer.)  I moved the wifi6 adapter up to the x16 slot, where a renesas USB 3.0 card was working fine. 
 The EDUP branded Intel AX200 chipset based AX3000 Wifi 6 PCIe adapter did not show up after logging in.  I copied dmesg to find a list of iwlwifi errors.  I was able to reproduce this reliably.  It occurred with multiple kernels of version 5.10.24.  After moving the iwlwifi driven hardware back to a PCIe x1 slot, expected functionality resumed.
bits of dmesg
Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[   24.094230] iwlwifi 0000:01:00.0: [   24.094230] iwlwifi 0000:01:00.0: SecBoot CPU1 Status: 0x5ae1, CPU2 Status: 0x3
[   24.097475] iwlwifi 0000:01:00.0: UMAC PC: 0x80480218
[   24.100734] iwlwifi 0000:01:00.0: LMAC PC: 0x104
[   24.103913] iwlwifi 0000:01:00.0: WRT: Collecting data: ini trigger 13 fired.
[   24.107236] iwlwifi 0000 CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[   24.210615] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[   24.595248] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110

sorry for not formatting, I googled but didn't find any information about howto (except all MARKDOWNs I tried didn't work).
I do have the same problem in here: -110 bug
I have
- ASUS Z97 mainboard
- Xeon kernel
- kernel 5.11 (ubuntu 21.04)
- the card in slot pciex16_1

These all:

 0x20100222 | ADVANCED_SYSASSERT

 0x201000A3 | ADVANCED_SYSASSERT

and possibly the

 SecBoot CPU1 Status: 0x5ae1, CPU2 Status: 0x3

as well all point to a similar issue with (firmware) timeouts during PCIe DMA transactions.

I don't know if there's something with the link that makes it slower, or the timeouts are just really small, I guess we'll need to check.

ax200/ax210 does not work in x16 pcie slots in my experience.  Try x1 or x4 slots instead.

This happens here every now and then on a ThinkPad T470 with the latest BIOS installed and an internal Intel Wireless 8265 / 8275 adapter:

$ grep NMI_INTERRUPT_UMAC_FATAL  /var/log/system.log | tail -5
Dec 30 15:19:41 horus kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
Dec 30 15:19:42 horus kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
Dec 31 17:51:17 horus kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
Dec 31 17:51:21 horus kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
Jan  2 13:08:12 horus kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    

Full example:

kernel: iwlwifi 0000:04:00.0: Microcode SW error detected.  Restarting 0x2000000.
kernel: iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
kernel: iwlwifi 0000:04:00.0: Transport status: 0x0000004A, valid: 6
kernel: iwlwifi 0000:04:00.0: Loaded firmware version: 36.ca7b901d.0 8265-36.ucode
kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
kernel: iwlwifi 0000:04:00.0: 0x00000083 | trm_hw_status0
kernel: iwlwifi 0000:04:00.0: 0x00000000 | trm_hw_status1
kernel: iwlwifi 0000:04:00.0: 0x00024A8C | branchlink2
kernel: iwlwifi 0000:04:00.0: 0x0003AC1E | interruptlink1
kernel: iwlwifi 0000:04:00.0: 0x00004DD2 | interruptlink2
kernel: iwlwifi 0000:04:00.0: 0x00000000 | data1
kernel: iwlwifi 0000:04:00.0: 0x00001000 | data2
kernel: iwlwifi 0000:04:00.0: 0x03830000 | data3
kernel: iwlwifi 0000:04:00.0: 0x63810560 | beacon time
kernel: iwlwifi 0000:04:00.0: 0xFD6F9A71 | tsf low
kernel: iwlwifi 0000:04:00.0: 0x00000055 | tsf hi
kernel: iwlwifi 0000:04:00.0: 0x00000000 | time gp1
kernel: iwlwifi 0000:04:00.0: 0x26462734 | time gp2
kernel: iwlwifi 0000:04:00.0: 0x00000001 | uCode revision type
kernel: iwlwifi 0000:04:00.0: 0x00000024 | uCode version major
kernel: iwlwifi 0000:04:00.0: 0xCA7B901D | uCode version minor
kernel: iwlwifi 0000:04:00.0: 0x00000230 | hw version
kernel: iwlwifi 0000:04:00.0: 0x00C89000 | board version
kernel: iwlwifi 0000:04:00.0: 0x0A4F001C | hcmd
kernel: iwlwifi 0000:04:00.0: 0x26FE3002 | isr0
kernel: iwlwifi 0000:04:00.0: 0x11800000 | isr1
kernel: iwlwifi 0000:04:00.0: 0x0800181A | isr2
kernel: iwlwifi 0000:04:00.0: 0x40412180 | isr3
kernel: iwlwifi 0000:04:00.0: 0x00000000 | isr4
kernel: iwlwifi 0000:04:00.0: 0x0A47001C | last cmd Id
kernel: iwlwifi 0000:04:00.0: 0x00000000 | wait_event
kernel: iwlwifi 0000:04:00.0: 0x00004A88 | l2p_control
kernel: iwlwifi 0000:04:00.0: 0x00019C24 | l2p_duration
kernel: iwlwifi 0000:04:00.0: 0x0000003F | l2p_mhvalid
kernel: iwlwifi 0000:04:00.0: 0x000000EF | l2p_addr_match
kernel: iwlwifi 0000:04:00.0: 0x0000001D | lmpm_pmg_sel
kernel: iwlwifi 0000:04:00.0: 0x10032209 | timestamp
kernel: iwlwifi 0000:04:00.0: 0x00002030 | flow_handler
kernel: iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
kernel: iwlwifi 0000:04:00.0: Transport status: 0x0000004A, valid: 7
kernel: iwlwifi 0000:04:00.0: 0x00000067 | ADVANCED_SYSASSERT
kernel: iwlwifi 0000:04:00.0: 0x00000000 | umac branchlink1
kernel: iwlwifi 0000:04:00.0: 0xC008694C | umac branchlink2
kernel: iwlwifi 0000:04:00.0: 0xC0083B0C | umac interruptlink1
kernel: iwlwifi 0000:04:00.0: 0xC0083B0C | umac interruptlink2
kernel: iwlwifi 0000:04:00.0: 0x00004000 | umac data1
kernel: iwlwifi 0000:04:00.0: 0xC0083B0C | umac data2
kernel: iwlwifi 0000:04:00.0: 0xDEADBEEF | umac data3
kernel: iwlwifi 0000:04:00.0: 0x00000024 | umac major
kernel: iwlwifi 0000:04:00.0: 0xCA7B901D | umac minor
kernel: iwlwifi 0000:04:00.0: 0xC088628C | frame pointer
kernel: iwlwifi 0000:04:00.0: 0xC088628C | stack pointer
kernel: iwlwifi 0000:04:00.0: 0x0086014E | last host cmd
kernel: iwlwifi 0000:04:00.0: 0x00000000 | isr status reg
kernel: iwlwifi 0000:04:00.0: IML/ROM dump:
kernel: iwlwifi 0000:04:00.0: 0x00000000 | IML/ROM error/state
kernel: iwlwifi 0000:04:00.0: 0x00000003 | IML/ROM data1
kernel: iwlwifi 0000:04:00.0: Fseq Registers:
kernel: iwlwifi 0000:04:00.0: 0x254FF6BE | FSEQ_ERROR_CODE
kernel: iwlwifi 0000:04:00.0: 0xEB4D862A | FSEQ_TOP_INIT_VERSION
kernel: iwlwifi 0000:04:00.0: 0x94078394 | FSEQ_CNVIO_INIT_VERSION
kernel: iwlwifi 0000:04:00.0: 0x0000A10B | FSEQ_OTP_VERSION
kernel: iwlwifi 0000:04:00.0: 0x23B1050F | FSEQ_TOP_CONTENT_VERSION
kernel: iwlwifi 0000:04:00.0: 0x2DFF3649 | FSEQ_ALIVE_TOKEN
kernel: iwlwifi 0000:04:00.0: 0xC953F0BA | FSEQ_CNVI_ID
kernel: iwlwifi 0000:04:00.0: 0x02B66AEC | FSEQ_CNVR_ID
kernel: iwlwifi 0000:04:00.0: 0x00000010 | CNVI_AUX_MISC_CHIP
kernel: iwlwifi 0000:04:00.0: 0x0BADCAFE | CNVR_AUX_MISC_CHIP
kernel: iwlwifi 0000:04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
kernel: iwlwifi 0000:04:00.0: 0x0BADCAFE | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
kernel: iwlwifi 0000:04:00.0: Collecting data: trigger 2 fired.
kernel: ieee80211 phy0: Hardware restart was requested
[...]


$ lspci -s 04:00.0 -v
04:00.0 Network controller: Intel Corporation Wireless 8265 / 8275 (rev 78)
        Subsystem: Intel Corporation Dual Band Wireless-AC 8265
        Flags: bus master, fast devsel, latency 0, IRQ 136
        Memory at ec100000 (64-bit, non-prefetchable) [size=8K]
        Capabilities: [c8] Power Management version 3
        Capabilities: [d0] MSI: Enable+ Count=1/1 Maskable- 64bit+
        Capabilities: [40] Express Endpoint, MSI 00
        Capabilities: [100] Advanced Error Reporting
        Capabilities: [140] Device Serial Number e4-70-b8-ff-ff-3f-cc-8f
        Capabilities: [14c] Latency Tolerance Reporting
        Capabilities: [154] L1 PM Substates
        Kernel driver in use: iwlwifi
        Kernel modules: iwlwifi

Is there an update to this?
Did anybody get the AX200 card working in a x16 slot?

I had no luck with kernel 5.16.12 (bullseye-backports) and firmware-iwlwifi 20210818-1

Thanks.

Disclaimer: I'm not a hardware programmer so I don't know how to evaluate the code and understand why it is breaking or what differences are between versions.

I got it working on a Lenovo Legion using the iwlwifi-cc-a0-48.ucode firmware. A clean install put it on the -63 version and Intel's website download is a -46 version.  

How to try this fix:

sudo caja (or your file organizer), or terminal using sudo mv /lib/firmware/<Applicable .ucode files> /your/desired/archive location 

search for iwlwifi and find the iwlwifi.cc-a0<version>.ucode files and move all but the one you want.  I moved the -46 and all other iwlwifi-cc-a0 versions out of /lib/firmware and left iwlwifi-cc-a0-48.ucode in /lib/firmware.   

//Please note that there are many .ucode files in /lib/firmware.  Move only the files iwlwifi-cc-a0[version.ucode] that you are isolating away from firmware loader.

sudo dmesg | grep iwlwifi will show a bunch of failed to load for the firmware that was moved out of /lib/firmware and then a successful load, in this case:

firmware: direct-loading firmware iwlwifi-cc-a0-48.ucode



If you happen to know how to tell the kernel which one to use instead of moving the ucode files out of /lib/firmware and causing all the startup loading errors please share.

I've spent a ridiculous amount of time researching a solution for this so I hope this helps a few people.

I forgot to specify that the above fix using iwlwifi-cc-a0-48.ucode is working on 5.16.0-12parrot1-amd64.  I haven't tested other higher versions of the .ucode yet.

(In reply to helios.solaris from comment #21)
> Did anybody get the AX200 card working in a x16 slot?
See my https://bugzilla.kernel.org/show_bug.cgi?id=205123#c13 .

I also have AX200 card with errors as mentioned above, and no wifi interface at startup.

I tried solution from @invalidhandle and it worked:

I left alone iwlwifi-cc-a0-50.ucode.zst (I don't have version 48) in /lib/firmware and rebooted. Then wifi was ok and I could connect to internet.

I tried also with iwlwifi-cc-a0-77.ucode.zst without success (no interface showing up).

I'm using kernel 6.6.2-arch1-1.