On 2013-02-01 09:37 (GMT+0100) Josef Reidinger composed:

...

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?

noplymouth on cmdline? splash=0 or splash=verbose on cmdline?

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

I did a fresh snapshot install a few days ago, updated to current 12.3 3 days ago, and I have no problem with 3 on cmdline doing as expected, though I have no bootsplash or plymouth obfuscating the boot process.

Problem was when I play with resolution for my kvm guess and have wrong X11.conf.

Wrong exactly what? What does Xorg.0.log report?

What is annoying is that systemd in this case doesn't provide common CMD line or at least at the end help in console how you must start it to get into command line.

I don't understand this question, but my ttys all work as expected except for https://bugzilla.novell.com/show_bug.cgi?id=768788 -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 2013-02-01 11:08 (GMT+0100) Josef Reidinger composed:

when xdm start failed I expect to get boot on tty, but it doesn't happen and show last lines but without any login.

Are you sure you are not seeing https://bugzilla.novell.com/show_bug.cgi?id=725913 here? If you wait long enough after switch to tty[2-6], do you see login prompt there? -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Sat, 2 Feb 2013 07:35:53 +0100 (CET) Jan Engelhardt пишет:

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)

This refers to /etc/init.d/boot.d support, not for using "3" on kernel command line to enter multi-user.target. static const char * const rlmap[] = { "emergency", SPECIAL_EMERGENCY_TARGET, "-b", SPECIAL_EMERGENCY_TARGET, "single", SPECIAL_RESCUE_TARGET, "-s", SPECIAL_RESCUE_TARGET, "s", SPECIAL_RESCUE_TARGET, "S", SPECIAL_RESCUE_TARGET, "1", SPECIAL_RESCUE_TARGET, "2", SPECIAL_RUNLEVEL2_TARGET, "3", SPECIAL_RUNLEVEL3_TARGET, "4", SPECIAL_RUNLEVEL4_TARGET, "5", SPECIAL_RUNLEVEL5_TARGET, }; -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Sat, 02 Feb 2013 09:13:16 -0500 Ken Schneider - openSUSE пишет:

On 02/02/2013 01:35 AM, Jan Engelhardt pecked at the keyboard and wrote:

...

On Friday 2013-02-01 09:37, Josef Reidinger wrote:

...

On Fri, 1 Feb 2013 09:18:04 +0100 Josef Reidinger wrote:

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)

systemctl isolate runlevel3.target is so much easier then init 3 isn't it.

What makes you believe init 3 does not work?

If I want to run fedora I will download fedora!

-- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Sat, 2 Feb 2013 14:49:51 -0500 Patrick Shanahan пишет:

* Andrey Borzenkov [02-02-13 14:37]:

...

В Sat, 02 Feb 2013 09:13:16 -0500 Ken Schneider - openSUSE пишет:

...

On 02/02/2013 01:35 AM, Jan Engelhardt pecked at the keyboard and wrote:

...

On Friday 2013-02-01 09:37, Josef Reidinger wrote:

...

On Fri, 1 Feb 2013 09:18:04 +0100 Josef Reidinger wrote:

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)

systemctl isolate runlevel3.target is so much easier then init 3 isn't it.

What makes you believe init 3 does not work?

boot to runlevel 3 and do init 5 and you cannot return/open any of the tty's.

And how is it relevant to this (sub-)thread?

boot to runlevel 5 and you have access to the tty's, unless you do init 3 and then either the system hangs or you cannot return to runlevel 5.

that's *screwed* up *royally*!

If you have bug to report, report a bug. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

В Sat, 2 Feb 2013 16:34:51 -0500 Patrick Shanahan пишет:

* Andrey Borzenkov [02-02-13 15:36]:

...

В Sat, 2 Feb 2013 14:49:51 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [02-02-13 14:37]:

...

В Sat, 02 Feb 2013 09:13:16 -0500 Ken Schneider - openSUSE пишет:

...

On 02/02/2013 01:35 AM, Jan Engelhardt pecked at the keyboard and wrote:

...

On Friday 2013-02-01 09:37, Josef Reidinger wrote:

> On Fri, 1 Feb 2013 09:18:04 +0100 > Josef Reidinger wrote: > 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)

systemctl isolate runlevel3.target is so much easier then init 3 isn't it.

What makes you believe init 3 does not work?

boot to runlevel 3 and do init 5 and you cannot return/open any of the tty's.

And how is it relevant to this (sub-)thread?

*You* asked "What makes you believe init 3 does not work?"

Do not take it out of context. My reply was to the statement that now one must use "systemctl isolate runlevel3.target" instead of "init 3"

from graphical mode, runlevel 5, issue "init 3" and system drops graphical mode but dose snot enter text mode, hangs.

Did you try to press Alt-F1?

...

...

boot to runlevel 5 and you have access to the tty's, unless you do init 3 and then either the system hangs or you cannot return to runlevel 5.

that's *screwed* up *royally*!

If you have bug to report, report a bug.

Bug# 801865

I, and I have noticed others, *usually* offer discussion before committing a bug report.

You already posted your problem in another thread. Piggybacking on random statement taken out of context in different discussion is not productive. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Andrey Borzenkov [02-02-13 15:36]:

В Sat, 2 Feb 2013 14:49:51 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [02-02-13 14:37]:

...

В Sat, 02 Feb 2013 09:13:16 -0500

There is really *no* need to cc: me or the list. I read the list and expect to receive responses on the list. You are just duplicating mail traffic w/o cause. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

On 02/06/2013 11:24 AM, Jan Engelhardt pecked at the keyboard and wrote:

On Saturday 2013-02-02 22:52, Patrick Shanahan wrote:

...

* Andrey Borzenkov [02-02-13 15:36]:

...

В Sat, 2 Feb 2013 14:49:51 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [02-02-13 14:37]:

...

В Sat, 02 Feb 2013 09:13:16 -0500

There is really *no* need to cc: me or the list. I read the list and expect to receive responses on the list. You are just duplicating mail traffic w/o cause.

Omg timeline.

http://en.opensuse.org/openSUSE:Mailing_lists_subscription#Generic_FAQ

<opinion> Jan, you are just being a lazy ass</opinion> -- Ken Schneider SuSe since Version 5.2, June 1998 -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Jan Engelhardt [02-06-13 11:26]:

On Saturday 2013-02-02 22:52, Patrick Shanahan wrote:

...

* Andrey Borzenkov [02-02-13 15:36]:

...

В Sat, 2 Feb 2013 14:49:51 -0500 Patrick Shanahan пишет:

...

* Andrey Borzenkov [02-02-13 14:37]:

...

В Sat, 02 Feb 2013 09:13:16 -0500

There is really *no* need to cc: me or the list. I read the list and expect to receive responses on the list. You are just duplicating mail traffic w/o cause.

Omg timeline.

http://en.opensuse.org/openSUSE:Mailing_lists_subscription#Generic_FAQ

Someone has taken *much* liberty with *normal* and expected email list behavior here. List mail *should* remain on list and replies be to the list, unless *specifically* requested otherwise. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Felix Miata [02-06-13 14:34]:

On 2013-02-06 14:27 (GMT-0500) Patrick Shanahan composed:

...

List mail *should* remain on list and replies be to the list, unless *specifically* requested otherwise.

Which reply-to munging facilitates and not munging frustrates for the causal email user.

wonder what would be said were I to set "Reply-To:jengelh@inai.de", which anyone *can* do. -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://linuxcounter.net -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

El 02/02/13 11:13, Ken Schneider - openSUSE escribió:

On 02/02/2013 01:35 AM, Jan Engelhardt pecked at the keyboard and wrote:

...

On Friday 2013-02-01 09:37, Josef Reidinger wrote:

...

On Fri, 1 Feb 2013 09:18:04 +0100 Josef Reidinger wrote:

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)

Yeah, but we dont have systemd 196... for some reason it was decided to stick with old versions..

systemctl isolate runlevel3.target is so much easier then init 3 isn't it.

If I want to run fedora I will download fedora!

it is multi-user,target and init 3 / init 5 should work too. -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org