From: Paul Larson <plars@linuxtestproject.org>
To: Keir Fraser <Keir.Fraser@cl.cam.ac.uk>
Cc: Ian Pratt <m+Ian.Pratt@cl.cam.ac.uk>,
xen-devel <xen-devel@lists.sourceforge.net>
Subject: Re: xen problem with save/restore
Date: Wed, 08 Dec 2004 22:20:03 -0600 [thread overview]
Message-ID: <1102566003.2815.2.camel@localhost.localdomain> (raw)
In-Reply-To: <E1Cc7yD-0001z5-00@mta1.cl.cam.ac.uk>
On Wed, 2004-12-08 at 13:59, Keir Fraser wrote:
> > On Tue, 2004-12-07 at 19:20, Ian Pratt wrote:
> > > What were you using before? I seem to recall it was 2.0-testing.bk?
> > Yes, 2.0-testing.bk fails, but xeno-unstable.bk passes.
> >
> > > There's currently very few changes between unstable and 2.0-testing
> > Great! Maybe it'll be easier to see what fixed it in xeno-unstable.
>
> The latest 2.0-testing and unstable trees only differ in that a new
> 'blktap' driver was added to the unstable tree, which is not even
> built by default. It really looks to be impossible that you could be
> seeing different behaviour between the two repositories. :-/
I see, I was running a diff of the trees a while ago and I see what you
mean. However, it has been very easy to reproduce this under testing,
but on unstable, it never failed for me even once. So, I installed gcc
3.2 and tried compiling testing with that, and it works now, no crash!
So it looks like it is a compiler issue after all.
Thanks,
Paul Larson
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-09 4:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 1:20 xen problem with save/restore Ian Pratt
2004-12-09 0:44 ` Paul Larson
2004-12-08 19:59 ` Keir Fraser
2004-12-09 4:20 ` Paul Larson [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 15:47 Ian Pratt
2004-12-09 21:56 ` Paul Larson
2004-12-09 16:55 ` Nuutti Kotivuori
2004-12-11 15:35 ` Paul Larson
2004-12-03 16:58 Paul Larson
2004-12-03 17:48 ` Jérôme Petazzoni
2004-12-03 18:27 ` Brian Wolfe
2004-12-03 18:54 ` Paul Larson
2004-12-07 4:44 ` Paul Larson
2004-12-08 3:05 ` Paul Larson
2004-12-03 15:22 Paul Larson
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=1102566003.2815.2.camel@localhost.localdomain \
--to=plars@linuxtestproject.org \
--cc=Keir.Fraser@cl.cam.ac.uk \
--cc=m+Ian.Pratt@cl.cam.ac.uk \
--cc=xen-devel@lists.sourceforge.net \
/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.