WARNING - OLD ARCHIVES

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

xen-devel

Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle

To: Stefan Berger <stefanb@xxxxxxxxxx>
Subject: Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle page request order 0!
From: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Date: Tue, 16 Sep 2008 22:21:56 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 16 Sep 2008 14:21:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <OFAA94C914.31027ED3-ON852574C6.0074E156-852574C6.0074FB35@xxxxxxxxxx>
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: AckYQj72fcmwgIQ1Ed2riAAWy6hiGQ==
Thread-topic: [Xen-devel] Re: Error while running the xm test suite: Cannot handle page request order 0!
User-agent: Microsoft-Entourage/11.4.0.080122
On 16/9/08 22:17, "Stefan Berger" <stefanb@xxxxxxxxxx> wrote:

> I suspect a memory leak in your particular configuration. It’d be
> good to try to narrow down which changeset or range of changesets
> introduced the problem.
>

I'll narrow it down, but it will take a while. I'll let you know.

As a starting point, if you are also using up-to-date linux-2.6.18-xen.hg then try reverting it back a month and see if the problem goes away. If not, bring back to tip and try same on xen-unstable.hg. This will establish which repo contains the bug. It’ll probably turn out to be xen-unstable.hg, at which point I would do ‘hg –v history xen | less’ to look for scary looking patches inside the hypervisor itself, and use that to guide which changesets I test for working vs non-working. You should be able to do much better than a binary chop this way.

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