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/
Home Products Support Community News


Re: [Xen-devel] credit2 BUG_ON triggered

To: George Dunlap <george.dunlap@xxxxxxxxxx>
Subject: Re: [Xen-devel] credit2 BUG_ON triggered
From: John Weekes <lists.xen@xxxxxxxxxxxxxxxxxx>
Date: Wed, 20 Apr 2011 12:10:24 -0700
Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Keir Fraser <keir@xxxxxxx>
Delivery-date: Wed, 20 Apr 2011 12:11:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4DAF18F0.5090400@xxxxxxxxxxxxxxxxxx>
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
References: <4DADF781.7070004@xxxxxxxxxxxxxxxxxx> <BANLkTi=a-MgnDF5uqnTJhUs5xzyVFKMysg@xxxxxxxxxxxxxx> <4DAF05D0.4060300@xxxxxxxxxxxxxxxxxx> <1303318285.1955.3629.camel@elijah> <4DAF18F0.5090400@xxxxxxxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv: Gecko/20110303 Thunderbird/3.1.9
On 4/20/2011 10:33 AM, John Weekes wrote:
I'll try 4.1-testing again with the patch reversion.

4.1-testing is now doing the same thing as unstable for me -- the domU freezes after "(XEN) HVM5: Writing SMBIOS tables ..." -- and only when credit2 is being used.

I did get it to "work" (panic) once, but then saw that it said debug=n. After that, I rebooted, did a "make clean" + recompile, and repeated my test, and it still said debug=n (this must be a separate build issue), so I completely wiped, checked out, reverted, recompile,d and tried again, leading to the current situation.

Here's what it said when it *did* crash. This is partial output because the later reboot overwrote part of the screen in ipmitool:

(XEN) irq.c:324: Dom3 callback via changed to Direct Vector 0xe9
(XEN) Xen BUG at sched_credit2.c:811
(XEN) ----[ Xen-4.1.1-rc1-pre  x86_64  debug=n  Not tainted ]----
(XEN) CPU:    12

That means that it died at one of your special debug lines:

BUG_ON(test_bit(__CSFLAG_scheduled, &svc->flags));

I'm trying to find a way to reproduce that output.


Xen-devel mailing list