http://bugzilla.novell.com/show_bug.cgi?id=1020283 Christoph Obexer changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |cobexer@gmail.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c2 --- Comment #2 from Robby Engelmann --- Update: -force a re-install of the kernel did not help -adding "plymouth.enable=0" to the kernel boot line in grub --> boot works maybe related: boo#966255 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 Robby Engelmann changed: What |Removed |Added ---------------------------------------------------------------------------- Component|Kernel |Basesystem Assignee|kernel-maintainers@forge.pr |bnc-team-screening@forge.pr |ovo.novell.com |ovo.novell.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c16 --- Comment #16 from Robby Engelmann --- Created attachment 712067 --> http://bugzilla.novell.com/attachment.cgi?id=712067&action=edit journalctl -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c18 Robby Engelmann changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |thiago@kde.org --- Comment #18 from Robby Engelmann --- *** Bug 1022707 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c20 Franck Bui changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |fbui@suse.com --- Comment #20 from Franck Bui --- Could anybody post the result of a failing case with debug log enabled (add "debug printk.devkmsg=on" on the kernel command line before booting) ? If it's not always failing the same logs for the working case might be interesting too. Oh and use the latest versions of all packages. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c21 Ju_Ping Chan changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |email@chanjp.me --- Comment #21 from Ju_Ping Chan --- I have added it to my boot kernel parameter, and am now awaiting for the crash. Where can I retrieve the right log? Presumably, I will be booting into a working desktop first to eventually get the log, and it will be the working log. Is it "journalctl --boot=-1"? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c23 --- Comment #23 from Andrei Borzenkov --- (In reply to Thiago Macieira from comment #22)

(In reply to Franck Bui from comment #20)

...

Could anybody post the result of a failing case with debug log enabled (add "debug printk.devkmsg=on" on the kernel command line before booting) ?

That's impossible for me. Because "failing" means "failing to mount root filesystem", nothing gets saved to /var/log. I can't get the log that it did generate when I ran like that.

If it fails to mount root, add rd.shell kernel parameter, you should be dropped into dracut shell. In which you can mount USB stick and copy dmesg there. You may need to regenerate initrd to include usb-storage and stick filesystem kernel modules and to pass log_buf_len=16M (or larger) to ensure kernel printk buffer is large enough. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c25 --- Comment #25 from Thiago Macieira --- (In reply to Thiago Macieira from comment #24)

(In reply to Andrei Borzenkov from comment #23)

...

If it fails to mount root, add rd.shell kernel parameter, you should be dropped into dracut shell. In which you can mount USB stick and copy dmesg there. You may need to regenerate initrd to include usb-storage and stick filesystem kernel modules and to pass log_buf_len=16M (or larger) to ensure kernel printk buffer is large enough.

Thanks, I will try. I don't think I will need USB storage, as I can save to /boot which is ext4.

It will take a few days. Hopefully by Friday.

BTW, don't get your hopes up. I don't think I'll get anything useful. Possible scenarios: * with rd.shell, it not ask for the password, in which case the problem will not have (yet) happened and there will be nothing useful to be logged and inspected * with rd.shell, it will ask for the password like "single" does, where the problem is bypassed * the problem will happen and, like right now, leave the keyboard inoperative and therefore I won't be able to even run dmesg (when it happens, CapsLock doesn't turn the LED on; I have to do Alt+SysRq,B to reboot) Are you sure that rd.shell will drop me to a shell *after* it tries to mount the root filesystem? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 Martin Wilck changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |martin.wilck@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c29 --- Comment #29 from Robby Engelmann --- On my machine the issue seems to be, that the system is not switching to the right VT. I would say in 30-40% of the boots I do only see a blinking cursor on a black screen. When I switch to VT7 via CTRL+ALT+F7, I have the graphical password prompt back. I assume I had a similar problem prior to the systemd-update: on some boots I only got the textmode password prompt. Thus, it seems to me (at least in my case) the problem was there before, but now, the textmode password prompt is not shown anymore. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c38 --- Comment #38 from Thiago Macieira --- After the upgrade to 4.9.8: I am still dropped to a text mode screen with no password prompt. But this time, Alt+F7 did switch to a VT with plymouth's graphical password prompt. I need a couple more boots to confirm that this is the new normal behaviour. As I previously noted, I had tried this before and it had not worked. And before this problem had happened, the graphical password prompt only appeared once every couple of boots. Most of the time, I used to get a full-screen text mode password prompt (that is not the one you get when you boot in "single"). So it's possible that the text mode password prompt is still failing, but I was lucky on this boot that the graphical one was available. I have another laptop that hasn't been updated since this problem began (4.9.0 kernel) and I can perform debugging in it, if necessary. It does have the problem of the password prompt being full-screen text instead of graphical, which is why I can confidently say that the text-mode password problem has been affecting OpenSUSE for at least 3 years. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c44 --- Comment #44 from Robby Engelmann --- The bug is still valid within snapshot 20170622! -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c46 --- Comment #46 from Robby Engelmann --- How is the runlevel related to the plymouth password prompt and the obvious faulty switch to the correct tty? I do not get the link? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.novell.com/show_bug.cgi?id=1020283 http://bugzilla.novell.com/show_bug.cgi?id=1020283#c48 --- Comment #48 from Takashi Iwai --- The question is why it's on VT-7. It's a VT where usually X runs. The VT switch happens by the display manager service as well even without plymouth. The fact that it happens by kernel update might be merely a coincidence, if it's about a race among VT switches. -- You are receiving this mail because: You are on the CC list for the bug.