Kernel Panic

Shibboleth · 2026-08-01 12:03:45

I encountered a Kernel Panic while restoring from suspend. This was accompanied by graphical errors on the secondary monitor. Panic report here: https://pastebin.com/raw/DvGMXFFD.

My initial suspicion was the GPU due to the display errors I saw on resume, but I see the nvme0n1p1 errors too. What could I use to dig into what exactly went wrong here?

seth · 2026-08-01 13:59:57

https://wiki.archlinux.org/title/Solid_ … leshooting
"nvme_core.default_ps_max_latency_us=0 pcie_aspm=off iommu=soft"

Also post the output of "lspci -tvnn", the upper part of the kernel dump is your wifi, then the nvme shows up - whatever the cause probably bleeds into the bus and then affects random other stuff, too.

mmy8x · 2026-08-01 14:37:45

[218188.113728] coredump: 1(systemd): |/usr/lib/systemd/systemd-coredump pipe failed
[218188.113739] Kernel panic - not syncing: Attempted to kill init! exitcode=0x0000000b

systemd strikes again?

edit:
Actually, you have a bunch of I/O errors and random processes crashing before that.

[218188.038204] Restarting tasks: Starting
[218188.038691] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #27788011: lblock 0: comm systemd-journal: error -5 reading directory block
[218188.038697] coredump: 794(tokio-rt-worker): |/usr/lib/systemd/systemd-coredump pipe failed
[218188.038710] systemd-journald[392]: Failed to rotate /var/log/journal/fe35c5a5896844419d2fd863482d0d5e/system.journal: Input/output error
[218188.038743] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #27788011: lblock 0: comm systemd-journal: error -5 reading directory block
[218188.038760] systemd-journald[392]: Failed to write entry to /var/log/journal/fe35c5a5896844419d2fd863482d0d5e/system.journal (11 items, 308 bytes) despite vacuuming, ignoring: Bad message
[218188.038784] systemd-journald[392]: Unknown SIGBUS page, aborting.
[218188.038813] coredump: 392(systemd-journal): |/usr/lib/systemd/systemd-coredump pipe failed
[218188.038843] coredump: 879(wpa_supplicant): |/usr/lib/systemd/systemd-coredump pipe failed
[218188.039192] Restarting tasks: Done
[218188.039234] random: crng reseeded on system resumption
[218188.039245] PM: suspend exit
[218188.039299] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #12059548: lblock 0: comm dhcpcd: error -5 reading directory block
[218188.039354] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #2621441: lblock 0: comm systemd-timesyn: error -5 reading directory block
[218188.039440] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #2621441: lblock 0: comm sd-resolve: error -5 reading directory block
[218188.039470] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #2621441: lblock 0: comm sd-resolve: error -5 reading directory block
[218188.040051] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #12059548: lblock 0: comm dhcpcd: error -5 reading directory block
[218188.055312] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #2621441: lblock 0: comm systemd-udevd: error -5 reading directory block
[218188.055334] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #2621441: lblock 0: comm systemd-udevd: error -5 reading directory block
[218188.055367] EXT4-fs warning (device nvme0n1p1): dx_probe:791: inode #2621441: lblock 0: comm systemd-udevd: error -5 reading directory block

Last edited by mmy8x (2026-08-01 14:43:17)

seth · 2026-08-01 14:39:25

While blaming lennart is always an entertaining option, I rather suspect the coredump storage fails because the nvme has bailed.

Shibboleth · 2026-08-01 17:24:17

seth wrote:

While blaming lennart is always an entertaining option

Tempting!

The output of "lspci -tvnn" can be found here: https://pastebin.com/raw/8iAmvRur
Cheers for taking a look

seth · 2026-08-01 18:40:38

Yeah, wifi and nvme sit right next to each other on the same lane, you need to figure which is the cause of this.
Apply the kernel parameters from #2, https://wiki.archlinux.org/title/Kernel_parameters or alternatively disable the wifi (ideally if you can in the UEFI settings)

Sanity check: you're not dual booting (windows)?
Otherwise and ceterum cesenseo, see the 3rd link below. Mandatory.
Disable it (it's NOT the BIOS setting!) and reboot windows and linux twice for voodo reasons.

Arch Linux

#1 2026-08-01 12:03:45

Kernel Panic

#2 2026-08-01 13:59:57

Re: Kernel Panic

#3 2026-08-01 14:37:45

Re: Kernel Panic

#4 2026-08-01 14:39:25

Re: Kernel Panic

#5 2026-08-01 17:24:17

Re: Kernel Panic

#6 2026-08-01 18:40:38

Re: Kernel Panic

Board footer