[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • 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=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

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?


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.