AX210 Soft Software Reset Under Heavy HCI Traffic (Linux)

[asrathanlal]

We are using the Intel AX210 on a Linux-based device, with our application communicating with the controller via HCI.

Under heavy HCI traffic, we intermittently observe a soft software reset of the AX210. After this reset, HCI communication with the device stops and does not recover without reinitialization.

When the issue occurs, we receive a soft software reset indication with the following payload:

HCI Event: Vendor (0xff) plen 7
    Intel Bootup (0x02)
    Zero: 0x00
    Number of packets: 2
    Source: Operational firmware (0x01)
    Reset type: Soft software reset (0x02)
    Reset reason: System exception (0x05)
    DDC status: Persistent RAM (0x02)
> HCI Event: Vendor (0xff) plen 79
    Vendor Prefix (0x8780)
    Intel Extended Telemetry (0x03)
    Extended event type (0x01): System Exception (0x00)
    Unknown extended subevent 0x07
    01 01 00 07 01 07 06 1c 00 00 00 00 60 ba 14 00
    1e 08 09 80 00 02 07 00 60 ba 14 00 01 00 00 00
    11 00 00 00 05 14 00 00 00 00 4a ba 14 00 76 29
    14 00 b6 0a 16 00 f2 f9 13 00 43 10 1a f2 13 00
    00 08 12 00 59 20 57 02 42 20 43 20
> HCI Event: Hardware Error (0x10) plen 1
    Code: 0x0c
< HCI Command: LE Create Connection Cancel (0x08|0x000e) plen 0
> HCI Event: Command Complete (0x0e) plen 4
    LE Create Connection Cancel (0x08|0x000e) ncmd 1
    Status: Command Disallowed (0x0c)

We would like to understand:

• The possible root cause of this soft software reset under high HCI load
• How to decode and interpret the reset payload, and what information it provides about the failure condition

At this stage, we are not looking for firmware upgrades. Our goal is to understand the reset behavior and payload to improve stability and handling on the host side.

dmesg | grep iwlwifi
[ 7.811233] iwlwifi 0000:01:00.0: enabling device (0000 -> 0002)
[ 7.931148] iwlwifi 0000:01:00.0: api flags index 2 larger than supported by driver
[ 7.940538] iwlwifi 0000:01:00.0: TLV_FW_FSEQ_VERSION: FSEQ Version: 0.0.2.36
[ 7.950810] iwlwifi 0000:01:00.0: loaded firmware version 72.a764baac.0 ty-a0-gf-a0-72.ucode op_mode iwlmvm
[ 8.024427] iwlwifi 0000:01:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz, REV=0x420
[ 8.220738] iwlwifi 0000:01:00.0: loaded PNVM version 674867bd
[ 8.241964] iwlwifi 0000:01:00.0: Detected RF GF, rfid=0x10d000

[JedG_Intel]

Hello asrathanlal,

Thank you for posting on Intel Community Forum.

Please share the information below for me to address your questions.

1. What is the Linux Kernel?

2. Is this the original adapter that came pre-installed in your system, or have you changed/installed a new adapter recently?

3. Is this a laptop or desktop system?

I look forward to your response.

Best regards

Jed G.

Intel Customer Support Technician

[JedG_Intel]

Hello asrathanlal,

I wanted to check if you had the chance to review the questions I posted. Please let me know at your earliest convenience so that we can determine the best course of action to resolve this matter.

Best regards,

Jed G.

Intel Customer Support Technician

[JedG_Intel]

Hello asrathanlal,

I’m reaching out to share some additional information that may help with further troubleshooting.

To proceed, please install the latest stable Kernel version 6.18, along with the most recent firmware files iwlwifi‑ty‑a0‑gf‑a0‑891 and iwlwifi‑ty‑a0‑gf‑a0.pnvm, which are available from the Firmware git tree. These updates may help address the behavior you’re experiencing.

As I have not received a response from you, I will be closing this inquiry for now. If you require further assistance or have additional questions, please feel free to submit a new request, as this thread will no longer be monitored.

Best regards

Jed G.

Intel Customer Support Technician

[asrathanlal]

Hi Jed,

I was tracking this ticket and didn’t see any updates, so I thought it might have been marked as spam. Because of that, I recreated the ticket and I’m interacting on the new one now. This ticket can be closed.

Thanks for the information. At the moment, updating the kernel or firmware is not an option. What I need right now is help decoding the message and understanding what is causing it.

Regards

Ashok