[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1251224072.13451.10.camel@penberg-laptop>
Date: Tue, 25 Aug 2009 21:14:32 +0300
From: Pekka Enberg <penberg@...helsinki.fi>
To: Jeremy Fitzhardinge <jeremy@...p.org>
Cc: Arnd Hannemann <hannemann@...s.rwth-aachen.de>,
Arnd Hannemann <Arnd.Hannemann@...s.rwth-aachen.de>,
LKML <linux-kernel@...r.kernel.org>,
"hannes@...xchg.org" <hannes@...xchg.org>,
"torvalds@...ux-foundation.org" <torvalds@...ux-foundation.org>,
"xen-devel@...ts.xensource.com" <xen-devel@...ts.xensource.com>,
Ingo Molnar <mingo@...e.hu>
Subject: Re: [bisected] 2.6.31 regression: fails to boot as xen guest
On Tue, 2009-08-25 at 11:06 -0700, Jeremy Fitzhardinge wrote:
> 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.
Which interrupt initialization is that? We call trap_init() _earlier_
now.
> However, this particular change shouldn't have any effect on interrupts
> being enabled early, right?
Yeah, interrupt enabling should not be affected.
Pekka
--
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