http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c1 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |mfleming@suse.com, | |rjschwei@suse.com, | |tiwai@suse.com Flags| |needinfo?(rjschwei@suse.com | |) --- Comment #1 from Takashi Iwai <tiwai@suse.com> --- Is this a regression with the recent kernel? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c3 --- Comment #3 from Robert Schweikert <rjschwei@suse.com> --- For completeness, for those that run into the issue here is the step by step work around implementation: 1.) Boot into a rescue system 2.) mount the partition that is usually your root partition (mount /dev/sdaX /mnt) X is a placeholder for a number 3.) mount your boot partition (mount /dev/sdaY /mnt/boot/efi) Y is a placeholder for a number, assuming EFI boot setup 4.) bind mount /proc /sys /dev /run (mount --bind /proc /mnt/proc) 5.) chroot to /mnt (chroot /mnt) 6.) vi /etc/default/grub (add plymouth.enable=0 to the string for GRUB_CMDLINE_LINUX_DEFAULT) 7.) grub2-mkconfig -o /boot/grub2/grub.cfg 8.) exit 9.) shutdown -r now Setting up the chroot is not strictly necessary but it makes dealing with grub2-mkconfig easier and thus makes things less error prone. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c5 Takashi Iwai <tiwai@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(rjschwei@suse.com | |) --- Comment #5 from Takashi Iwai <tiwai@suse.com> --- For confirming that it's a kernel regression: I have the old kernel packages, e.g. 4.3.x in OBS home:tiwai:kernel:4.3 repo. Install this kernel and retest again with plymouth enabled. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c7 --- Comment #7 from Robert Schweikert <rjschwei@suse.com> --- Reported by Paul Gonin on ML: Same issue here with Tumbleweed, updated to 4.4 kernel and LUKS crypted partition (but not root fortunately) Symptoms are similar but not exactly the same. I was able to boot when insisting... but protected partition is not mounted. Looking at systemd journal I could see that plymouth related issues : Feb 12 09:30:25 systemd[1]: plymouth-start.service: Main process exited, code=dumped, status=11/SEGV Feb 12 09:30:25 audit[1]: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=plymouth-start comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? termi Feb 12 09:30:25 systemd[1]: plymouth-start.service: Unit entered failed state. Feb 12 09:30:25 systemd[1]: plymouth-start.service: Failed with result 'core-dump'. I have had issues with plymouth and luks for dome time actually https://bugzilla.opensuse.org/show_bug.cgi?id=948975 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c9 --- Comment #9 from Takashi Iwai <tiwai@suse.com> --- (In reply to Robert Schweikert from comment #8)

Experiencing the same symptom with kernel-default-4.3.3-1.1.gda39cbd.x86_64.rpm

Please don't make me go back in time through more kernel versions.

If you can conclude certainly that this is no kernel regression, I'm happy to hear. If not, it'd be helpful for further tests; there are other kernel versions in my OBS home:tiwai:kernel:$VERSION repos :) (4.1 is found in Leap.) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 PatrickD Garvey <PatrickDGarveyt@gMail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |PatrickDGarveyt@gMail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c12 --- Comment #12 from Ismail Donmez <idonmez@suse.com> --- I setup a new VM to try this bug but sorry 1. I got a graphical dialog asking the disk password 2. systemctl status plymouth-start shows that it exited successfully. I don't get a login windows but looks like X.org crashes with a reference to vboxvideo_drv.so which is a VirtualBox bug it seems. So, if any of you guys can get a coredump with debuginfo it would be the most appreciated. I'll be testing on a laptop as a second resort. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c14 --- Comment #14 from Ismail Donmez <idonmez@suse.com> --- (In reply to Fabian Vogt from comment #13)

I tried to debug it, but the issue is that plymouth works fine if started manualy, even in the initrd. As a better workaround, I added plymouth to the list of modules to omit from the initrd, so that it uses the plymouth on / and not the one inside the initrd and it works fine. I guess it's some kind of timing issue...

Do we really need plymouth in initrd? That really makes it harder to debug it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Robert Kaiser <kairo@kairo.at> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |kairo@kairo.at -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 James Mason <jmason@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |jmason@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c25 --- Comment #25 from Jacob W <jacobwinski@gmail.com> --- Created attachment 667207 --> http://bugzilla.opensuse.org/attachment.cgi?id=667207&action=edit cryptsetup boot password prompt goes into background as a job -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c27 --- Comment #27 from Jacob W <jacobwinski@gmail.com> --- Thank you Fabian for your quick replies. (In reply to Fabian Vogt from comment #26)

(In reply to Jacob W from comment #25)

...

Created attachment 667207 [details] cryptsetup boot password prompt goes into background as a job

That's not the plymouth prompt, so a totally different issue. It didn't even try to use plymouth for password asking.

This is when booting without kernel options "splash=silent" and "quiet". So of course plymouth is not started, because it's not supposed to. The point of this screenshot is to show that even without plymouth, the password prompting is incorrect. If I do have the above kernel options enabled, I do not get a splash screen. All I get is a blank black screen. VT switching does not work. This blank black screen shows up where previously, prior to this bug, I would get the plymouth password prompt.

...

Password prompt is not shown and plymouth theme never shows up, instead it freezes the system where VT switching does not work.

If even the cursor stops blinking, the kernel either froze or panics -> kernel bug.

Logs show no mention of kernel panic. Kernel loads fine from what I can tell. Have not had a kernel panic since I started having this cryptsetup issue. I've check both /var/log/messages and systemd journald.

To confirm, run on a booted system as root on a TTY:

...

rcxdm stop plymouthd --no-daemon --no-boot-log --tty=/dev/tty0 --debug --mode=boot

and on a different tty also as root

...

plymouth show-splash

and you should the the splash screen (on TTY7).

I do not see the splash screen. All I see is the regular output of booting: [ OK ] .... [ OK ] .... No errors, nothing unusual, no interruptions, etc. None of the above commands showed errors from what I could tell.

...

Forcing the system to boot without plymouth (press e on grub's kernel list) shows what looks like cryptsetup trying to prompt for the password, but instead instantly being backgrounded as a job. After more processes go through their boot procedure, the boot process stops and looks frozen. If I press a button on the keyboard, it forces the password prompt to re-appear. Now I can enter my password and everything works from there.

It's not backgrounded, it's the current TTY so systemd uses it, although it's also being used by something else... -> systemd bug(?)

From the above, I am guessing that this is a systemd issue. When using

Exactly! The password prompt should halt all further processes until the correct password is entered, but this is not the case. The password prompt is suppressed and other things just keep loading. I call this backgrounding, because that's exactly how it looks like: the job (it's literally called that) of cryptsetup password prompt is being suppressed. Hitting a button later "reveals" the job (to me, that's like foregrounding it). Maybe that's bad use of terminology. Yes, this looks like a systemd bug. I've been trying to say that from the beginning. Isn't this bug report a systemd issue? I'm confused. Like I mentioned before, I do not think plymouth is to blame, but systemd because even without plymouth, there is an issue with the password prompt (see previously attached screenshot). See also (like you already have) my comments on bug 942940 To recap: 1) without kernel options "splash=silent" and "quiet", it's clear cryptsetup password prompt is not being correctly initiated (see previously attached screenshot). 2) with kernel option "quiet" but NOT "splash=silent" (or with "splash=verbose"), password prompt is correctly shown and halts everything until a correct password is provided. Once provded, everything continues to load. This is how it's supposed to work. 3) with both "splash=silent" and "quiet", the instance plymouth is supposed show the password prompt, what I assume is the graphical system freezes and all I get is a blank black screen. I cannot switch VT. plymouth, it is getting two conflicting "signals": 1) the passowrd prompt is needed and 2) don't show password prompt. This is exactly what happens without kernel options "splash=silent" and "quiet" (see previously attached screenshot): cryptsetup is asked to show password prompt and 2) the password prompt is not shown / hidden (I call this the job being backgrounded). But because there is no plymouth being loaded, the system does not freeze and you wait until other things load, press a button on the keyboard, and the password prompt is then foregrounded. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Antoine Belvire <antoine.belvire@laposte.net> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |antoine.belvire@laposte.net -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Ismail Donmez <idonmez@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC|idonmez@suse.com | -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c31 --- Comment #31 from John Chufar <john.chufar@gmail.com> --- I can confirm the only thing that works for me is the method Jacob W listed. Remove kernel boot parameter "splash=silent" but keep "quiet" I then enter my pw after the point the system starts prompting in the message display during boot. It still spools other output while I am typing sometimes, but works. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 http://bugzilla.opensuse.org/show_bug.cgi?id=966255#c33 Fabian Vogt <fvogt@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Assignee|fvogt@suse.com |qzhao@suse.com Summary|System does not boot |No passphrase requested on | |boot if plymouth is active --- Comment #33 from Fabian Vogt <fvogt@suse.com> --- (In reply to Jacob W from comment #32)

I'm glad that people have found my workaround helpful.

Just like Shashank and John, this bug still affects me after all this time and I still use the workaround I gave 1.5 years ago myself.

It's not easy to debug as it only happens reproducibly on very certain setups. For instance, it no longer shows up on my system where I originally debugged the issue for a while, I'll also removed plymouth from all systems I have access to meanwhile. I recommend everyone to do the same, it's an extremely annoying and unreliable piece of software. There's currently work ongoing to drop plymouth from openSUSE and replace it with a different kernel-based bootsplash that is free from race conditions. Still, I adjusted the title and reassigned it to the plymouth maintainer. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=966255 Michal Suchanek <msuchanek@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |msuchanek@suse.com -- You are receiving this mail because: You are on the CC list for the bug.