From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934977AbXGXKgd (ORCPT ); Tue, 24 Jul 2007 06:36:33 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1756476AbXGXKgZ (ORCPT ); Tue, 24 Jul 2007 06:36:25 -0400 Received: from posthamster.phnxsoft.com ([195.227.45.4]:2160 "EHLO posthamster.phnxsoft.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753840AbXGXKgZ (ORCPT ); Tue, 24 Jul 2007 06:36:25 -0400 Message-ID: <46A5D619.5030600@imap.cc> Date: Tue, 24 Jul 2007 12:36:09 +0200 From: Tilman Schmidt User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; de-AT; rv:1.8.1.4) Gecko/20070509 SeaMonkey/1.1.2 Mnenhy/0.7.5.666 MIME-Version: 1.0 To: Olaf Hering CC: Jeremy Fitzhardinge , LKML , nix.or.die@googlemail.com, andi@firstfloor.org Subject: Re: 2.6.22-git17 boot failure References: <46A3EC92.3050504@imap.cc> <46A3FBB7.9000608@imap.cc> <46A46BF9.6010906@goop.org> <46A481FD.2030607@imap.cc> <46A4C081.6070305@goop.org> <46A504A3.3070205@imap.cc> <46A51079.5030006@goop.org> <46A53396.2060902@imap.cc> <46A5444D.4080304@goop.org> <20070724091018.GA26724@one.firstfloor.org> <20070724095614.GB625@suse.de> In-Reply-To: <20070724095614.GB625@suse.de> X-Enigmail-Version: 0.95.1 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="------------enig1C31030E5B5D0B91419EACBE" Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org This is an OpenPGP/MIME signed message (RFC 2440 and 3156) --------------enig1C31030E5B5D0B91419EACBE Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Olaf Hering schrieb: > On Tue, Jul 24, Andi Kleen wrote: >=20 >> > Andi, any thoughts about how to debug the suse boot sequence? >=20 > The SuSE boot sequence is rather long. Which part (and which version) a= re 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=3Dy 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=3Dn everything works fine. Netconsole logs with initcall_debug=3D1 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/m= kinitrd > 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=3Dtrace' 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=3D. Thanks, Tilman --=20 Tilman Schmidt E-Mail: tilman@imap.cc Bonn, Germany Diese Nachricht besteht zu 100% aus wiederverwerteten Bits. Unge=C3=B6ffnet mindestens haltbar bis: (siehe R=C3=BCckseite) --------------enig1C31030E5B5D0B91419EACBE Content-Type: application/pgp-signature; name="signature.asc" Content-Description: OpenPGP digital signature Content-Disposition: attachment; filename="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.4 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGpdYZMdB4Whm86/kRAizLAJ4ye0gQqdA8z2gIYH/AvMR0tfjvagCfU8BD sxp8LAaGoEC5fHc7US8AhLw= =/LnZ -----END PGP SIGNATURE----- --------------enig1C31030E5B5D0B91419EACBE--