From mboxrd@z Thu Jan 1 00:00:00 1970 From: Daniel Magenheimer Subject: RE: Re: Error while running the xm test suite: Cannot handle page request order 0! Date: Wed, 17 Sep 2008 21:45:14 +0000 (GMT) Message-ID: <6ebaf9d0-65fe-4e8e-a441-c4a3842155bc@default> References: Mime-Version: 1.0 Content-Type: multipart/mixed; boundary="===============0111640045==" Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Keir Fraser , Stefan Berger Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org --===============0111640045== Content-Type: multipart/alternative; boundary="__12216879732603643acsmt706.oracle.com" --__12216879732603643acsmt706.oracle.com Content-Type: text/plain; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle pa= ge request order 0!Perhaps the cset numbers refer to 3.3-testing, not xen-u= nstable? -----Original Message----- From: Keir Fraser [mailto:keir.fraser@eu.citrix.com] Sent: Wednesday, September 17, 2008 3:40 PM To: Stefan Berger Cc: xen-devel@lists.xensource.com Subject: Re: [Xen-devel] Re: Error while running the xm test suite: Canno= t handle page request order 0! On 17/9/08 22:23, "Stefan Berger" wrote: > I suspect a memory leak in your particular configuration. It=92d be= =20 > good to try to narrow down which changeset or range of changesets=20 > introduced the problem.=20 I narrowed it down as far as : 18411 fails and 18407 works, which is ve= ry strange since I don't see any critical changes in between...=20 Yes. 18411 affects only ia64. 18410 affects only internal ioemu (not used= by default build). 18409 reverts 18408, and simply adds a wrapper around = =91install=92 inside the tools/ directory. Weird! -- Keir --__12216879732603643acsmt706.oracle.com Content-Type: text/html; charset=Windows-1252 Content-Transfer-Encoding: quoted-printable Re: [Xen-devel] Re: Error while running the xm test suit= e: Cannot handle page request order 0!
Perhaps the cset numbers refer to 3.3-testing, not=20 xen-unstable?
-----Original Message-----
From: Keir Fraser=20 [mailto:keir.fraser@eu.citrix.com]
Sent: Wednesday, September 1= 7,=20 2008 3:40 PM
To: Stefan Berger
Cc:=20 xen-devel@lists.xensource.com
Subject: Re: [Xen-devel] Re: Erro= r=20 while running the xm test suite: Cannot handle page request order=20 0!

On 17/9/08 22:23, "Stefan Berger"=20 <stefanb@us.ibm.com> wrote:
> I suspect a memory leak in your parti= cular=20 configuration. It’d be
> good to try to narrow down which= changeset=20 or range of changesets
> introduced the problem.

I narrowed it down as far as : 18411 fails= and=20 18407 works, which is very strange since I don't see any critical chang= es in=20 between...=20

Yes. 18411 affects only ia64. 1841= 0=20 affects only internal ioemu (not used by default build). 18409 reverts 18= 408,=20 and simply adds a wrapper around ‘install’ inside the tools= / directory.=20 Weird!

 -- Keir
 --__12216879732603643acsmt706.oracle.com-- --===============0111640045== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel --===============0111640045==--