From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Tilman Schmidt <tilman@imap.cc>
Cc: LKML <linux-kernel@vger.kernel.org>,
g3vbv@blueyonder.co.uk, nix.or.die@googlemail.com
Subject: Re: 2.6.22-git17 boot failure
Date: Mon, 23 Jul 2007 01:51:05 -0700 [thread overview]
Message-ID: <46A46BF9.6010906@goop.org> (raw)
In-Reply-To: <46A3FBB7.9000608@imap.cc>
Tilman Schmidt wrote:
> on Mon, 23 Jul 2007 01:47:30 +0200, /me wrote:
>
>> On my test machine with a Pentium D 940 processor, Intel DQ965GF
>> mainboard and SATA disks, kernel 2.6.22-git17 (32 bit build) fails
>> to come up because it cannot find the disk drives. Same issue
>> with a clone of the 'linus' git tree. Anything known?
>>
>
> Ok, scrap this. Turns out it wasn't a good idea to answer 'Y' to
> the new XEN config option during "make oldconfig". After changing
> it to CONFIG_XEN=n, all's well again. Sorry for the noise.
>
That seems very unlikely. If you're booting a Xen-enabled kernel on
bare hardware, the Xen code should have no effect at all. It certainly
shouldn't prevent you from probing devices.
Could you send me your .config and dmesg output? Are you saying that
leaving PARAVIRT enabled but XEN disabled will allow your system to
boot? What happens if you enable VMI and/or LGUEST?
Thanks,
J
next prev parent reply other threads:[~2007-07-23 8:52 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 [this message]
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
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=46A46BF9.6010906@goop.org \
--to=jeremy@goop.org \
--cc=g3vbv@blueyonder.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
--cc=tilman@imap.cc \
/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