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: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] xm pause causing lockup
From: Kip Macy <kip.macy@xxxxxxxxx>
Date: Thu, 14 Apr 2005 12:41:13 -0700
Cc: xen-devel <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 14 Apr 2005 19:41:07 +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=aXVc/hrbLZebbzRnr6xCE5FnD8diIfX44cuupzFSwch5BJ6RQtUyIz1ZHN5TNVjG5afZvAjOaJGyiV0RCg4tJLPO6lHIzBVClqrVqqFOX2V6UKEmLVfXMGrC+EdNashAGbSvTfH2UqtdmPra/pNaykv4pT6mKxBZxRZs13oilsU=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <b1fa29170504132018110362f6@xxxxxxxxxxxxxx>
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: <b1fa291705041319464ffdb42a@xxxxxxxxxxxxxx> <4afce18847157fad34cd38e14fb83c2c@xxxxxxxxxxxx> <b1fa291705041320031af8f565@xxxxxxxxxxxxxx> <cafff1b5d55bd618912085cc8e2b34dc@xxxxxxxxxxxx> <b1fa29170504132018110362f6@xxxxxxxxxxxxxx>
Reply-to: Kip Macy <kip.macy@xxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
I haven't tracked down the problem yet, but I thought the following
was sufficiently interesting to post:

kmacy@curly while (1)
while? xm list
while? sleep 5
while? end
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     67.9        
xen-vm2            1      128    1  r----      4.0    9601
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     68.1        
xen-vm2            1      128    1  r----      4.0    9601
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     68.3        
xen-vm2            1      128    1  r----      4.0    9601
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     68.5        
xen-vm2            1      128    1  r----      4.0    9601
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     68.7        
xen-vm2            1      128    1  r----      4.0    9601
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     68.9        
xen-vm2            1      128    1  r----      4.0    9601

xen-vm2 is always shown as running, but its time is not increasing.

               -Kip



On 4/13/05, Kip Macy <kip.macy@xxxxxxxxx> wrote:
> On 4/13/05, Keir Fraser <Keir.Fraser@xxxxxxxxxxxx> wrote:
> > Probably easiest way to trace this is with printk's in Xen. The guts of
> > the work is done by domain_pause_by_systemcontroller() in xen/sched.h.
> > This in turn calls domain_sleep() in common/schedule.c.
> 
> I traced through that code a while back when trying to decide what to
> call from the int3 handler.
> 
> A particularly
> > interesting place to look will be teh synchronous spin loop at the end
> > of domain_sleep -- if the paused domain isn't descheduled for some
> > weird reason then the spin loop would never exit and domain0 would
> > hang.
> 
> Good point. It will be interesting to see.
> 
> I sometimes wonder if I should keep some of the buggy versions of
> FreeBSD around for regression testing as they trigger some interesting
> behaviours in xen and xend.
> 
>            -Kip
>

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