1968205 – iwlwifi: "Microcode SW error detected. Restarting 0x0" on Intel(R) Wi-Fi 6 AX210 (used as an AP)

Bug 1968205 - iwlwifi: "Microcode SW error detected. Restarting 0x0" on Intel(R) Wi-Fi 6 AX210 (used as an AP)

Summary: iwlwifi: "Microcode SW error detected. Restarting 0x0" on Intel(R) Wi-Fi 6 AX...

Keywords:
Status:	CLOSED EOL
Alias:	None
Product:	Fedora
Classification:	Fedora
Component:	kernel
Sub Component:
Version:	34
Hardware:	Unspecified
OS:	Unspecified
Priority:	unspecified
Severity:	unspecified
Target Milestone:	---
Assignee:	Kernel Maintainer List
QA Contact:	Fedora Extras Quality Assurance
Docs Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+	depends on / blocked

Reported:	2021-06-06 19:43 UTC by Vadim Trochinsky
Modified:	2022-06-07 22:37 UTC (History)
CC List:	18 users (show)
Fixed In Version:
Clone Of:
Environment:
Last Closed:	2022-06-07 22:37:23 UTC
Type:	Bug
Embargoed:
Dependent Products:

Attachments	(Terms of Use)
Kernel dmesg log (113.86 KB, text/plain) 2021-06-06 19:43 UTC, Vadim Trochinsky	no flags	Details
View All

Description Vadim Trochinsky 2021-06-06 19:43:41 UTC

Created attachment 1789153 [details]
Kernel dmesg log

1. Please describe the problem:

Shortly after booting, the kernel produces a microcode error on the wifi card, which keep happening once in a while.

The card is being used to create an access point.

The driver initializes:

Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: enabling device (0140 -> 0142)
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: api flags index 2 larger than supported by driver
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.59.2.22
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: loaded firmware version 62.49eeb572.0 ty-a0-gf-a0-62.ucode op_mode iwlmvm
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: loaded PNVM version 0x324cd670
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0: base HW address: 70:cf:49:bc:68:6c
Jun 06 16:51:31 kernel: iwlwifi 0000:04:00.0 wifi: renamed from wlan0
Jun 06 16:51:37 kernel: iwlwifi 0000:04:00.0: Failed to create debugfs directory under (efault)


And crashes begin soon after:

Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Microcode SW error detected. Restarting 0x0.
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Status: 0x00000040, count: 6
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Loaded firmware version: 62.49eeb572.0 ty-a0-gf-a0-62.ucode
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000071 | NMI_INTERRUPT_UMAC_FATAL    
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00A08200 | trm_hw_status0
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | trm_hw_status1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x004DA02C | branchlink2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x004D070E | interruptlink1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x004D070E | interruptlink2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00016364 | data1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000010 | data2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | data3
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | beacon time
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x0234C097 | tsf low
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | tsf hi
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | time gp1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x023600DA | time gp2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000001 | uCode revision type
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x0000003E | uCode version major
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x49EEB572 | uCode version minor
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000420 | hw version
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00C89002 | board version
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x80E6FF00 | hcmd
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x24020000 | isr0
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x01000000 | isr1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x59F00002 | isr2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00C37FCC | isr3
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00200000 | isr4
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x1301001C | last cmd Id
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00016364 | wait_event
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x000000D0 | l2p_control
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00018034 | l2p_duration
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x0000003F | l2p_mhvalid
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00CB00E9 | l2p_addr_match
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000009 | lmpm_pmg_sel
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | timestamp
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x0000B83C | flow_handler
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Start IWL Error Log Dump:
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Status: 0x00000040, count: 7
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x200020A3 | ADVANCED_SYSASSERT
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | umac branchlink1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x8045C7E4 | umac branchlink2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0xC00845FC | umac interruptlink1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | umac interruptlink2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000014 | umac data1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000004 | umac data2
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000006 | umac data3
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x0000003E | umac major
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x49EEB572 | umac minor
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x023600D2 | frame pointer
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0xC0885E58 | stack pointer
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x009C011D | last host cmd
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000000 | isr status reg
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: IML/ROM dump:
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000B03 | IML/ROM error/state
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00008110 | IML/ROM data1
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: Fseq Registers:
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x60000000 | FSEQ_ERROR_CODE
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x80440002 | FSEQ_TOP_INIT_VERSION
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00070008 | FSEQ_CNVIO_INIT_VERSION
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x0000A652 | FSEQ_OTP_VERSION
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000002 | FSEQ_TOP_CONTENT_VERSION
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00400410 | FSEQ_CNVI_ID
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00400410 | FSEQ_CNVR_ID
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00400410 | CNVI_AUX_MISC_CHIP
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00400410 | CNVR_AUX_MISC_CHIP
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00009061 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: 0x00000061 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Jun 06 16:52:14 kernel: iwlwifi 0000:04:00.0: WRT: Collecting data: ini trigger 4 fired.


Despite crashing, so far wifi seems to be still working, 

2. What is the Version-Release number of the kernel:

5.12.8-300.fc34.x86_64


3. Did it work previously in Fedora? If so, what kernel version did the issue
   *first* appear?  Old kernels are available for download at
   https://koji.fedoraproject.org/koji/packageinfo?packageID=8 :

This started happening since the installation of the new hardware, a PCIe "Buttwo But-AX210P" adapter.

4. Can you reproduce this issue? If so, please provide the steps to reproduce
   the issue below:

It keeps happening on its own, so far counting 5 occurrences in about 5 hours, one happening shortly after boot.


5. Does this problem occur with the latest Rawhide kernel? To install the
   Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by
   ``sudo dnf update --enablerepo=rawhide kernel``:


Untested yet, but since it says "microcode", probably a different firmware would be more likely to fix something here.


6. Are you running any modules that not shipped with directly Fedora's kernel?:

no


7. Please attach the kernel logs. You can get the complete kernel log
   for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the
   issue occurred on a previous boot, use the journalctl ``-b`` flag.

Comment 1 Ben Cotton 2022-05-12 15:45:55 UTC

This message is a reminder that Fedora Linux 34 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 34 on 2022-06-07.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '34'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 34 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

Comment 2 Ben Cotton 2022-06-07 22:37:23 UTC

Fedora Linux 34 entered end-of-life (EOL) status on 2022-06-07.

Fedora Linux 34 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.