From: Tilman Schmidt <tilman@imap.cc>
To: Olaf Hering <olh@suse.de>
Cc: Jeremy Fitzhardinge <jeremy@goop.org>,
LKML <linux-kernel@vger.kernel.org>,
Gabriel C <nix.or.die@googlemail.com>,
Andi Kleen <andi@firstfloor.org>
Subject: Re: 2.6.22-git17 boot failure
Date: Tue, 24 Jul 2007 20:08:25 +0200 [thread overview]
Message-ID: <46A64019.4010508@imap.cc> (raw)
In-Reply-To: <20070724095614.GB625@suse.de>
[-- Attachment #1: Type: text/plain, Size: 2196 bytes --]
Alright, I know what's going on now, and it looks like a problem with
the Opensuse init script. In fact, the initrd for the Xen enabled
kernel got a *different* init script than the one for the non-Xen one.
The difference being:
--- /tmp/testing/init 2007-07-24 15:53:58.000000000 +0200
+++ /tmp/xentest/init 2007-07-24 15:54:16.000000000 +0200
@@ -308,6 +308,9 @@
fi
fi
+caps="$(</proc/xen/capabilities)"
+if [ "$caps" != "${caps%control_d*}" ]; then
+
params=
for p in $(cat /proc/cmdline) ; do
case $p in
@@ -509,6 +512,32 @@
echo "Loading dm-snapshot"
modprobe dm-snapshot $params
+else
+
+params=
+for p in $(cat /proc/cmdline) ; do
+ case $p in
+ dm-mod.*)
+ params="$params ${p#dm-mod.}"
+ ;;
+ esac
+done
+echo "Loading dm-mod"
+modprobe dm-mod $params
+
+params=
+for p in $(cat /proc/cmdline) ; do
+ case $p in
+ dm-snapshot.*)
+ params="$params ${p#dm-snapshot.}"
+ ;;
+ esac
+done
+echo "Loading dm-snapshot"
+modprobe dm-snapshot $params
+
+fi
+
echo -n "Waiting for /dev/mapper/control to appear: "
for i in 1 2 3 4 5; do
[ -e /dev/mapper/control ] && break
In clear: the Xen init script reads /proc/xen/capabilities and if it
doesn't find the magic string "control_d" in it, willfully *skips*
loading all the SCSI and ATA stuff.
The missing piece then is the innocent little line:
/init: line 311: /proc/xen/capabilities: No such file or directory
appearing on my screen during boot ... BOOM!
If I just diligently type all the skipped modprobe commands
$ modprobe scsi_mod
$ modprobe sd_mod
$ modprobe processor
$ modprobe thermal
$ modprobe libata
$ modprobe ahci
$ modprobe pata_marvell
$ modprobe scsi_transport_spi
$ modprobe aic7xxx
$ modprobe fan
$ modprobe edd
$ ^D
into the fallback shell by hand, the system comes up without further ado.
So there, case solved. Now you sort it out who's to fix what. :-)
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: 253 bytes --]
next prev parent reply other threads:[~2007-07-24 18:08 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
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 [this message]
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=46A64019.4010508@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