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] xen-unstable: Xen BUG at sched_credit.c:925

To: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>, "Xen-Devel (E-mail)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] xen-unstable: Xen BUG at sched_credit.c:925
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Fri, 13 Nov 2009 17:15:41 +0000
Delivery-date: Fri, 13 Nov 2009 09:16:05 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <9fcedf22-c807-47a6-bc3f-28d19c055615@default>
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>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acpkg5o74dNLkTyjS4uMKMxN7G7PtQAAVLhm
Thread-topic: [Xen-devel] xen-unstable: Xen BUG at sched_credit.c:925
User-agent: Microsoft-Entourage/
On 13/11/2009 17:04, "Dan Magenheimer" <dan.magenheimer@xxxxxxxxxx> wrote:

> I'm seeing this BUG/crash when shutting down a domain.
> I've only seen it when running a domain with tmem, though
> I'm not clear on what the relationship would be.
> I haven't tested tmem with xen-unstable for a couple of
> months now and I see five patches to sched_credit.c
> since Aug 25... should I just try backing those out,
> or any other ideas on what might be going on?  The
> code around the BUG is not very intuitive to me
> and it looks like that chunk of code hasn't been
> changed for years.

Worth a try, but I don't think any of those changesets are likely to cause
this bug either. It's not a BUG() I've seen or had reported triggering

 -- Keir

Xen-devel mailing list