From: Tilman Schmidt <tilman@imap.cc>
To: Olaf Hering <olh@suse.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
LKML <linux-kernel@vger.kernel.org>,
nix.or.die@googlemail.com, andi@firstfloor.org
Subject: Re: 2.6.22-git17 boot failure
Date: Tue, 24 Jul 2007 12:36:09 +0200 [thread overview]
Message-ID: <46A5D619.5030600@imap.cc> (raw)
In-Reply-To: <20070724095614.GB625@suse.de>
[-- Attachment #1: Type: text/plain, Size: 1596 bytes --]
Olaf Hering schrieb:
> 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?
Quick summary of the problem:
Opensuse 10.2 32-bit install on a Pentium D 940
Kernel 2.6.22-git17 or later (last reproduced with 2.6.23-rc1)
A kernel built with CONFIG_XEN=y fails to detect the SATA disks during
boot, so the root filesystem cannot be mounted and I'm thrown into
the emergency /bin/sh. With CONFIG_XEN=n everything works fine.
Netconsole logs with initcall_debug=1 of a successful and a
failing startup and corresponding .config-s are available at
http://www.phnxsoft.com/~ts/linux/
> As Andi said, putting a 'set -x' into /init script generated by /sbin/mkinitrd
> is one thing.
I'll try. I guess I'll have to unpack/repack the finished initrd
image (gzipped cpio archive, AFAICS) for that - or is there a way
to have mkinitrd inject that statement for me?
> You can also boot with 'linuxrc=trace' to generate a huge
> amount of udev and /init debug.
That looks simple enough, so I'll try that first, although it looks
to me like the trouble happens before udev comes into play.
> Booting with 'confirm' will allow you to step each runlevel script, see
> /etc/init.d/boot, look for DO_CONFIRM=.
Thanks,
Tilman
--
Tilman Schmidt E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 250 bytes --]
next prev parent reply other threads:[~2007-07-24 10:36 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-22 23:47 2.6.22-git17 boot failure Tilman Schmidt
2007-07-23 0:31 ` Gabriel C
2007-07-23 0:52 ` Tilman Schmidt
2007-07-23 8:51 ` Jeremy Fitzhardinge
2007-07-23 10:25 ` Tilman Schmidt
2007-07-23 14:51 ` Jeremy Fitzhardinge
2007-07-23 19:42 ` Tilman Schmidt
2007-07-23 20:32 ` Jeremy Fitzhardinge
2007-07-23 23:02 ` Tilman Schmidt
2007-07-24 0:14 ` Jeremy Fitzhardinge
2007-07-24 8:51 ` Tilman Schmidt
2007-07-24 8:59 ` Jeremy Fitzhardinge
2007-07-24 9:10 ` Andi Kleen
2007-07-24 9:56 ` Olaf Hering
2007-07-24 10:36 ` Tilman Schmidt [this message]
2007-07-24 13:45 ` Olaf Hering
2007-07-24 15:45 ` Jeremy Fitzhardinge
2007-07-24 15:47 ` Andi Kleen
2007-07-24 18:08 ` Tilman Schmidt
2007-07-24 19:02 ` Jeremy Fitzhardinge
2007-07-24 19:12 ` Andi Kleen
2007-07-24 19:15 ` Jeremy Fitzhardinge
2007-07-24 20:48 ` Tilman Schmidt
2007-07-24 21:20 ` Jeremy Fitzhardinge
2007-07-24 3:46 ` Jeremy Fitzhardinge
2007-07-23 9:25 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2007-07-23 0:27 Sid Boyce
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=46A5D619.5030600@imap.cc \
--to=tilman@imap.cc \
--cc=andi@firstfloor.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--cc=olh@suse.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox