Re: xm pause causing lockup

[Kip Macy <kip.macy@gmail.com>]

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@cl.cam.ac.uk> wrote:
> 
> 
> > -----Original Message-----
> > From: xen-devel-bounces@lists.xensource.com
> > [mailto:xen-devel-bounces@lists.xensource.com] 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
>