Intermittant issues with Intel Wi-Fi 6 AX201 adatper in Ubuntu 24.04

Support and Help
, ,
1

Ubuntu Version:
LTS Ubuntu 24.04.3 LTS

Desktop Environment (if applicable):
GNOME

Problem Description:
Hello, I’ve been having issues where my built in Intel Wi-Fi 6 AX201Wireless Adapter starts having very bad issues and it will drop the connection. This has been happening on and off since at least May of 2025. It will also make my mouse and system hang bad.

Per this entry:
Dec 07 15:38:58 yoga9i kernel: workqueue: iwl_fw_error_dump_wk [iwlwifi] hogged CPU for >10000us 8 times, consider switching to WQ_UNBOUND

Relevant System Information:
sudo lshw -class network
*-network
description: Wireless interface
product: Wi-Fi 6 AX201
vendor: Intel Corporation
physical id: 14.3
bus info: pci@0000:00:14.3
logical name: wlp0s20f3
version: 20
serial: XX
width: 64 bits
clock: 33MHz
capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
configuration: broadcast=yes driver=iwlwifi driverversion=6.8.0-88-generic firmware=77.b405f9d4.0 QuZ-a0-hr-b0-77.u ip=XXXX latency=0 link=yes multicast=yes wireless=IEEE 802.11
resources: iomemory:600-5ff irq:16 memory:607d1dc000-607d1dffff

lspci -k |grep AX
00:14.3 Network controller: Intel Corporation Wi-Fi 6 AX201 (rev 20)
Subsystem: Intel Corporation Wi-Fi 6 AX201

And here’s my current Kernel but this has been happening on multiple Kernels.

uname -a
Linux yoga9i 6.8.0-88-generic #89-Ubuntu SMP PREEMPT_DYNAMIC Sat Oct 11 01:02:46 UTC 2025 x86_64 x86_64 x86_64 GNU/Linux

Screenshots or Error Messages:
This is the output in dmesg when this problem occurs. Also, all the text red. Here’s all the text that will scroll in dmesg.

[Tue May 27 18:31:00 2025] ieee80211 phy0: Hardware restart was requested
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Queue 1 is stuck 0 15
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: **Microcode SW error detected.** Restarting 0x0.
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 6
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Loaded firmware version: 77.ad46c98b.0 QuZ-a0-hr-b0-77.ucode
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000084 | NMI_INTERRUPT_UNKNOWN       
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0000A2F0 | trm_hw_status0
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x004C938E | branchlink2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x004BF29A | interruptlink1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x004BF29A | interruptlink2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x000152DA | data1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x01000000 | data2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | data3
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x18409E8A | beacon time
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x83566B78 | tsf low
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000007 | tsf hi
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | time gp1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x009C4119 | time gp2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0000004D | uCode version major
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0xAD46C98B | uCode version minor
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000351 | hw version
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00C89001 | board version
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x8002FC18 | hcmd
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x20028000 | isr0
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x01000000 | isr1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x08F00002 | isr2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00C30808 | isr3
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | isr4
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00310103 | last cmd Id
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x000152DA | wait_event
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | l2p_duration
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x000000CE | l2p_addr_match
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | timestamp
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x000080C4 | flow_handler
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Transport status: 0x0000004A, valid: 7
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x20000066 | NMI_INTERRUPT_HOST
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x804561E2 | umac branchlink2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x8047348E | umac interruptlink1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x8047348E | umac interruptlink2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x01000000 | umac data1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x8047348E | umac data2
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | umac data3
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0000004D | umac major
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0xAD46C98B | umac minor
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x009C4117 | frame pointer
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0xC0886260 | stack pointer
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0048019C | last host cmd
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: IML/ROM dump:
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00005959 | IML/ROM data1
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: Fseq Registers:
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x20000302 | FSEQ_CNVI_ID
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00090006 | FSEQ_PREV_CNVIO_INIT_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00290033 | FSEQ_WIFI_FSEQ_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x00290033 | FSEQ_BT_FSEQ_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: 0x000000DC | FSEQ_CLASS_TP_VERSION
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: UMAC CURRENT PC: 0x80472fa4
[Tue May 27 18:31:16 2025] iwlwifi 0000:00:14.3: LMAC1 CURRENT PC: 0xd0

What I’ve Tried:
List the solutions or workarounds you’ve already attempted. Nothing yet. I usually have to reboot and it usually starts working again. However, today it took multiple reboots to stop the errors.
I was ‘debating’ on running this but not sure yet?
sudo apt-get install intel-microcode

Here’s my current microcode:
sudo dmesg | grep microcode
[ 0.930102] microcode: Current revision: 0x000000bc
[ 0.930103] microcode: Updated early from: 0x000000a6

I also appear to be using the latest firmware based on my searches:

Current Linux firmware
dpkg -l | grep linux-firmware
ii linux-firmware 20240318.git3b128b60-0ubuntu2.21 amd64 Firmware for Linux kernel drivers

I greatly appreciate any ideas or help!

2

FYI: I went ahead and pulled the trigger and ran this. I was pretty nervous since this is a dual boot setup but my GRUB / Dual boot remained intact. Also, my wifi connected right up on boot so that’s good. However, I will have to monitor to see if this reoccurs since it’s TOTALLY RANDOM from what I have observed.

sudo apt install --reinstall linux-firmware
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages were automatically installed and are no longer required:
  libclamav11t64 libgl1-amber-dri libglapi-amber libllvm19
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 2 not upgraded.
Need to get 539 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://us.archive.ubuntu.com/ubuntu noble-updates/main amd64 linux-firmware amd64 20240318.git3b128b60-0ubuntu2.21 [539 MB]
Fetched 539 MB in 21s (25.2 MB/s)                                                                                                                                           
(Reading database ... 270843 files and directories currently installed.)
Preparing to unpack .../linux-firmware_20240318.git3b128b60-0ubuntu2.21_amd64.deb ...
Unpacking linux-firmware (20240318.git3b128b60-0ubuntu2.21) over (20240318.git3b128b60-0ubuntu2.21) ...
Setting up linux-firmware (20240318.git3b128b60-0ubuntu2.21) ...
Processing triggers for initramfs-tools (0.142ubuntu25.5) ...
update-initramfs: Generating /boot/initrd.img-6.8.0-88-generic

If problems persist I will likely try this next.

sudo apt-get install intel-microcode

3

BUMP, so far I wanted to mention running this command appears to have helped with this NASTY issue!
sudo apt install --reinstall linux-firmware

I haven’t bothered running this command >
sudo apt-get install intel-microcode

So, if any encounters similar issues I would recommend doing the same as of now. Peace & Linux. :peace_symbol: :penguin:

4

@vw16v First of all, welcome to Ubuntu Discourse :slight_smile:

Thank you for sharing these troubleshooting steps with the community.

Fingers crossed the issue is resolved.

1 Like
5

Well, unfortunately my Ubuntu system Froze up tonight. It was totally unresponsive. Could not SSH in but could ping it fine. I had this happen a few time before I applied the firmware via this command to fix the original issue I mentioned.
sudo apt install --reinstall linux-firmware

So, the linux-firmware is not suspected of this freeze. What is, is the microcode I mentioned. I’m seeing this in my syslog when the event occurred.

2025-12-08T17:48:08.014200-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
2025-12-08T17:48:08.015522-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
2025-12-08T17:48:23.886248-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
2025-12-08T17:48:23.887555-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
2025-12-08T17:48:40.270238-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
2025-12-08T17:48:40.270748-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
2025-12-08T17:48:56.654277-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
2025-12-08T17:48:56.655542-07:00 yoga9i kernel: iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
2025-12-08T17:48:56.669220-07:00 yoga9i kernel: workqueue: iwl_fw_error_dump_wk [iwlwifi] hogged CPU for >10000us 4 times, consider switching to WQ_UNBOUND

Also, based on what I mentioned in my original post I believe I’m on the latest/current microcode for my Intel wireless adapter.

sudo lshw -C network
[sudo] password for  
  *-network                 
       description: Wireless interface
       product: Wi-Fi 6 AX201
       vendor: Intel Corporation
       physical id: 14.3
       bus info: pci@0000:00:14.3
       logical name: wlp0s20f3
       version: 20
       serial: 
       width: 64 bits
       clock: 33MHz
       capabilities: pm msi pciexpress msix bus_master cap_list ethernet physical wireless
       configuration: broadcast=yes driver=iwlwifi driverversion=6.8.0-90-generic firmware=77.b405f9d4.0 QuZ-a0-hr-b0-77.u ip=10.16.0.63 latency=0 link=yes multicast=yes wireless=IEEE 802.11
       resources: iomemory:600-5ff irq:16 memory:607d1dc000-607d1dffff
       
       sudo dmesg | grep microcode
[    0.930102] microcode: Current revision: 0x000000bc
[    0.930103] microcode: Updated early from: 0x000000a6

However, I’m going to go ahead and run the microcode command now and see if I get any updates on my microcode and or driver/firmware. However, I believe I’m on the latest firmware.
Loaded firmware version: 77.ad46c98b.0 QuZ-a0-hr-b0-77.ucode

Running these commands and hoping for the best!

sudo apt update
sudo apt install intel-microcode

Fingers crossed! :hand_with_index_finger_and_thumb_crossed:

6

Well, nothing changed after running that. Say’s I’m already on the latest microcode.
So… Not sure what caused these random freezes. Might need a different thread for this one but appears wifi related…???

Here’s the latest microcode: (which matches mine: 3.20250812.0ubuntu0.24.04.1)
intel microcode

sudo apt install intel-microcode
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
intel-microcode is already the newest version (3.20250812.0ubuntu0.24.04.1).
intel-microcode set to manually installed.
The following packages were automatically installed and are no longer required:
  linux-headers-6.8.0-87 linux-headers-6.8.0-87-generic linux-image-6.8.0-87-generic
  linux-modules-6.8.0-87-generic linux-modules-extra-6.8.0-87-generic linux-tools-6.8.0-87
  linux-tools-6.8.0-87-generic
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 29 not upgraded.


sudo apt autoremove
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
The following packages will be REMOVED:
  linux-headers-6.8.0-87 linux-headers-6.8.0-87-generic linux-image-6.8.0-87-generic linux-modules-6.8.0-87-generic
  linux-modules-extra-6.8.0-87-generic linux-tools-6.8.0-87 linux-tools-6.8.0-87-generic
0 upgraded, 0 newly installed, 7 to remove and 29 not upgraded.
After this operation, 301 MB disk space will be freed.

Do you want to continue? [Y/n] y
(Reading database ... 308812 files and directories currently installed.)
Removing linux-headers-6.8.0-87-generic (6.8.0-87.88) ...
Removing linux-headers-6.8.0-87 (6.8.0-87.88) ...
Removing linux-image-6.8.0-87-generic (6.8.0-87.88) ...
/etc/kernel/postrm.d/initramfs-tools:
update-initramfs: Deleting /boot/initrd.img-6.8.0-87-generic
/etc/kernel/postrm.d/zz-update-grub:
Sourcing file `/etc/default/grub'
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-6.8.0-90-generic
Found initrd image: /boot/initrd.img-6.8.0-90-generic
Found linux image: /boot/vmlinuz-6.8.0-88-generic
Found initrd image: /boot/initrd.img-6.8.0-88-generic
Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
Warning: os-prober will be executed to detect other bootable partitions.
Its output will be used to detect bootable binaries on them and create new boot entries.
Found Windows Boot Manager on /dev/nvme0n1p1@/EFI/Microsoft/Boot/bootmgfw.efi
Adding boot menu entry for UEFI Firmware Settings ...
done
Removing linux-modules-extra-6.8.0-87-generic (6.8.0-87.88) ...
Removing linux-modules-6.8.0-87-generic (6.8.0-87.88) ...
Removing linux-tools-6.8.0-87-generic (6.8.0-87.88) ...
Removing linux-tools-6.8.0-87 (6.8.0-87.88) ...
7

Any chance you have Windows as a dual boot with the hybrid shutdown enabled?

1 Like
8

This is a dual boot setup with Windows 11 and Ubuntu. Are you referring to “Fast Startup” enabled in the BIOS? This problem has been intermittent and doesn’t happen really often. I’m still hoping to isolate the issue. Thanks!

9

The fast startup in BIOS could affect the wifi at times, but see https://www.computerhope.com/issues/ch001762.htm

2 Likes
10

Cool. I’ll check that next time I boot into Windows! I’m pretty sure it’s enabled. I prefer to leave it enabled but might be a good test to disable it if the freezing persist. :penguin:

11

This topic was automatically closed after 30 days. New replies are no longer allowed.