This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Re: [bisected] 2.6.31 regression: fails to boot as xen guest

To: Pekka Enberg <penberg@xxxxxxxxxxxxxx>
Subject: [Xen-devel] Re: [bisected] 2.6.31 regression: fails to boot as xen guest
From: Jeremy Fitzhardinge <jeremy@xxxxxxxx>
Date: Tue, 25 Aug 2009 11:06:52 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Arnd Hannemann <hannemann@xxxxxxxxxxxxxxxxxxx>, LKML <linux-kernel@xxxxxxxxxxxxxxx>, "hannes@xxxxxxxxxxx" <hannes@xxxxxxxxxxx>, Arnd Hannemann <Arnd.Hannemann@xxxxxxxxxxxxxxxxxxx>, "torvalds@xxxxxxxxxxxxxxxxxxxx" <torvalds@xxxxxxxxxxxxxxxxxxxx>, Ingo Molnar <mingo@xxxxxxx>
Delivery-date: Tue, 25 Aug 2009 11:07:22 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <1251219129.4852.1.camel@penberg-laptop>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4A9407B1.6020400@xxxxxxxxxxxxxxxxxxx> <84144f020908250929t7d4a74f1n4827de04e5c4c56a@xxxxxxxxxxxxxx> <4A94161A.2020609@xxxxxxxxxxxxxxxxxxx> <1251219129.4852.1.camel@penberg-laptop>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv: Gecko/20090814 Fedora/3.0-2.6.b3.fc11 Lightning/1.0pre Thunderbird/3.0b3
On 08/25/09 09:52, Pekka Enberg wrote:
> Hi Arnd,
> On Tue, 2009-08-25 at 18:49 +0200, Arnd Hannemann wrote:
>>> Thanks for doing the bisect! Can we also see your .config also?
>> Config for -rc7 is attached. My bisect configs were based on that
> Thanks! While we wait for the Xen people, you can try the following
> patch to see if we can narrow the bug down to trap_init().

I think there's a problem that the side-effect of this change is that
interrupt initialization comes later, and so the dynamically allocated
arrays are not set up when the first interrupt comes in.

However, this particular change shouldn't have any effect on interrupts
being enabled early, right?

I have a local workaround which simply reverts the arrays back to
statically allocated, but it isn't very satisfactory (large memory hit,
esp if you're not running Xen).


Xen-devel mailing list