Ubuntu
linux-firmware package

Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading error resulting in no wifi

Bug #1848831 reported by Ari
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
Gaming Edition
In Progress
Medium
linux-firmware (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Ubuntu 19.10 - stock kernel - Intel AX200 PCI card in a desktop PC

uname -a
Linux nahuatl 5.3.0-18-generic #19-Ubuntu SMP Tue Oct 8 20:14:06 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

The card is detected OK as dmesg shows, however the card's firmware fails immediately after loading (see dmesg output below) and wifi doesn't work at all. Big disappointment since the AX200 chip was supposed to be supported on 19.10.

Ubuntu includes two ax200 firmware versions, version 48 loads by default in my system (and fails). I tried version 46 (by renaming the version 48 file) and it failed in the exact same manner

$ ls /lib/firmware/iwlwifi-cc-*
/lib/firmware/iwlwifi-cc-a0-46.ucode /lib/firmware/iwlwifi-cc-a0-48.ucode

The card's Bluetooth functionality is also detected and it works fine. It's just the wifi FW loading what seems broken in ubuntu's 5.3 kernel.

$ rfkill list
0: hci0: Bluetooth
 Soft blocked: yes
 Hard blocked: no

~$ dmesg | grep iwl
[ 12.312443] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 12.321098] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 43.2.23.17
[ 12.321101] iwlwifi 0000:01:00.0: Found debug destination: EXTERNAL_DRAM
[ 12.321102] iwlwifi 0000:01:00.0: Found debug configuration: 0
[ 12.321309] iwlwifi 0000:01:00.0: loaded firmware version 48.4fa0041f.0 op_mode iwlmvm
[ 12.390389] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[ 12.400654] iwlwifi 0000:01:00.0: Applying debug destination EXTERNAL_DRAM
[ 12.400893] iwlwifi 0000:01:00.0: Allocated 0x00400000 bytes for firmware monitor.
[ 13.414781] iwlwifi 0000:01:00.0: Collecting data: trigger 15 fired.
[ 13.414908] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[ 13.414910] iwlwifi 0000:01:00.0: Status: 0x00000000, count: 6
[ 13.414911] iwlwifi 0000:01:00.0: Loaded firmware version: 48.4fa0041f.0
[ 13.414912] iwlwifi 0000:01:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 13.414913] iwlwifi 0000:01:00.0: 0x002022F0 | trm_hw_status0
[ 13.414913] iwlwifi 0000:01:00.0: 0x00000000 | trm_hw_status1
[ 13.414914] iwlwifi 0000:01:00.0: 0x004F8E3C | branchlink2
[ 13.414915] iwlwifi 0000:01:00.0: 0x004E4FF4 | interruptlink1
[ 13.414915] iwlwifi 0000:01:00.0: 0x004E4FF4 | interruptlink2
[ 13.414916] iwlwifi 0000:01:00.0: 0x004F3DB0 | data1
[ 13.414917] iwlwifi 0000:01:00.0: 0x00001000 | data2
[ 13.414917] iwlwifi 0000:01:00.0: 0xF0000000 | data3
[ 13.414918] iwlwifi 0000:01:00.0: 0x00000000 | beacon time
[ 13.414919] iwlwifi 0000:01:00.0: 0x0000795F | tsf low
[ 13.414919] iwlwifi 0000:01:00.0: 0x00000000 | tsf hi
[ 13.414920] iwlwifi 0000:01:00.0: 0x00000000 | time gp1
[ 13.414921] iwlwifi 0000:01:00.0: 0x0000DFD5 | time gp2
[ 13.414921] iwlwifi 0000:01:00.0: 0x00000001 | uCode revision type
[ 13.414922] iwlwifi 0000:01:00.0: 0x00000030 | uCode version major
[ 13.414923] iwlwifi 0000:01:00.0: 0x4FA0041F | uCode version minor
[ 13.414923] iwlwifi 0000:01:00.0: 0x00000340 | hw version
[ 13.414924] iwlwifi 0000:01:00.0: 0x18C89000 | board version
[ 13.414925] iwlwifi 0000:01:00.0: 0x8002FF03 | hcmd
[ 13.414925] iwlwifi 0000:01:00.0: 0x00020000 | isr0
[ 13.414926] iwlwifi 0000:01:00.0: 0x00000000 | isr1
[ 13.414926] iwlwifi 0000:01:00.0: 0x08F00002 | isr2
[ 13.414927] iwlwifi 0000:01:00.0: 0x00C0000C | isr3
[ 13.414928] iwlwifi 0000:01:00.0: 0x00000000 | isr4
[ 13.414928] iwlwifi 0000:01:00.0: 0x00000000 | last cmd Id
[ 13.414929] iwlwifi 0000:01:00.0: 0x004F3DB0 | wait_event
[ 13.414930] iwlwifi 0000:01:00.0: 0x00000000 | l2p_control
[ 13.414930] iwlwifi 0000:01:00.0: 0x00000020 | l2p_duration
[ 13.414931] iwlwifi 0000:01:00.0: 0x00000000 | l2p_mhvalid
[ 13.414932] iwlwifi 0000:01:00.0: 0x00000000 | l2p_addr_match
[ 13.414932] iwlwifi 0000:01:00.0: 0x00000009 | lmpm_pmg_sel
[ 13.414933] iwlwifi 0000:01:00.0: 0x00000000 | timestamp
[ 13.414934] iwlwifi 0000:01:00.0: 0x0000F81C | flow_handler
[ 13.414974] iwlwifi 0000:01:00.0: Start IWL Error Log Dump:
[ 13.414975] iwlwifi 0000:01:00.0: Status: 0x00000000, count: 7
[ 13.414976] iwlwifi 0000:01:00.0: 0x201000A3 | ADVANCED_SYSASSERT
[ 13.414976] iwlwifi 0000:01:00.0: 0x00000000 | umac branchlink1
[ 13.414977] iwlwifi 0000:01:00.0: 0xC008CC3C | umac branchlink2
[ 13.414978] iwlwifi 0000:01:00.0: 0xC0087660 | umac interruptlink1
[ 13.414978] iwlwifi 0000:01:00.0: 0x00000000 | umac interruptlink2
[ 13.414979] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data1
[ 13.414980] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data2
[ 13.414980] iwlwifi 0000:01:00.0: 0xDEADBEEF | umac data3
[ 13.414981] iwlwifi 0000:01:00.0: 0x00000030 | umac major
[ 13.414981] iwlwifi 0000:01:00.0: 0x4FA0041F | umac minor
[ 13.414982] iwlwifi 0000:01:00.0: 0x0000DFC9 | frame pointer
[ 13.414983] iwlwifi 0000:01:00.0: 0xC0886C1C | stack pointer
[ 13.414983] iwlwifi 0000:01:00.0: 0x0000FFFF | last host cmd
[ 13.414984] iwlwifi 0000:01:00.0: 0x00000000 | isr status reg
[ 13.414991] iwlwifi 0000:01:00.0: Fseq Registers:
[ 13.414994] iwlwifi 0000:01:00.0: 0xE0000000 | FSEQ_ERROR_CODE
[ 13.414998] iwlwifi 0000:01:00.0: 0x80290001 | FSEQ_TOP_INIT_VERSION
[ 13.415002] iwlwifi 0000:01:00.0: 0x80050008 | FSEQ_CNVIO_INIT_VERSION
[ 13.415006] iwlwifi 0000:01:00.0: 0x0000A503 | FSEQ_OTP_VERSION
[ 13.415010] iwlwifi 0000:01:00.0: 0x80000003 | FSEQ_TOP_CONTENT_VERSION
[ 13.415014] iwlwifi 0000:01:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
[ 13.415018] iwlwifi 0000:01:00.0: 0x00100530 | FSEQ_CNVI_ID
[ 13.415022] iwlwifi 0000:01:00.0: 0x00000532 | FSEQ_CNVR_ID
[ 13.415025] iwlwifi 0000:01:00.0: 0x00100530 | CNVI_AUX_MISC_CHIP
[ 13.415031] iwlwifi 0000:01:00.0: 0x00000532 | CNVR_AUX_MISC_CHIP
[ 13.415037] iwlwifi 0000:01:00.0: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[ 13.415043] iwlwifi 0000:01:00.0: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[ 13.415069] iwlwifi 0000:01:00.0: SecBoot CPU1 Status: 0x6558, CPU2 Status: 0x3
[ 13.415070] iwlwifi 0000:01:00.0: Failed to start RT ucode: -110
[ 13.415071] iwlwifi 0000:01:00.0: Firmware not running - cannot dump error
[ 13.426862] iwlwifi 0000:01:00.0: Failed to run INIT ucode: -110

ProblemType: Bug
DistroRelease: Ubuntu 19.10
Package: linux-firmware 1.183
ProcVersionSignature: Ubuntu 5.3.0-18.19-generic 5.3.1
Uname: Linux 5.3.0-18-generic x86_64
ApportVersion: 2.20.11-0ubuntu8
Architecture: amd64
CurrentDesktop: GNOME
Date: Sat Oct 19 00:25:44 2019
Dependencies:

InstallationDate: Installed on 2018-08-01 (443 days ago)
InstallationMedia: Ubuntu 18.04.1 LTS "Bionic Beaver" - Release amd64 (20180725)
PackageArchitecture: all
SourcePackage: linux-firmware
UpgradeStatus: Upgraded to eoan on 2019-10-18 (1 days ago)

Revision history for this message
In , sidhayn (sidhayn-linux-kernel-bugs) wrote :
Download full text (14.5 KiB)

I have a few different models of newer intel based wifi cards on a minipcie splitter/carrier board https://www.alftel.com/pages/product-airbud-pcie

When the hardware is detected during boot, all the intels on the carrier board fail to load/run their ucode. This is happening on a unit I have dedicated for testing, so I am available for any/all requested testing. Here is what it looks like:

[ 6.582036] iwlwifi 0000:12:00.0: WRT: collecting data: ini trigger 1 fired.
[ 6.582282] iwlwifi 0000:12:00.0: Start IWL Error Log Dump:
[ 6.582283] iwlwifi 0000:12:00.0: Status: 0x00000000, count: 6
[ 6.582283] iwlwifi 0000:12:00.0: Loaded firmware version: 48.4fa0041f.0
[ 6.582284] iwlwifi 0000:12:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL
[ 6.582285] iwlwifi 0000:12:00.0: 0x002022F0 | trm_hw_status0
[ 6.582285] iwlwifi 0000:12:00.0: 0x00000000 | trm_hw_status1
[ 6.582286] iwlwifi 0000:12:00.0: 0x004F8E3C | branchlink2
[ 6.582286] iwlwifi 0000:12:00.0: 0x004E4FF4 | interruptlink1
[ 6.582286] iwlwifi 0000:12:00.0: 0x004E4FF4 | interruptlink2
[ 6.582287] iwlwifi 0000:12:00.0: 0x004F3DB0 | data1
[ 6.582287] iwlwifi 0000:12:00.0: 0x00001000 | data2
[ 6.582288] iwlwifi 0000:12:00.0: 0xF0000000 | data3
[ 6.582288] iwlwifi 0000:12:00.0: 0x00000000 | beacon time
[ 6.582289] iwlwifi 0000:12:00.0: 0x00008B75 | tsf low
[ 6.582289] iwlwifi 0000:12:00.0: 0x00000000 | tsf hi
[ 6.582290] iwlwifi 0000:12:00.0: 0x00000000 | time gp1
[ 6.582290] iwlwifi 0000:12:00.0: 0x0000ED53 | time gp2
[ 6.582290] iwlwifi 0000:12:00.0: 0x00000001 | uCode revision type
[ 6.582291] iwlwifi 0000:12:00.0: 0x00000030 | uCode version major
[ 6.582291] iwlwifi 0000:12:00.0: 0x4FA0041F | uCode version minor
[ 6.582292] iwlwifi 0000:12:00.0: 0x00000340 | hw version
[ 6.582292] iwlwifi 0000:12:00.0: 0x00C89000 | board version
[ 6.582293] iwlwifi 0000:12:00.0: 0x8001FF03 | hcmd
[ 6.582293] iwlwifi 0000:12:00.0: 0x00020000 | isr0
[ 6.582294] iwlwifi 0000:12:00.0: 0x00000000 | isr1
[ 6.582294] iwlwifi 0000:12:00.0: 0x08F00002 | isr2
[ 6.582294] iwlwifi 0000:12:00.0: 0x00C0000C | isr3
[ 6.582295] iwlwifi 0000:12:00.0: 0x00000000 | isr4
[ 6.582295] iwlwifi 0000:12:00.0: 0x00000000 | last cmd Id
[ 6.582296] iwlwifi 0000:12:00.0: 0x004F3DB0 | wait_event
[ 6.582296] iwlwifi 0000:12:00.0: 0x00000000 | l2p_control
[ 6.582297] iwlwifi 0000:12:00.0: 0x00000020 | l2p_duration
[ 6.582297] iwlwifi 0000:12:00.0: 0x00000000 | l2p_mhvalid
[ 6.582298] iwlwifi 0000:12:00.0: 0x00000000 | l2p_addr_match
[ 6.582298] iwlwifi 0000:12:00.0: 0x00000009 | lmpm_pmg_sel
[ 6.582298] iwlwifi 0000:12:00.0: 0x00000000 | timestamp
[ 6.582299] iwlwifi 0000:12:00.0: 0x0000F81C | flow_handler
[ 6.582339] iwlwifi 0000:12:00.0: Start IWL Error Log Dump:
[ 6.582339] iwlwifi 0000:12:00.0: Status: 0x00000000, count: 7
[ 6.582340] iwlwifi 0000:12:00.0: 0x201000A3 | ADVANCED_SYSASSERT
[ 6.582340] iwlwifi 0000:12:00.0: 0x00000000 | umac branchlink1
[ 6.582341] iwlwifi 0000:12:00.0: 0xC008CC3C | umac branchlink2
[ 6.582341] iwlwifi 0000:12:00.0: 0xC0087660 | umac interruptlink1
[ 6.582342] iwlwifi 0000...

Revision history for this message
Ari (ari-reads) wrote :
Revision history for this message
Ari (ari-reads) wrote :

The issue could be in:

linux-modules-extra-5.3.0-18-generic

(iwlwifi module) rather than in intel's firmware

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Hi, could you also try mainline kernel https://kernel.ubuntu.com/~kernel-ppa/mainline/v5.4-rc3/ as well as backport-iwlwifi dkms from https://launchpad.net/~vicamo/+archive/ubuntu/backport-iwlwifi-dkms ? The firmware blobs in Eoan are already latest openly available ones.

Revision history for this message
Ari (ari-reads) wrote :

@vicamo I tested various combinations, here's the dmesg output:

stock 5.3 kernel + iwlwifi backport: https://paste.ubuntu.com/p/j6WDwqDJcd/

mainline 5.4rc3: https://paste.ubuntu.com/p/VnY6vZvqnC/

mainline 5.4rc3 + backported iwlwifi (there was an error inthe install, see notes in log): https://paste.ubuntu.com/p/WwpmGmPdvh/

Unfortunately no luck - in all cases the firmware errors out immediately after loading.
I noticed the 'trigger' is different with the backported iwlwifi.

FWIW I've seen some old reports of people getting AX200 to work on ubuntu 19.04 using 'mainline kernels' from June/July this year, and also 19.10 some ppl using the chipset on 19.10 daily builds prior to launch - this is why I decided to upgrade SW + change wifi card.

I also notice that the mainline iwlwifi module looks for firmware 50, then 49, and finally loads 48 which is the one that ubuntu ships. The one in the kernel tree is also 48, I wonder if intel keeps a "-next" tree of some sort somewhere where versions 49/50 could be present.

I found these kernel bug reports:

https://bugzilla.kernel.org/show_bug.cgi?id=205123

https://bugzilla.kernel.org/show_bug.cgi?id=204821

They both refer to the use of PCI slot adapters triggering the problem, which do not apply on my case. Motherboard: ASUS Maximus Gene Viii

Revision history for this message
In , ari.reads (ari.reads-linux-kernel-bugs) wrote :

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.

Revision history for this message
Ari (ari-reads) wrote :

Based on a few references and the issue in my system, it seems ax200 has issues with (at least) specific PCIE slot types X16, again at least with certain motherboards.X1/X4/X8 slots seem to work ok consistently. Hopefully this is fixable via firmware, so will retest once Intel releases the next few version

Revision history for this message
In , sidhayn (sidhayn-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , sidhayn (sidhayn-linux-kernel-bugs) wrote :

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

Revision history for this message
You-Sheng Yang (vicamo) wrote :

Hi, could you also attach output of `sudo lspci -vvnk -s 01:00.0`?

Revision history for this message
Zero_Chaos (sidhayn) wrote :

I'm not on ubuntu but I'm the same kernel with the same kernel bug and same hardware. Hope this helps anyway :-)

Revision history for this message
Ari (ari-reads) wrote :

For reference, here is the output, but with an old intel wifi card 7260 that works perfectly well and is installed in the same X16 PCIE slot where the AX200 fails to load its firmware.

The AX200 was supposed to replace the 7260 however due to this problem I've had to roll back the upgrade.

https://paste.ubuntu.com/p/FywHwCJYq5/

FWIW the system CPU is kabylake core i7, with a z170 chipset

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in linux-firmware (Ubuntu):
status: New → Confirmed
Revision history for this message
In , luca (luca-linux-kernel-bugs) wrote :

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

We will investigate what is causing this issue.

Revision history for this message
In , luca (luca-linux-kernel-bugs) wrote :

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

Bug Watch Updater (bug-watch-updater)
Changed in ubuntux:
importance: Unknown → Medium
status: Unknown → In Progress
Revision history for this message
Maheshwaran (maheshmaceee) wrote : Re: Intel WiFi AX200 firmware loading error resulting in no wifi

Any update on this issue? Dell latitude 7540 still reporting this issue.

Kernel : Linux 5.3.18-050318-generic

You-Sheng Yang (vicamo)
summary: - Intel WiFi AX200 firmware loading error resulting in no wifi
+ Intel WiFi AX200 [8086:08b1] subsystem [8086:4070] firmware loading
+ error resulting in no wifi
Revision history for this message
You-Sheng Yang (vicamo) wrote :

@Maheshwaran, if neither latest mainline kernel[1] nor backport-iwlwifi-dkms[2], along with latest linux-firmware[3], work for you, then probably we can only wait for updates to https://bugzilla.kernel.org/show_bug.cgi?id=205123 from Intel.

[1]: https://kernel.ubuntu.com/~kernel-ppa/mainline/
[2]: https://packages.ubuntu.com/focal/backport-iwlwifi-dkms
[3]: https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/

Revision history for this message
Christian Ohrfandl (christian-ohrfandl) wrote :
Download full text (9.2 KiB)

I get the same propblem on Ubuntu 20.04

uname -a
Linux christian-vie-ubuntu 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

sudo lspci -vvnk -s 01:00.0
01:00.0 0280: 8086:2723 (rev 1a)
 Subsystem: 8086:0084
 Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx+
 Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
 Latency: 0, Cache Line Size: 64 bytes
 Interrupt: pin A routed to IRQ 16
 Region 0: Memory at f0700000 (64-bit, non-prefetchable) [size=16K]
 Capabilities: [c8] Power Management version 3
  Flags: PMEClk- DSI+ D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
  Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
 Capabilities: [d0] MSI: Enable- Count=1/1 Maskable- 64bit+
  Address: 0000000000000000 Data: 0000
 Capabilities: [40] Express (v2) Endpoint, MSI 00
  DevCap: MaxPayload 128 bytes, PhantFunc 0, Latency L0s <512ns, L1 unlimited
   ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset+ SlotPowerLimit 0.000W
  DevCtl: CorrErr- NonFatalErr- FatalErr- UnsupReq-
   RlxdOrd- ExtTag- PhantFunc- AuxPwr+ NoSnoop+ FLReset-
   MaxPayload 128 bytes, MaxReadReq 128 bytes
  DevSta: CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
  LnkCap: Port #0, Speed 5GT/s, Width x1, ASPM L1, Exit Latency L1 <8us
   ClockPM+ Surprise- LLActRep- BwNot- ASPMOptComp+
  LnkCtl: ASPM Disabled; RCB 64 bytes Disabled- CommClk+
   ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
  LnkSta: Speed 5GT/s (ok), Width x1 (ok)
   TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
  DevCap2: Completion Timeout: Range B, TimeoutDis+, NROPrPrP-, LTR+
    10BitTagComp-, 10BitTagReq-, OBFF Via WAKE#, ExtFmt-, EETLPPrefix-
    EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
    FRS-, TPHComp-, ExtTPHComp-
    AtomicOpsCap: 32bit- 64bit- 128bitCAS-
  DevCtl2: Completion Timeout: 16ms to 55ms, TimeoutDis-, LTR+, OBFF Via WAKE#
    AtomicOpsCtl: ReqEn-
  LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
    Transmit Margin: Normal Operating Range, EnterModifiedCompliance- ComplianceSOS-
    Compliance De-emphasis: -6dB
  LnkSta2: Current De-emphasis Level: -3.5dB, EqualizationComplete-, EqualizationPhase1-
    EqualizationPhase2-, EqualizationPhase3-, LinkEqualizationRequest-
 Capabilities: [80] MSI-X: Enable+ Count=16 Masked-
  Vector table: BAR=0 offset=00002000
  PBA: BAR=0 offset=00003000
 Capabilities: [100 v1] Advanced Error Reporting
  UESta: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UEMsk: DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- MalfTLP- ECRC- UnsupReq- ACSViol-
  UESvrt: DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ MalfTLP+ ECRC- UnsupReq- ACSViol-
  CESta: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr-
  CEMsk: RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
  AERCap: First Error Pointer: 00, ECRCGenCap- ECRCGenEn- ECRCChkCap- ECRCChkEn-
   MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
  HeaderLog: 00000000 00000000 00000000 00000000
 Capabilities: [14c v1] Latency Tolerance R...

Read more...

Revision history for this message
In , s.penhouet (s.penhouet-linux-kernel-bugs) wrote :
Download full text (5.1 KiB)

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
[ ...

Read more...

Revision history for this message
In , s.penhouet (s.penhouet-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , gabemarcano (gabemarcano-linux-kernel-bugs) wrote :
Download full text (4.4 KiB)

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.
[...

Read more...

Revision history for this message
In , flowhellow (flowhellow-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , ravenexp (ravenexp-linux-kernel-bugs) wrote :

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?

Revision history for this message
In , ravenexp (ravenexp-linux-kernel-bugs) wrote :

Created attachment 290711
Firmware crash log

Revision history for this message
In , pepsov (pepsov-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , MdAyq1 (mdayq1-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , stephanhoerold (stephanhoerold-linux-kernel-bugs) wrote :

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

Revision history for this message
In , stephanhoerold (stephanhoerold-linux-kernel-bugs) wrote :

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/

Revision history for this message
In , micro.modder (micro.modder-linux-kernel-bugs) wrote :

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

Revision history for this message
In , kernel (kernel-linux-kernel-bugs) wrote :

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

Revision history for this message
In , johannes (johannes-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , greearb (greearb-linux-kernel-bugs) wrote :

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

Revision history for this message
Eric Ackermann (worldofjarcraft) wrote :
Download full text (6.4 KiB)

I have the same problem with a M.2 AX200 card installed in a laptop running Ubuntu 20.04, with kernel 5.11.0-40-generic.
I noticed that the WiFi works fine when I force the driver to load the firmware "iwlwifi-cc-a0-48.ucode" by renaming newer versions of this file, and this also worked with previous kernel releases.
After every update of linux-firmware, however, the renamed files are replaced and the WiFi starts crash-looping again.
Thus, I am confident that the issue is specific to the newer firmware releases for the AX200:
- iwlwifi-cc-a0-55.ucode
- iwlwifi-cc-a0-59.ucode
- iwlwifi-cc-a0-63.ucode
Does anyone know what was changed in these firmware revisions?

For reference, here is the error message printed when iwlwifi-cc-a0-55.ucode is loaded. It repeats over and over until I delete the aforementioned firmware file:
[ 215.397707] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-59.ucode failed with error -2
[ 215.397747] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-58.ucode failed with error -2
[ 215.397779] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-57.ucode failed with error -2
[ 215.397810] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-cc-a0-56.ucode failed with error -2
[ 215.398396] iwlwifi 0000:03:00.0: api flags index 2 larger than supported by driver
[ 215.398423] iwlwifi 0000:03:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.22
[ 215.398430] iwlwifi 0000:03:00.0: Found debug destination: EXTERNAL_DRAM
[ 215.398434] iwlwifi 0000:03:00.0: Found debug configuration: 0
[ 215.399009] iwlwifi 0000:03:00.0: loaded firmware version 55.d9698065.0 cc-a0-55.ucode op_mode iwlmvm
[ 215.399106] iwlwifi 0000:03:00.0: Detected Intel(R) Wi-Fi 6 AX200 160MHz, REV=0x340
[ 216.087870] iwlwifi 0000:03:00.0: base HW address: b0:7d:64:dc:49:f2
[ 216.101508] thermal thermal_zone2: failed to read out thermal zone (-61)
[ 218.817520] iwlwifi 0000:03:00.0: Error sending BT_CONFIG: time out after 2000ms.
[ 218.817533] iwlwifi 0000:03:00.0: Current CMD queue read_ptr 5 write_ptr 6
[ 218.817755] iwlwifi 0000:03:00.0: HCMD_ACTIVE already clear for command BT_CONFIG
[ 218.817920] iwlwifi 0000:03:00.0: Start IWL Error Log Dump:
[ 218.817924] iwlwifi 0000:03:00.0: Status: 0x00000040, count: 6
[ 218.817928] iwlwifi 0000:03:00.0: Loaded firmware version: 55.d9698065.0 cc-a0-55.ucode
[ 218.817932] iwlwifi 0000:03:00.0: 0x00000084 | NMI_INTERRUPT_UNKNOWN
[ 218.817936] iwlwifi 0000:03:00.0: 0x00A022F0 | trm_hw_status0
[ 218.817939] iwlwifi 0000:03:00.0: 0x00000000 | trm_hw_status1
[ 218.817942] iwlwifi 0000:03:00.0: 0x004FA34A | branchlink2
[ 218.817945] iwlwifi 0000:03:00.0: 0x004E4BBC | interruptlink1
[ 218.817948] iwlwifi 0000:03:00.0: 0x004E4BBC | interruptlink2
[ 218.817950] iwlwifi 0000:03:00.0: 0x00016468 | data1
[ 218.817953] iwlwifi 0000:03:00.0: 0x01000000 | data2
[ 218.817956] iwlwifi 0000:03:00.0: 0x00000000 | data3
[ 218.817958] iwlwifi 0000:03:00.0: 0x00000000 | beacon time
[ 218.817961] iwlwifi 0000:03:00.0: 0x00289204 | tsf low
[ 218.817963] iwlwifi 0000:03:00.0: 0x00000000 | tsf hi
[ 218.817966] iwlwifi 0000:03:00.0: 0x00000000 | time gp1
[ 218.817968] iw...

Read more...

Revision history for this message
In , lists (lists-linux-kernel-bugs) wrote :
Download full text (5.5 KiB)

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...

Read more...

Revision history for this message
In , helios.solaris (helios.solaris-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , invalidhandle (invalidhandle-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , invalidhandle (invalidhandle-linux-kernel-bugs) wrote :

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.

Revision history for this message
In , MdAyq1 (mdayq1-linux-kernel-bugs) wrote :

(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 .

Revision history for this message
In , matthias (matthias-linux-kernel-bugs) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.