From mboxrd@z Thu Jan  1 00:00:00 1970
From: Kip Macy <kip.macy@gmail.com>
Subject: xm pause causing lockup
Date: Wed, 13 Apr 2005 19:46:37 -0700
Message-ID: <b1fa291705041319464ffdb42a@mail.gmail.com>
Reply-To: Kip Macy <kip.macy@gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Return-path: <xen-devel-bounces@lists.xensource.com>
Content-Disposition: inline
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel <xen-devel@lists.xensource.com>
List-Id: xen-devel@lists.xenproject.org

Is there some critical section where "xm pause" might cause a lockup?
When I run FreeBSD to some point (I don't know where - the console
isn't giving output) - and then pause it, the machine locks up. I
can't even get info from xen apart from switching the switching the
serial input.


kmacy@siml4 ssh moe
kmacy@moe xm list
Name              Id  Mem(MB)  CPU  State  Time(s)  Console
Domain-0           0      507    0  r----     54.5       =20
xen-vm2            1      128    1  r----      0.1    9601
kmacy@moe xm pause 1

<....>
Note that this is with domu_debug =3D n.

The changeset I'm using is from the -unstable on the 11th.=20


         -Kip