From mboxrd@z Thu Jan 1 00:00:00 1970 From: Kip Macy Subject: Re: xm pause causing lockup Date: Fri, 15 Apr 2005 10:12:33 -0700 Message-ID: References: Reply-To: Kip Macy Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: Content-Disposition: inline List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Pratt Cc: xen-devel List-Id: xen-devel@lists.xenproject.org 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 : mov 0x40(%esp,1),%eax (gdb) x/i 0xfc51c746 0xfc51c746 : mov 0x14(%eax),%ebx (gdb) x/i 0xfc51c74b 0xfc51c74b : je 0xfc51c740 (gdb) x/i 0xfc51c740 0xfc51c740 : repz nop=20 -Kip On 4/14/05, Ian Pratt wrote: >=20 >=20 > > -----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. >=20 > Is your hypothesis that Xen gets stuck in either the mmuext_op or > mmu_update loops? > Are you running with watchdog enabled? >=20 > It might be good to add a printk at the end so that you can prove this. >=20 > Hitting 'd' on the debug console will give us an EIP on CPU 1. >=20 > Ian >