xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
To: Anthony PERARD <anthony.perard@citrix.com>
Cc: xen-devel@lists.xensource.com, wei.liu2@citrix.com
Subject: Re: [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier]
Date: Mon, 28 Nov 2016 10:03:07 -0500	[thread overview]
Message-ID: <20161128150307.GC2304@localhost.localdomain> (raw)
In-Reply-To: <20161128123808.GD1847@perard.uk.xensource.com>

On Mon, Nov 28, 2016 at 12:38:08PM +0000, Anthony PERARD wrote:
> On Fri, Nov 25, 2016 at 08:24:00AM -0500, Konrad Rzeszutek Wilk wrote:
> > Hey Wei, Anthony,
> > 
> > Are you guys OK pushing this commit: 2667ad40919a in the
> > git://xenbits.xen.org/ovmf.git     
> > 
> > tree? Without this I cannot build Xen 4.8 with TianoCore
> > (--enable-ovmf).
> 
> Can you actually start a guest this OVMF (when it's build on Fedora Core
> 25, and built using the GCC5 toolchain)?

Hadn't gotten to that part yet.
> 
> On Arch Linux (gcc (GCC) 6.2.1 20160830), if I build OVMF with the GCC5
> toolchain, the firmware fail to boot.

Yikes!
> 
> For reference, I have this error:
> !!!! X64 Exception Type - 06(#UD - Invalid Opcode)  CPU Apic ID - 00000000 !!!!
> RIP  - 000000001F26AF6B, CS  - 0000000000000038, RFLAGS - 0000000000010202
> RAX  - 0000000000000001, RCX - 000000001F26AF51, RDX - 0000000000000004
> RBX  - 0000000000000000, RSP - 000000001F43C510, RBP - 000000001E583D18
> RSI  - 0000000000000003, RDI - 0000000000000001
> R8   - 0000000000000000, R9  - 0000000000000000, R10 - 000000001E58DB98
> R11  - 0000000000000002, R12 - 000000001E58D898, R13 - 0000000000000000
> R14  - 000000001E58D8A0, R15 - 000000001F26D001
> DS   - 0000000000000030, ES  - 0000000000000030, FS  - 0000000000000030
> GS   - 0000000000000030, SS  - 0000000000000030
> CR0  - 0000000080000033, CR2 - 0000000000000000, CR3 - 000000001F3DB000
> CR4  - 0000000000000668, CR8 - 0000000000000000
> DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
> DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
> GDTR - 000000001F3C9A98 0000000000000047, LDTR - 0000000000000000
> IDTR - 000000001EB0A018 0000000000000FFF,   TR - 0000000000000000
> FXSAVE_STATE - 000000001F43C170
> !!!! Find PE image ./Build/OvmfX64/DEBUG_GCC5/X64/OvmfPkg/XenBusDxe/XenBusDxe/DEBUG/XenBusDxe.dll (ImageBase=000000001F266000, EntryPoint=000000001F2669D5) !!!!
> 
> I'll try to investigate, and report upstream.
> 
> -- 
> Anthony PERARD

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel

      reply	other threads:[~2016-11-28 15:03 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-11-25 13:24 [lersek@redhat.com: Re: [PATCH v3] OvmfPkg/build.sh: Make GCC5 the default toolchain, catch GCC43 and earlier] Konrad Rzeszutek Wilk
2016-11-25 13:51 ` Wei Liu
2016-11-25 17:04   ` Konrad Rzeszutek Wilk
2016-11-29  4:34     ` Wei Liu
2016-11-28 12:38 ` Anthony PERARD
2016-11-28 15:03   ` Konrad Rzeszutek Wilk [this message]

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=20161128150307.GC2304@localhost.localdomain \
    --to=konrad.wilk@oracle.com \
    --cc=anthony.perard@citrix.com \
    --cc=wei.liu2@citrix.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 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).