Intel AX201 [8086:a0f0] subsys [8086:4070] iwlwifi microcode crash after updating to 5.14.0-1027-oem

[Kai-Chuan Hsieh]

Mar 09 10:33:40 MDAT-DVT2-D8 kernel: FAT-fs (sda1): unable to read boot sector to mark fs as dirty
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: Loaded firmware version: 63.c04f3485.0 QuZ-a0-hr-b0-63.ucode
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: 0x00000FAD | ADVANCED_SYSASSERT
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: 0x0000A210 | trm_hw_status0
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: 0x004CAD42 | branchlink2
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: 0x004C17C6 | interruptlink1
Mar 09 11:04:25 MDAT-DVT2-D8 kernel: iwlwifi 0000:00:14.3: 0x004C17C6 | interruptlink2
...

ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.14.0-1027-oem 5.14.0-1027.30
ProcVersionSignature: Ubuntu 5.14.0-1027.30-oem 5.14.21
Uname: Linux 5.14.0-1027-oem x86_64
ApportVersion: 2.20.11-0ubuntu27.21
Architecture: amd64
CasperMD5CheckResult: skip
CurrentDesktop: ubuntu:GNOME
Date: Wed Mar 9 11:13:53 2022
InstallationDate: Installed on 2021-10-19 (140 days ago)
InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819)
SourcePackage: linux-signed-oem-5.14
UpgradeStatus: No upgrade log present (probably fresh install)

[Kai-Chuan Hsieh (kchsieh)]

Upload sos report.

[Launchpad Janitor (janitor)]

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

[Colin Brown (colinwilliambrown)]

Problem occurs on my LG gram laptop with Intel AX2-1, running Kubuntu 21.10. Disconnects/reconnects occurred sporadically for a week or two recently but now it fails to reconnect, even on reboot. Log shows the same error messages reported above.

[Kai-Chuan Hsieh (kchsieh)]

@colinwilliambrow

hello,

Could you help to upload your kernel log to check if you see the same issue as mine?

Thanks,