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: Ian Pratt <m+Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm pause causing lockup
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Fri, 15 Apr 2005 10:12:33 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Fri, 15 Apr 2005 17:12:34 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=SM6H//Uhq2A4Cbut7we8t99+W3KTlDXDU9Fl4tPgSqOhrdO99OEMzj6DYoacVvKmDmgem9JM55pa2PA/RD3cEpQ/Q+8xYCZUNhsu3cndBIsXwYs+7DT2CqpRlVgg1S1lC9YApjAQcZUqD9IVEJZEUkq9OkCvTexjqRoEb3+Oh6Y=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3BAC@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
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>
References: <A95E2296287EAD4EB592B5DEEFCE0E9D1E3BAC@xxxxxxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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