From mboxrd@z Thu Jan  1 00:00:00 1970
From: Mukesh Rathor <mukesh.rathor@oracle.com>
Subject: dom0 hang
Date: Wed, 24 Jun 2009 11:15:44 -0700
Message-ID: <4A426D50.80401@oracle.com>
Reply-To: mukesh.rathor@oracle.com
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/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/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

Here are the details on the dom0 hang:

xen: 3.4.0
dom0: 2.6.18-128

dom0.vcpu0: spinning in schedule() on spinlock: spin_lock_irq(&rq->lock);
dom0.vcpu1: eip == ret after __HYPERVISOR_event_channel_op hypercall

Just of of curiosity, I set breakpoint at the above ret in kdb, and it never 
got hit. So I wondered why vcpu1 is not getting scheculed, and noticed that 
xen.schedule always schedules vcpu0. Two cpus on the box, other one is mostly 
in idle.

anyways, I've turned lock debugging on in dom0 and reproducing it right now.

thanks,
Mukesh