FS#76383 - System reboots after entering LUKS password first time

Attached to Project: Arch Linux
Opened by gudvinr (gudvinr) - Wednesday, 02 November 2022, 10:14 GMT
Last edited by Toolybird (Toolybird) - Tuesday, 22 November 2022, 20:12 GMT
Task Type Bug Report
Category System
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

I use LUKS to encrypt whole disk.
My only unencrypted partition is /boot/efi that has UKI files and systemd-boot bootloader

When I boot system after power off, I see plymouth greeting with password prompt and when I enter password, system doesn't boot further and just reboots.
After it boots again, I enter password again and boot process continues normally.

It started to happen around 2022-10-27.

I do not feel comfortable attaching boot logs publicly but I can send them to relevant person by e-mail.
If there's a need to post specific configuration files, package versions, etc, I have no issue with that but I don't know what information would be relevant in this case.
This task depends upon

Closed by  Toolybird (Toolybird)
Tuesday, 22 November 2022, 20:12 GMT
Reason for closing:  None
Additional comments about closing:  Reporter says "It just stopped happening after updating something. However, it is still a mystery what was causing this."
Comment by Toolybird (Toolybird) - Thursday, 03 November 2022, 02:15 GMT
There's not enough info here. A kernel issue seems likely. Can you try an older kernel?

There is no "relevant person by e-mail" option. Arch is a volunteer org which means you have to be prepared to help yourself. Unless info is forthcoming which demonstrates an Arch packaging issue, I'm afraid there is nothing we can do. You are best advised to visit the proper support channels (forum/IRC/etc) to see if someone can assist in debugging the problem.
Comment by gudvinr (gudvinr) - Thursday, 03 November 2022, 08:51 GMT
Sure. I just don't know where to start investigation to gather relevant information so I'll start with the kernel, than you.
Comment by gudvinr (gudvinr) - Saturday, 05 November 2022, 13:44 GMT
I tried kernel 5.15.76-1-lts and it is the same here too.
I am pretty sure it did work okay back then, when 5.15 was still fresh because I didn't have this behaviour until late october.

Loading...