Am Mittwoch, 26. Oktober 2011 schrieb Guido Berhoerster:

* Guido Berhoerster [2011-10-25 10:47]:

...

when booting the RC1 installer on my netbook it just hangs after "Starting udev...". There's no kernel panic and it works fine on another notebook and desktop machine so it looks like it's hardware-specific. How do I debug this?

Booting the RC1 GNOME live media works fine, what is the difference in boot process and is there a way to get more verbose output from udev?

Try booting with linuxrc.debug=-udev.mods and/or try all consoles Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

Am Mittwoch, 26. Oktober 2011 schrieb Guido Berhoerster:

* Stephan Kulow [2011-10-26 13:47]:

...

Am Mittwoch, 26. Oktober 2011 schrieb Guido Berhoerster:

...

* Guido Berhoerster [2011-10-25 10:47]:

...

when booting the RC1 installer on my netbook it just hangs after "Starting udev...". There's no kernel panic and it works fine on another notebook and desktop machine so it looks like it's hardware-specific. How do I debug this?

Booting the RC1 GNOME live media works fine, what is the difference in boot process and is there a way to get more verbose output from udev?

Try booting with linuxrc.debug=-udev.mods and/or try all consoles

That allows it to boot, now how do I find the module at fault? VTs are not yet set up at that stage and there's no further output.

Hmm, changing back to alt-f1 won't give you some more info? Greetings, Stephan -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Steffen Winterfeldt [2011-10-26 15:30]:

On Wed, 26 Oct 2011, Guido Berhoerster wrote:

...

* Stephan Kulow [2011-10-26 13:47]:

...

Am Mittwoch, 26. Oktober 2011 schrieb Guido Berhoerster:

...

* Guido Berhoerster [2011-10-25 10:47]:

...

when booting the RC1 installer on my netbook it just hangs after "Starting udev...". There's no kernel panic and it works fine on another notebook and desktop machine so it looks like it's hardware-specific. How do I debug this?

Booting the RC1 GNOME live media works fine, what is the difference in boot process and is there a way to get more verbose output from udev?

Try booting with linuxrc.debug=-udev.mods and/or try all consoles

That allows it to boot, now how do I find the module at fault? VTs are not yet set up at that stage and there's no further output.

You can boot with 'linuxrc.debug=wait'. This gives you a prompt ('?') at several points. There you can either press 'enter' to go to the next one or 's' to get a shell.

Skip the first prompt and start a shell at the second (the one after some loop mounts). There run 'myudevstart' and see what happens.

There seems to be some kind of race condition here, booting with linuxrc.debug=wait works every single time and I also noticed that regular booting works about 2 out of 10 times. Any ideas on how to investigate this further? This is on a MSI U-100 netbook which should be reasonably common. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org

* Steffen Winterfeldt [2011-10-26 16:49]:

On Wed, 26 Oct 2011, Guido Berhoerster wrote:

...

* Steffen Winterfeldt [2011-10-26 15:30]:

...

On Wed, 26 Oct 2011, Guido Berhoerster wrote:

...

* Stephan Kulow [2011-10-26 13:47]:

...

Am Mittwoch, 26. Oktober 2011 schrieb Guido Berhoerster:

...

* Guido Berhoerster [2011-10-25 10:47]: >when booting the RC1 installer on my netbook it just hangs after >"Starting udev...". There's no kernel panic and it works fine on >another notebook and desktop machine so it looks like it's >hardware-specific. How do I debug this?

Booting the RC1 GNOME live media works fine, what is the difference in boot process and is there a way to get more verbose output from udev?

Try booting with linuxrc.debug=-udev.mods and/or try all consoles

That allows it to boot, now how do I find the module at fault? VTs are not yet set up at that stage and there's no further output.

You can boot with 'linuxrc.debug=wait'. This gives you a prompt ('?') at several points. There you can either press 'enter' to go to the next one or 's' to get a shell.

Skip the first prompt and start a shell at the second (the one after some loop mounts). There run 'myudevstart' and see what happens.

There seems to be some kind of race condition here, booting with linuxrc.debug=wait works every single time and I also noticed that regular booting works about 2 out of 10 times. Any ideas on how to investigate this further? This is on a MSI U-100 netbook which should be reasonably common.

If you can switch to console 4, you could look at the last kernel messages and guess on the last loaded module, then exclude it with brokenmodules=foo.

Last message was from i915/drm, disabling i915 makes it boot every single time. Somehow I'm not very suprised by this... I've filed bnc#726781. -- Guido Berhoerster -- To unsubscribe, e-mail: opensuse-factory+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-factory+owner@opensuse.org