From: Daniel Magenheimer <dan.magenheimer@oracle.com>
To: Keir Fraser <keir.fraser@eu.citrix.com>,
Stefan Berger <stefanb@us.ibm.com>
Cc: xen-devel@lists.xensource.com
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) [thread overview]
Message-ID: <6ebaf9d0-65fe-4e8e-a441-c4a3842155bc@default> (raw)
In-Reply-To: <C4F737BC.1D534%keir.fraser@eu.citrix.com>
[-- Attachment #1.1: Type: text/plain, Size: 1068 bytes --]
Re: [Xen-devel] Re: Error while running the xm test suite: Cannot handle page request order 0!Perhaps the cset numbers refer to 3.3-testing, not xen-unstable?
-----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: Cannot handle page request order 0!
On 17/9/08 22:23, "Stefan Berger" <stefanb@us.ibm.com> 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 narrowed it down as far as : 18411 fails and 18407 works, which is very strange since I don't see any critical changes in between...
Yes. 18411 affects only ia64. 18410 affects only internal ioemu (not used by default build). 18409 reverts 18408, and simply adds a wrapper around ‘install’ inside the tools/ directory. Weird!
-- Keir
[-- Attachment #1.2: Type: text/html, Size: 2113 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2008-09-17 21:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-16 16:33 Error while running the xm test suite: Cannot handle page request order 0! Stefan Berger
2008-09-16 16:58 ` Keir Fraser
2008-09-16 17:09 ` Stefan Berger
2008-09-16 19:03 ` Keir Fraser
2008-09-16 19:09 ` Keir Fraser
2008-09-16 20:50 ` Stefan Berger
2008-09-16 21:10 ` Keir Fraser
2008-09-16 21:17 ` Stefan Berger
2008-09-16 21:21 ` Keir Fraser
2008-09-17 21:23 ` Stefan Berger
2008-09-17 21:39 ` Keir Fraser
2008-09-17 21:45 ` Daniel Magenheimer [this message]
2008-09-18 1:54 ` Stefan Berger
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6ebaf9d0-65fe-4e8e-a441-c4a3842155bc@default \
--to=dan.magenheimer@oracle.com \
--cc=keir.fraser@eu.citrix.com \
--cc=stefanb@us.ibm.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.