[Xen-devel] Assertion '__task_on_runqueue(prev)' failed in sched

To:	xen-devel@xxxxxxxxxxxxxxxxxxx
Subject:	[Xen-devel] Assertion '__task_on_runqueue(prev)' failed in sched_bvt.c
From:	George Dunlap <dunlapg@xxxxxxxxx>
Date:	Sat, 21 Jan 2006 14:47:21 -0500
Delivery-date:	Sat, 21 Jan 2006 19:55:27 +0000
Domainkey-signature:	a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=GiAq0U2uovGszxxTmrOxXnFsnzO74rk/Qu++h6zPSXbNLpBv8BSgj7FrXGmkvT+LMLHinacA0CU7zbJGFeAUCN7V6LXFIePA6B4uifHPl8+H41LhfBxeGS0PcQ2w6si7zJFk54d5MCrQ/8s4ufpnJw3AWLsieMkT6vD0MbJyMU4=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxxx
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>
Sender:	xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

I'm using a tree forked from xen-unstable in mid-July, with debug mode
on.  With long testing runs in a domU in a multiprocessor host, I get
the above assertion maybe one in five times.

There was a message from early June saying that the invariants had
changed, and that the ASSERT() in question was no longer right, but
it's still in xen-3.0-testing.  Can anyone verify that the ASSERT() in
sched_bvt.c:bvt_do_schedule() is wrong?

Thanks,
 -George

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

WARNING - OLD ARCHIVES

xen-devel

[Xen-devel] Assertion '__task_on_runqueue(prev)' failed in sched_bvt.c