From: Andrew Cooper <andrew.cooper3@citrix.com>
To: M A Young <m.a.young@durham.ac.uk>
Cc: xen-devel@lists.xen.org, Jason Fritcher <jkf@wolfnet.org>
Subject: Re: Xen BUG at page_alloc.c:1738 (Xen 4.5)
Date: Fri, 29 May 2015 11:57:49 +0100 [thread overview]
Message-ID: <5568462D.9040802@citrix.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1505291141380.29784@procyon.dur.ac.uk>
On 29/05/15 11:50, M A Young wrote:
> On Fri, 29 May 2015, Andrew Cooper wrote:
>
>> Are you in a position to compile identical Xen 4.5 source with two different
>> versions of gcc? (current staging-4.5 staging even has the gcc5 build fix
>> in)
>>
>> If it is a gcc compiler bug, we would expect the version compiled with gcc
>> 4.9 to work fine, but the one compiled with 5 to fail in the identified
>> manor.
> I did a bit of testing - xen-4.5.1-rc1 built on Fedora 22 (gcc5) doesn't
> boot for me, but if I replace xen.gz with one from the same code built on
> Fedora 21 (gcc4) then it does boot. There are rpms and build logs
> available via
> http://copr.fedoraproject.org/coprs/myoung/xentest/build/93366/
> if anyone else wants to do some testing.
>
> Michael Young
Do you have easy access to xen-syms from each build?
~Andrew
next prev parent reply other threads:[~2015-05-29 10:57 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-29 6:24 Xen BUG at page_alloc.c:1738 (Xen 4.5) Jason Fritcher
2015-05-29 10:09 ` Andrew Cooper
2015-05-29 10:50 ` M A Young
2015-05-29 10:57 ` Andrew Cooper [this message]
2015-05-29 11:17 ` M A Young
2015-05-29 18:12 ` Andrew Cooper
2015-05-30 22:07 ` M A Young
2015-05-30 22:43 ` Andrew Cooper
2015-06-01 7:40 ` Jan Beulich
2015-06-01 7:47 ` M A Young
2015-06-06 21:00 ` M A Young
-- strict thread matches above, loose matches on Subject: below --
2015-05-19 18:06 Major Hayden
2015-05-19 18:16 ` Andrew Cooper
2015-05-20 2:11 ` Major Hayden
2015-05-20 10:41 ` Jan Beulich
2015-05-20 16:52 ` Major Hayden
2015-05-20 19:51 ` M A Young
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=5568462D.9040802@citrix.com \
--to=andrew.cooper3@citrix.com \
--cc=jkf@wolfnet.org \
--cc=m.a.young@durham.ac.uk \
--cc=xen-devel@lists.xen.org \
/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.