linux-kernel - Re: 2.6.22-git17 boot failure

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20070724095614.GB625@suse.de>
Date:	Tue, 24 Jul 2007 11:56:14 +0200
From:	Olaf Hering <olh@...e.de>
To:	Jeremy Fitzhardinge <jeremy@...p.org>
Cc:	Tilman Schmidt <tilman@...p.cc>,
	LKML <linux-kernel@...r.kernel.org>, nix.or.die@...glemail.com,
	andi@...stfloor.org
Subject: Re: 2.6.22-git17 boot failure

On Tue, Jul 24, Andi Kleen wrote:

> > Andi, any thoughts about how to debug the suse boot sequence?

The SuSE boot sequence is rather long. Which part (and which version) are we talking about?

As Andi said, putting a 'set -x' into /init script generated by /sbin/mkinitrd
is one thing. You can also boot with 'linuxrc=trace' to generate a huge
amount of udev and /init debug.

Booting with 'confirm' will allow you to step each runlevel script, see
/etc/init.d/boot, look for DO_CONFIRM=.

My Email provider kicked me off of lkml, so I dont have the rest of this
thread at hand.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/