WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] xm pause causing lockup

To: "Kip Macy" <kip.macy@xxxxxxxxx>
Subject: RE: [Xen-devel] xm pause causing lockup
From: "Ian Pratt" <m+Ian.Pratt@xxxxxxxxxxxx>
Date: Fri, 15 Apr 2005 18:25:55 +0100
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 15 Apr 2005 17:25:48 +0000
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcVB3ls/030ZwwSuTWiFuF6D2VXQaAAAXcYA
Thread-topic: [Xen-devel] xm pause causing lockup
Wild! It really is looping in get_page_type.

Any chance you could use the serial debugger to find out what x, nx and
y are in the cmpxchg?

I've tried to think of duff inputs that could cause it to loop, but I'm
not smart enough.

Ian 

> -----Original Message-----
> From: Kip Macy [mailto:kip.macy@xxxxxxxxx] 
> Sent: 15 April 2005 18:13
> To: Ian Pratt
> Cc: Keir Fraser; xen-devel; ian.pratt@xxxxxxxxxxxx
> Subject: Re: [Xen-devel] xm pause causing lockup
> 
> Great, thanks. I'm now running a completely fresh tree from 
> last night.
> 
> Over the course of several minutes I hit 'd' a number of 
> times. The addresses I got were:
> 
> 0xfc51c742
> 0xfc51c746
> 0xfc51c74b
> 0xfc51c740
> 
> (gdb) x/i 0xfc51c742
> 0xfc51c742 <get_page_type+1218>:        mov    0x40(%esp,1),%eax
> (gdb) x/i 0xfc51c746
> 0xfc51c746 <get_page_type+1222>:        mov    0x14(%eax),%ebx
> (gdb) x/i 0xfc51c74b
> 0xfc51c74b <get_page_type+1227>:        je     0xfc51c740 
> <get_page_type+1216>
> (gdb) x/i 0xfc51c740
> 0xfc51c740 <get_page_type+1216>:        repz nop 
> 
> 
>                -Kip
> 
> On 4/14/05, Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx> wrote:
> > 
> > 
> > > -----Original Message-----
> > > From: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > > [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf 
> Of Kip Macy
> > > Sent: 15 April 2005 05:36
> > > To: Keir Fraser
> > > Cc: xen-devel
> > > Subject: Re: [Xen-devel] xm pause causing lockup
> > >
> > > To further check this I added:
> > >  printk("%s %d %d %d %d %d\n", __FUNCTION__, op->cmd,
> > > op->mfn, count, success_count, domid); to
> > > HYPERVISOR_mmuext_op and something similar to mmu_update.
> > 
> > Is your hypothesis that Xen gets stuck in either the mmuext_op or 
> > mmu_update loops?
> > Are you running with watchdog enabled?
> > 
> > It might be good to add a printk at the end so that you can 
> prove this.
> > 
> > Hitting 'd' on the debug console will give us an EIP on CPU 1.
> > 
> > Ian
> >
> 

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