(Intel Core Ultra 7 155H, Ubuntu 24.04, Kernel 6.14) Kernel crash related to iwlwifi

Framework Laptop 13 Linux
1

Which Linux distro are you using?
Ubuntu

Which release version?
24.04.3

Which kernel are you using?
6.14.0-29-generic #29~24.04.1-Ubuntu SMP PREEMPT_DYNAMIC

Which BIOS version are you using?
03.05

Which Framework Laptop 13 model are you using?
Intel® Core™ Ultra Series 1

I’ve been experiencing system crashes over the last few days, and I haven’t been able to nail down a culprit. I’ve setup kdump to create dumps when the kernel crashes. The most recent one happened a few minutes ago.

I’ve captured the output of three commands after rebooting:

I’ve been seeing lots of references to iwlwifi and thunderboltin the kernel logs.

The first messages that started the kdump log I saw was:

Sep 01 15:14:06 kernel: DMAR: DRHD: handling fault status reg 3
Sep 01 15:14:06 kernel: DMAR: [DMA Write NO_PASID] Request device [aa:00.0] fault addr 0xffaf2000 [fault reason 0x71] SM: Present bit in first-level paging entry is clear
Sep 01 15:14:06 kernel: iwlwifi 0000:aa:00.0: Detected crf-id 0x400410, cnv-id 0x400410 wfpm id 0x80000000
Sep 01 15:14:06 kernel: iwlwifi 0000:aa:00.0: PCI dev 2725/0024, rev=0x420, rfid=0x10d000
Sep 01 15:14:06 kernel: iwlwifi 0000:aa:00.0: Detected Intel(R) Wi-Fi 6 AX210 160MHz
Sep 01 15:14:06 kernel: iwlwifi 0000:aa:00.0: [0] Got MSI-X interrupt before we have Rx queues
Sep 01 15:14:06 kernel: iwlwifi 0000:aa:00.0: [1] Got MSI-X interrupt before we have Rx queues
Sep 01 15:14:06 kernel: iwlwifi 0000:aa:00.0: Microcode SW error detected. Restarting 0x0.

I’m at my wits end with this issue. I don’t know how to reproduce it reliably.

What should I be doing to troubleshoot this?

2

The crash log output only shows three WARNING: CPU … which are not kernel panics (a panic is a kernel crash - these warnings may be leading up to a panic tho). See if your logs shows a kernel panic. They may not if your kernel is indeed crashing before it even has a chance log the reason for the panic.

The first warning is related to the display (i915 0000:00:02.0: [drm]) so that might be the place to start looking. Another fw13 intel core ultra user reported “freezes” on Ubuntu 24.04.3 (kernel 6.14.0-27) that went away upon changing to fedora 42. This makes me suspect the display server (X for ubuntu 24.04.3 vs wayland for fedora 42).

If your system “freezes” again see if you can do ctl-alt-f3 and get to a console or, if you have sshd set up, see if you can log into your framework from another device. If either of these work, then your kernel has not crashed. From the console (or remote ssh session), you should be able to get a better idea of what is going wrong.

FWIW, I’m using kubuntu 24.03 and kernel 6.14.0-29 (using X as a display server) on a fw 13 core ultra 125H with bios 3.05 and so far I have not experienced these issues.

HTH

1 Like
3

Thank you for the response!

Wayland is the default on Ubuntu 24.04 and that’s what I’ve been using: Mutter with GNOME 46.

Right now, I’ve switched back to the original kernel 24.04 comes with (6.8.0-79-generic) to see if that improves system stability. The next time I encounter a freeze, I’ll check for tty3 like you suggested to try and narrow down the real fault.

Will update if this happens again.

1 Like
4

@Noelle_Leigh See if there are any directories in /var/lib/systemd/pstore/. Directories there may contain dmesg.txt files with some debugging info from prior crashes (look for kernel panics).

If you do find something, likely you will have to start by checking if anything similar in your dmesg files has already been reported to ubuntu. If what you find has not been reported to ubuntu, then try reporting to them first.

The symptoms and logs you describe above may get a little attention as they are; however my experience is that there will be little follow up. If you find a kernel panic in your dmesg logs, then reporting that is more likely to be noticed (if it has not already been reported).