Arch Linux

Green Lemonade

Member

Registered: 2022-06-11

Posts: 2

[SOLVED] systemd failed to Load Kernel Modules after Hardware change

Hi,

a few days ago, I changed my processor (i3 4170 => i5 12600k), mainboard (now H670M chipset by ASROCK) as well as RAM. Since then systemd is not able to start systemd-modules-load.service.
The dual-booted Windows is still working, as well as my Arch installation medium.

I previously thought that my old cpu might have corrupted something with the multiple crashes, so I did a clean Arch installation after formatting the disk. The problem is still persisting on the new Arch installation.

sistemd status systemd-modules-load gives when used right after the boot process:

× systemd-modules-load.service - Load Kernel Modules
     Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
     Active: failed (Result: signal) since Sat 2022-06-11 06:59:25 CEST; 3min 41s ago
       Docs: man:systemd-modules-load.service(8)
             man:modules-load.d(5)
    Process: 365 ExecStart=/usr/lib/systemd/systemd-modules-load (code=killed, signal=SEGV)
   Main PID: 365 (code=killed, signal=SEGV)
        CPU: 720ms

Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'crypto_user'
Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'sg'
Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'ipmi_devintf'
Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'dm_multipath'
Jun 11 06:59:25 Lemonade systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=11/SEGV
Jun 11 06:59:25 Lemonade systemd[1]: systemd-modules-load.service: Failed with result 'signal'.
Jun 11 06:59:25 Lemonade systemd[1]: Failed to start Load Kernel Modules.
Notice: journal has been rotated since unit was started, output may be incomplete.

systemd status systemd-modules-load gives when used after restarting the module manually:

× systemd-modules-load.service - Load Kernel Modules
     Loaded: loaded (/usr/lib/systemd/system/systemd-modules-load.service; static)
     Active: failed (Result: timeout) since Sat 2022-06-11 06:27:03 CEST; 25min ago
       Docs: man:systemd-modules-load.service(8)
             man:modules-load.d(5)
    Process: 796 ExecStart=/usr/lib/systemd/systemd-modules-load (code=killed, signal=TERM)
   Main PID: 796 (code=killed, signal=TERM)
        CPU: 606ms

Jun 11 06:25:33 Lemonade systemd[1]: Starting Load Kernel Modules...
Jun 11 06:27:03 Lemonade systemd[1]: systemd-modules-load.service: start operation timed out. Terminating.
Jun 11 06:27:03 Lemonade systemd[1]: systemd-modules-load.service: Main process exited, code=killed, status=15/TERM
Jun 11 06:27:03 Lemonade systemd[1]: systemd-modules-load.service: Failed with result 'timeout'.
Jun 11 06:27:03 Lemonade systemd[1]: Failed to start Load Kernel Modules.

journalctl -xeu systemd-modules-load gives the same output as systemctl status:

Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'crypto_user'
Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'sg'
Jun 11 06:59:24 Lemonade systemd-modules-load[365]: Inserted module 'ipmi_devintf'
...
Jun 11 06:59:25 Lemonade systemd[1]: Failed to start Load Kernel Modules.

My installed linux package version matches uname -r and the version of the installed linux-header package: 5.18.2-arch1-1. My linux-api-headers package is version 5.17.5-2 but according to pacman this is the newest version. Uninstalling it would break the dependencies of glibc and libbpf.

Thanks in advance!

PS: I'm sorry for the formatting, this is my first post here and I have not yet found out about single-line code-blocks.

Last edited by Green Lemonade (2022-06-11 08:53:54)

Green Lemonade

Member

Registered: 2022-06-11

Posts: 2

Re: [SOLVED] systemd failed to Load Kernel Modules after Hardware change

So after a bit of reading i found out that the nvidia-uvm module didn't load.

That is because "Due to FS#74886/FS#74891, nvidia doesn't boot on Linux 5.18 on systems with Intel CPUs." as the Arch wiki says. Switching to linux lts solved the problem.