RE: [Xen-devel] experienced unstability

[Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>]

Looks likely the same problem I reported yesterday:

http://lists.xensource.com/archives/html/xen-devel/2009-04/msg00742.html

However my stack dump did NOT report xen_poll_irq or
xen_spin_lock at the top of the dump... I would have
remembered or commented on that.  Unfortunately I didn't
save the stack dump.

>From googling a bit, I suspect this might be a Linux
problem, perhaps exacerbated by Xen or 2.6.29-pv.

Dan


> -----Original Message-----
> From: Keir Fraser [mailto:keir.fraser@xxxxxxxxxxxxx]
> Sent: Tuesday, April 21, 2009 5:51 AM
> To: jon.hart; xen-devel@xxxxxxxxxxxxxxxxxxx
> Subject: Re: [Xen-devel] experienced unstability
> 
> 
> On 21/04/2009 12:26, "jon.hart" <jon.hart@xxxxxx> wrote:
> 
> > If a domU crash happens all I can do is to destroy this 
> guest because it
> > is unaccessable in this state.
> > 
> > My questions are: is there an other kernel tree I can try? 
> What can I do
> > to figure out what the problem is or to fix this?
> 
> You could try 
> http://xenbits.xensource.com/linux-2.6.18-xen.hg in a domU and
> see if that stabilises that particular domU. The bug looks 
> possibly like a
> spinlock deadlock within the domU kernel, or possibly a bug in the
> paravirtualised spinlock implementation.
> 
>  -- Keir
> 
> 
> 
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-devel
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel