From: Tilman Schmidt <tilman@imap.cc>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
andi@firstfloor.org, nix.or.die@googlemail.com,
Roland McGrath <roland@redhat.com>
Subject: Re: 2.6.22-git17 boot failure
Date: Tue, 24 Jul 2007 01:02:46 +0200 [thread overview]
Message-ID: <46A53396.2060902@imap.cc> (raw)
In-Reply-To: <46A51079.5030006@goop.org>
[-- Attachment #1: Type: text/plain, Size: 1633 bytes --]
Am 23.07.2007 22:32 schrieb Jeremy Fitzhardinge:
> How much of this is modules? Is the initrd probing for scsi/sata?
> Maybe the the vdso change is having an effect.
Pretty much all of it is modules. The base system is openSUSE 10.2, and
SuSE has a long habit of building everything as modules and putting the
drivers needed for accessing the root filesystem into an initrd. I have
fought it for a while but nowadays I'm playing along.
So yes, all of ahci, pata_marvell, aic7xxx, jbd, dm_mod, ext3 are in
fact modules in initrd. Would it help to try a kernel with some or all
of these built in?
> Ooh, wait. Do you have an old version of the Xen patches in place,
> perhaps?
In which place? I installed and successfully ran the Xen packages that
came with openSUSE 10.2, so there is a 2.6.18 kernel with SuSE's Xen
patches on the machine. But that shouldn't have any influence on the
kernel.org kernels I build myself, should it?
> Does drivers/block/Makefile have:
>
> obj-$(CONFIG_XEN_BLKDEV_FRONTEND) += xen-blkfront.o
>
> (vs := xen-blkfront.o)
It has the "+=" variant.
> Could you do a before and after booting with initcall_debug=1?
"Before" and "after" meaning with CONFIG_XEN=n and CONFIG_XEN=y, I
suppose. The resulting logs are a bit biggish, so I have put them on
http://www.phnxsoft.com/~ts/linux/ for download. Let me know if you
prefer having them mailed.
HTH
T.
--
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: 253 bytes --]
next prev parent reply other threads:[~2007-07-23 23:03 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 [this message]
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
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=46A53396.2060902@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=roland@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.