[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <46A504A3.3070205@imap.cc>
Date: Mon, 23 Jul 2007 21:42:27 +0200
From: Tilman Schmidt <tilman@...p.cc>
To: Jeremy Fitzhardinge <jeremy@...p.org>
CC: LKML <linux-kernel@...r.kernel.org>, andi@...stfloor.org,
nix.or.die@...glemail.com
Subject: Re: 2.6.22-git17 boot failure
Am 23.07.2007 16:51 schrieb Jeremy Fitzhardinge:
> Tilman Schmidt wrote:
>> Attached are .config and dmesg (as captured in SuSE's /var/log/boot.msg)
>> of a CONFIG_XEN=n git-current build.
>
> That's dmesg from a successful boot?
Yes.
> What does it look like when its
> unsuccessful? Where do they start to differ?
To answer that, I have reproduced the effect with kernel 2.6.23-rc1 with
netconsole compiled in. I'm attaching both captures, for CONFIG_XEN=y
(unsuccessful) as well CONFIG_XEN=n (successful).
The first noticeable difference is that the nonzero timestamps starting
after the line "Detected 3197.059 MHz processor" are much bigger with XEN -
but perhaps that's expected.
More to the point, everything from:
SCSI subsystem initialized
on is completely missing, including all the [S/P]ATA, SCSI, parport, AGP,
USB, Firewire, RTC and of course ext3 messages. Only the "device-mapper"
line still appears.
Btw, the NULL pointer BUG at the end of the successful boot is new with
2.6.23-rc1. I'll report that separately but didn't want to edit anything.
HTH
T.
--
Tilman Schmidt E-Mail: tilman@...p.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)
View attachment "netconsole-2.6.23-rc1-xen" of type "text/plain" (23393 bytes)
View attachment "netconsole-2.6.23-rc1-noxen" of type "text/plain" (39177 bytes)
Download attachment "signature.asc" of type "application/pgp-signature" (254 bytes)
Powered by blists - more mailing lists