You are not logged in.
Hi,
Systemd keeps failing with: Failed to set invocation ID for unit: File exists error. Sometimes the OS doesn't even boot.
logs:
Jan 08 21:47:40 archlinux systemd[1]: dev-ttyS27.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: sys-devices-platform-serial8250-tty-ttyS27.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: dev-ttyS29.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: sys-devices-platform-serial8250-tty-ttyS29.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: dev-ttyS28.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: sys-devices-platform-serial8250-tty-ttyS28.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: dev-ttyS3.device: Failed to set invocation ID for unit: File exists
Jan 08 21:47:40 archlinux systemd[1]: dev-ttyS31.device: Failed to set invocation ID for unit: File exists
Jan 08 21:49:03 office01 systemd[1]: sys-kernel-tracing.mount: Failed to set invocation ID for unit: File exists
Jan 08 21:49:03 office01 systemd[1]: Failed to mount Kernel Trace File System.
based on some google search results, it seems it's related to a bug with AMD rdrand. However, I'm not sure about that.
System Info
CPU: AMD Ryzen 9 5900X
Microcode update image (amd-ucode) version: 20201218.646f159-1
Motherboard: X570 i Aorus Pro Wifi
BIOS/Firmware Version: F31b (10/28/2020)
Arch Kernel Version: 5.10.5-arch1-1
Systemd Version: 247.2-1
Thanks
Last edited by asahaf (2021-01-08 19:55:53)
Offline
Adding SYSTEMD_RDRAND=0 to the kernel cmdline solves the issue for me
Thanks to
Lennart Poettering @poettering on GitHub
https://github.com/systemd/systemd/issu … -758089410
Offline
That's disturbing. Hopefully you will find a BIOS update to fix it.
CPU-optimized Linux-ck packages @ Repo-ck • AUR packages • Zsh and other configs
Offline
The problem was actually fixed with motherboard BIOS update.
Offline