You are not logged in.
I tried booting with "nomodeset" in the kernel parameter line - no luck.
The startup behavior is always a bit random. Some times I get the soft lockup bug already before partition decryption password prompt, some times after partitions have been decrypted, sometimes the system gets stuck before graphical output with varying error messages. It seems to depend on what process fails due to the CPU getting stuck.
I do seem to get better chances for a successful boot with the 5.15 LTS kernel, though. I haven't been able to successfully boot the current 5.16 kernel yet.
Offline
https://bbs.archlinux.org/viewtopic.php?id=273295
Can you reliably boot the 5.15 lts kernel when appending "debug" or delay the boot process?
Offline
Thank you for your continued support. I am not always able to test your suggestions immediately, so also thanks for patience.
After having applied the latest updates, I tried your suggestions today. With "debug" I can mostly boot into the current LTS kernel, even though I still get "Soft Lockup" messages most of the times. I made about 5 to 7 boot runs, of which only one failed. One time I didn't seem to get Soft Lockup messages.
With applying boot_delay=100 I ran out of patience for the boot process after about 5 mins. I can try that again though, if desired.
The current kernel did not boot up at all (tried 2 times, both with debug parameter).
I noticed that just before the GRUB menu there is an error that lvm2.mod cannot be found. Lvm2 is installed though.
error: file '/grub/x86_64-efi/lvm2.mod' not found.
But I think that's probably not related. Lvm2 has been reinstalled after chrooting and mkinitcpio.conf lists lvm2 in HOOKS: "...block encrypt lvm2 filesystems..."
Last edited by halogene (2022-02-07 14:21:55)
Offline
https://bbs.archlinux.org/viewtopic.php … 8#p2018268 has a patched 5.16 kernel that you could try to boot.
(It's mostly about whether you hit the same bug)
Offline
Thank you seth for your continued support. I apologize I have not tried to boot a custom kernel because I don't feel overly confident with these kind of experiments. However, I discovered that with the most current kernel the system is now booting without problems. Maybe that patch has already made it into the kernel? If @beryllium could try that too and confirm, that would be great. Then we could mark this thread as [solved].
(Using 5.16.10-arch1-1 atm)
Last edited by halogene (2022-02-22 13:06:29)
Offline
I can verify, it works now.
Offline