All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony PERARD <anthony.perard@citrix.com>
To: Konrad Rzeszutek Wilk <konrad@kernel.org>
Cc: xen-devel@lists.xenproject.org, daniel.kiper@oracle.com,
	wei.liu2@citrix.com
Subject: Re: OVMF blows up at unless I use pci_platform=0
Date: Mon, 20 Feb 2017 15:49:31 +0000	[thread overview]
Message-ID: <20170220154931.GA1867@perard.uk.xensource.com> (raw)
In-Reply-To: <20170216013743.GA6603@dhcp-amer-vpn-adc-anyconnect-10-154-139-165.vpn.oracle.com>

On Wed, Feb 15, 2017 at 08:37:44PM -0500, Konrad Rzeszutek Wilk wrote:
> Hey,
> 
> I just built today Xen based on  93e1435290867703c50acad1f54b9208df473562
> Author: Oleksandr Tyshchenko <olekstysh@gmail.com>
> Date:   Wed Feb 15 12:20:01 2017 +0000
> 
>     IOMMU: always call teardown callback
> 
[...]
> #xl create -c root-image-uefi.xm
> I get:
> 
> !!!! X64 Exception Type - 0E(#PF - Page-Fault)  CPU Apic ID - 00000000 !!!!
> RIP  - 000000003F2658DB, CS  - 0000000000000038, RFLAGS - 0000000000010206
> ExceptionData - 0000000000000002
> RAX  - 0000000000000001, RCX - 000000003F2658BB, RDX - 0000000000000004
> RBX  - 0000000000000000, RSP - 000000003F43B510, RBP - 000000003E574D18
> RSI  - 0000000000000003, RDI - 0000000000000001
> R8   - 0000000000000000, R9  - 0000000000000000, R10 - 000000003EA39198
> R11  - 0000000000000002, R12 - 000000003E575218, R13 - 0000000000000000
> R14  - 000000003E575220, R15 - 000000003F269301
> DS   - 0000000000000030, ES  - 0000000000000030, FS  - 0000000000000030
> GS   - 0000000000000030, SS  - 0000000000000030
> CR0  - 00000000C0000033, CR2 - FFFFFFFFBF2658BB, CR3 - 000000003F3DA000
> CR4  - 0000000000000668, CR8 - 0000000000000000
> DR0  - 0000000000000000, DR1 - 0000000000000000, DR2 - 0000000000000000
> DR3  - 0000000000000000, DR6 - 00000000FFFF0FF0, DR7 - 0000000000000400
> GDTR - 000000003F3C8A98 0000000000000047, LDTR - 0000000000000000
> IDTR - 000000003EAFD018 0000000000000FFF,   TR - 0000000000000000
> FXSAVE_STATE - 000000003F43B170
> !!!! Find PE image /home/konrad/xen/tools/firmware/ovmf-dir-remote/Build/OvmfX64/DEBUG_GCC5/X64/OvmfPkg/XenBusDxe/XenBusDxe/DEBUG/XenBusDxe.dll (ImageBase=000000003F262000, EntryPoint=000000003F263FE8) !!!!

Which version of gcc did you compile OVMF with?

I can reproduce with a "Page-Fault" in the same modules, but with an OVMF
binary compiled later, I have a "General Protection" fault in the module
PcRtc...

I blame -flto of gcc.

If you have gcc 6.3, to build ovmf without -flto, either:
- build using OvmfPkg/build.sh -a X64 -n 4 -t GCC49
    (that is "-t GCC49" added to ./build.sh call)
- or edit OvmfPkg/build.sh, replace GCC5 by GCC49.

I can try to find out what is wrong, and report it upstream.

-- 
Anthony PERARD

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

  reply	other threads:[~2017-02-20 15:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-16  1:37 OVMF blows up at unless I use pci_platform=0 Konrad Rzeszutek Wilk
2017-02-20 15:49 ` Anthony PERARD [this message]
2017-02-27 17:42   ` Konrad Rzeszutek Wilk
2017-02-27 18:13     ` Anthony PERARD

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=20170220154931.GA1867@perard.uk.xensource.com \
    --to=anthony.perard@citrix.com \
    --cc=daniel.kiper@oracle.com \
    --cc=konrad@kernel.org \
    --cc=wei.liu2@citrix.com \
    --cc=xen-devel@lists.xenproject.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.