[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <519a8b110801201129kd4347d5mf87920f69cf1821e@mail.gmail.com>
Date: Sun, 20 Jan 2008 20:29:47 +0100
From: xming <xmingske@...il.com>
To: "Jeremy Fitzhardinge" <jeremy@...p.org>
Cc: linux-kernel@...r.kernel.org,
Xen-devel <xen-devel@...ts.xensource.com>
Subject: Re: Cannot boot xen DomU > 2.6.23.1
On Jan 20, 2008 7:37 PM, Jeremy Fitzhardinge <jeremy@...p.org> wrote:
> xming wrote:
> > ok I have done some of them, but I still don't know what I should be looking
> > at. Do you mean code related to xen or code related to have_vcpu_info_placement?
> > Please be patient with me :)
> >
> > I just paste some of the result (around those addresses) here:
> >
>
> Thanks, that answers that particular question; the vcpu is blocked
> waiting for something to happen, which probably means it missed the
> event which was supposed to wake it up. Why is another question. At
> least there's a workaround, and that workaround gives me some clue where
> to look.
Want me to test it?
> BTW, is it an SMP or UP domain? Does it make a difference?
It doesn't matter, I tried vcpu=1 and vcpu=2, unless you want me to try
to recompile a UP kernel?
> >> OK, good. I Didn't Break It (tm) ;)
>
> > So no fix from you? :)
>
> Maybe when I have nothing else to do.
I'll wait, or should I poke xen-devel?
--
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