From: Ian Campbell <ian.campbell@citrix.com>
To: xen-devel <xen-devel@lists.xen.org>
Cc: Ian Jackson <Ian.Jackson@eu.citrix.com>,
Stefano Stabellini <Stefano.Stabellini@eu.citrix.com>
Subject: Re: OVMF related osstest failures on multiple branches
Date: Wed, 6 Jan 2016 14:27:57 +0000 [thread overview]
Message-ID: <1452090477.21055.48.camel@citrix.com> (raw)
In-Reply-To: <1452083701.21055.43.camel@citrix.com>
On Wed, 2016-01-06 at 12:35 +0000, Ian Campbell wrote:
> The fly in the ointment of this theory is that the Jessie upgrade doesn't
> seem to have broken unstable in this way, for some reason, which is what I
> intend to investigate first.
One difference between all the failing versions and xen-unstable is that
unstable has a newer OVMF 52a99493cce8 (works) vs cb9a7ebabcd6 (fails).
It's possible there is a fix in there which would explain this, but its a
lot of commits to trawl through.
That said, one did stand out (below). A hang would correlate with a
complete lack of output (serial, vga) in the failure case (e.g. the 4.6-
testing one at [0]). Jessie is GCC49.
Next step is I'm trying 4.6-testing with the newer OVMF to see if this is
worth pursuing.
Ian.
[0] http://logs.test-lab.xenproject.org/osstest/logs/76950/test-amd64-amd64-xl-qemuu-ovmf-amd64/info.html)
Ian.
commit 55e96f9c601781b8dc52c40747922f6ca3521f9e
Author: Ruiyu Ni <ruiyu.ni@intel.com>
Date: Thu Jul 9 08:55:23 2015 +0000
OvmfPkg: Fix GCC49 build hang in PeiCore
PeiCore hang when loads a PEIM whose section alignment requirement is 0x40
but the actual base address is 0x20 aligned.
The issue is caused by the following facts, in order:
1. GCC49 requires the section alignment of .data to be 0x40. So a new link
script gcc4.9-ld-script was added for GCC49 to specify the 0x40
alignment.
2. GenFw tool was enhanced to sync ELF's section alignment to PE header.
Before the enhancement, the section alignment of converted PE image
always equals to 0x20.
If only with #1 change, GCC49 build image won't hang in PeiCore because
the converted PE image still claims 0x20 section alignment which is
aligned to the align setting set in FDF file. But later with #2 change,
the converted PE image starts to claims 0x40 section alignment, while
build tool still puts the PEIM in 0x20 aligned address, resulting the
PeCoffLoaderLoadImage() reports IMAGE_ERROR_INVALID_SECTION_ALIGNMENT
error.
Contributed-under: TianoCore Contribution Agreement 1.0
Signed-off-by: Ruiyu Ni <ruiyu.ni@intel.com>
Reviewed-by: Liming Gao <liming.gao@intel.com>
Reviewed-by: Laszlo Ersek <lersek@redhat.com>
git-svn-id: https://svn.code.sf.net/p/edk2/code/trunk/edk2@17902 6f19259b-4bc3-4df7-8a09-765794883524
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel
next prev parent reply other threads:[~2016-01-06 14:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 12:35 OVMF related osstest failures on multiple branches Ian Campbell
2016-01-06 14:27 ` Ian Campbell [this message]
2016-01-06 15:28 ` Ian Campbell
2016-01-06 16:20 ` Jan Beulich
2016-01-06 16:28 ` Ian Jackson
2016-01-06 17:08 ` Ian Campbell
2016-01-06 17:14 ` Ian Jackson
2016-01-07 15:36 ` Ian Jackson
2016-01-07 15:42 ` Ian Campbell
2016-01-07 15:47 ` Ian Jackson
2016-01-07 15:53 ` Ian Jackson
2016-01-06 16:50 ` Wei Liu
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=1452090477.21055.48.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=Stefano.Stabellini@eu.citrix.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).