[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A46BF9.6010906@goop.org>
Date: Mon, 23 Jul 2007 01:51:05 -0700
From: Jeremy Fitzhardinge <jeremy@...p.org>
To: Tilman Schmidt <tilman@...p.cc>
CC: LKML <linux-kernel@...r.kernel.org>, g3vbv@...eyonder.co.uk,
nix.or.die@...glemail.com
Subject: Re: 2.6.22-git17 boot failure
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
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists