Intel BE200 Microcode SW error detected

[BlastChaser]

Hi,

My network wifi card (Intel BE200) seems to crash every 5~10 minutes, resulting in frequent disconnections and very annoying user experience. I am trying to figure out what is going on, and I keep seeing "Microcode SW error detected" followed by a core dump from the iwlwifi module. Any help is appreciated! See attached logs.

I am running the latest microcode provided by the Arch repositories:

Feb 18 22:23:32 wirerider kernel: iwlwifi 0000:2e:00.0: loaded firmware version 94.62990553.0 gl-c0-fm-c0-94.ucode op_mode iwlmvm

Here is the coredump:

Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00001B4C | rcm log PC
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00803FF0 | rcm frame pointer
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00803F5C | rcm stack pointer
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | rcm msg ID
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x20000000 | rcm ISR status
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00020400 | frame HW status
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | LMAC-to-RCM request mbox
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | RCM-to-LMAC request mbox
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | MAC header control
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | MAC header addr1 low
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x003C0000 | MAC header info
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | MAC header error
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: IML/ROM dump:
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000B03 | IML/ROM error/state
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00010046 | IML/ROM data1
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: Fseq Registers:
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x67A00000 | FSEQ_ERROR_CODE
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x80B10005 | FSEQ_TOP_INIT_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00570000 | FSEQ_CNVIO_INIT_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x0000AA14 | FSEQ_OTP_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x0000000F | FSEQ_TOP_CONTENT_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x4552414E | FSEQ_ALIVE_TOKEN
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x02001910 | FSEQ_CNVI_ID
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x02001910 | FSEQ_CNVR_ID
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x02001910 | CNVI_AUX_MISC_CHIP
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x02001910 | CNVR_AUX_MISC_CHIP
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00001BE7 | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00000000 | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00570000 | FSEQ_PREV_CNVIO_INIT_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00B10005 | FSEQ_WIFI_FSEQ_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x00B10005 | FSEQ_BT_FSEQ_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x000000DC | FSEQ_CLASS_TP_VERSION
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: UMAC CURRENT PC: 0x80289dae
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: LMAC1 CURRENT PC: 0xd0
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: LMAC2 CURRENT PC: 0xd0
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: UMAC CURRENT PC 1: 0x80289dac
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: TCM1 CURRENT PC: 0xd0
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: RCM1 CURRENT PC: 0xd0
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: RCM2 CURRENT PC: 0xd0
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: Function Scratch status:
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: 0x01010100 | Func Scratch
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
Feb 18 23:17:08 work-pc kernel: ieee80211 phy0: Hardware restart was requested
Feb 18 23:17:08 work-pc kernel: iwlwifi 0000:2e:00.0: FW error in SYNC CMD PHY_CONTEXT_CMD
Feb 18 23:17:08 work-pc kernel: CPU: 2 UID: 0 PID: 2447 Comm: iwd Not tainted 6.13.2-arch1-1 #1 0973c91260d936c90a829134c4296c40fdd8c0c0

The attached log file includes more before/after logs to provide context about what may have triggered the crash.

About my system:

Distro: Arch Linux

Kernel: Linux 6.13.2

Laptop model: Nitrokey Nitropad v54 (Intel BE200 wifi)

[DhannielM_Intel]

Hello BlastChaser,

Thank you for reaching out to the community. Before I proceed with investigating your concern, could you please confirm if your laptop's BIOS is up to date?

Best regards,

Dhanniel M.

Intel Customer Support Technician

[BlastChaser]

Hi Dhanniel, yes, my BIOS is at the latest version available for my device.

Thanks

[DhannielM_Intel]

Hello BlastChaser, 

Thanks for sharing this to me, I will conduct a thorough internal investigation regarding this concern. Once I have gathered my findings, I will share them with you.

Best regards,

Dhanniel M.

Intel Customer Support Technician

[DhannielM_Intel]

Hello BlastChaser, 

Thank you for your patience. I have a few follow-up questions regarding the Microcode Software error you mentioned. Please provide answers to the following:

1. Could you let me know when the issue first started? Was the wireless connection functioning properly before this issue occurred?
2. Have you attempted to connect to a different access point to see if the issue persists?
3. Please try installing the latest stable version of the Linux Kernel from kernel.org. After installation, let me know the results.
4. Have you reached out to Nitrokey for further assistance regarding this issue?

Best regards,

Dhanniel M.

Intel Customer Support Technician

[BlastChaser]

Hi, sorry for the delayed reply. I did try your suggestions.

1) The error started sometime in the last month. I did not pay attention to say exactly when.

2) Yes with mixed results. I tried two access points at my home, both exhibited the problem. Then, a few days ago (after I started this post), I tried a third router in a different building and the problem no longer occurs.

3) I've installed latest via Arch repositories, this did not fix the issue. I also tried on LTS kernel as well. No change with these kernels.

4) Yes. They are unaware of any issues and unable to provide much assistance.

Thanks

[DhannielM_Intel]

Hello BlastChaser, 

I'm reaching out to see if you've had a chance to review my follow-up questions regarding this issue. Your responses will greatly assist me in analyzing the situation more effectively. Please let me know your answers at your earliest convenience.

Best regards,

Dhanniel M.

Intel Customer Support Technician

[DhannielM_Intel]

Hello BlastChaser, 

Thank you for getting back to me. Your response to question number 2 is quite interesting. Before we delve into that, could you let me know if the issue persisted after following my suggestion?

Moving forward, could you please provide the exact model of the two access points you have at home? Additionally, include the model of the one you used in a different building. From what I can tell, the issue might be related to your home router rather than the access points. 

Best regards,

Dhanniel M.

Intel Customer Support Technician

[BlastChaser]

No, the issue persisted across multiple access points.

Unfortunately I don't have the model numbers, because it was not my home and I am no longer staying there

Perhaps its not useful to keep debugging this issue. I will reply back if the issue returns.

Thanks for your time!

[DhannielM_Intel]

Hello BlastChaser, 

Thank you for the update. Could you please let me know if it's alright to close this inquiry for now? I appreciate your confirmation. Thank you.

Best regards,

Dhanniel M.

Intel Customer Support Technician

[BlastChaser]

yes. please close it

[DhannielM_Intel]

Hello BlastChaser, 

Thank you for confirming this, and please do contact your Access Point OEM for further assistance. I will now close this inquiry. If you need further assistance, please feel free to submit a new question, as this thread will no longer be monitored.

Best regards,

Dhanniel M.

Intel Customer Support Technician