From mboxrd@z Thu Jan 1 00:00:00 1970 From: John Weekes Subject: Re: credit2 BUG_ON triggered Date: Wed, 20 Apr 2011 12:10:24 -0700 Message-ID: <4DAF2FA0.9020008@nuclearfallout.net> References: <4DADF781.7070004@nuclearfallout.net> <4DAF05D0.4060300@nuclearfallout.net> <1303318285.1955.3629.camel@elijah> <4DAF18F0.5090400@nuclearfallout.net> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4DAF18F0.5090400@nuclearfallout.net> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: George Dunlap Cc: "xen-devel@lists.xensource.com" , Keir Fraser List-Id: xen-devel@lists.xenproject.org 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. -John