On Friday 2013-02-01 09:37, Josef Reidinger wrote:
On Fri, 1 Feb 2013 09:18:04 +0100 Josef Reidinger
wrote: Hi, Yesterday I upgrade my virtual machine via zypper dup to current opensuse snapshot. After dup system works fine. Problem happen when I reboot. Then system stuck during boot. Few notable things I see * plymouth boot failed with see systemctl ... * xdm start succeed but nothing shown * I get no console where I can login ( even if systemd start all services except failed plymouth), how can I login to obtain some logs or see what and why failed?
after 11 minutes multiple lines of segfault in mandb start occuring with lines mandb[<pid>]: segfault at 7fffd708c000 ip 00007fc543de5a6b sp 00007fffd7089fe8 error 4 in libc-2.17.so[7fc543d5e000+1a3000]
If I boot with 3 to just console with X it stuck same way ( just no xdm of course ). In this case mandb do not print segfaults.
Any ideas how can I proceed at least to console login and to start debugging it?
Thanks Josef
After more digging I found that old '3' at the end of line doesn't help and need to use systemd specific options - http://fedoraproject.org/wiki/Systemd#Boot_Kernel_Command_Line
Quote from a systemd-devel posting that made it to my inbox just a bit later: """ As of 3cdebc217c42c8529086f2965319b6a48eaaeabe support for distro specific boot up runlevels has been dropped. """ (3cde... = systemd-196) -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org