From: Laszlo Ersek <lersek@redhat.com>
To: Hristo Mihaylov <hristo.mihaylov@prodrive-technologies.com>,
"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>
Subject: Re: DxeIpl module cannot find DXE entry point
Date: Tue, 14 Aug 2018 15:17:35 +0200 [thread overview]
Message-ID: <eeab6c27-9836-ac9e-946a-63edb9206505@redhat.com> (raw)
In-Reply-To: <c98dc9df50b045a19439a255319a8d63@prodrive-technologies.com>
On 08/14/18 14:00, Hristo Mihaylov wrote:
> Hello, Laszlo,
>
> There is a PEIM that executes BuildFvHob with the FVMAIN_COMPACT address and size, the function also exits normally.
>
> The crash occurs here: https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/DxeIplPeim/DxeLoad.c#L469 and the platform uses UDK2015 packages.
> I also updated the DxeIpl module to the latest UDK release, but that didn't fix the issue.
>
> Now I'm trying two approaches:
>
> 1. to use a decompressed DXE and see if the issue was in the compression.
> 2. to enable source level debugging and track execution.
>
> Any idea what else it could be, besides the BuildFvHob function? Or a way to see if the HOB was built successfully.
Sorry, adding fine-grained debug messages (or source level debugging, as
you say) is my only thought at this point.
Laszlo
next prev parent reply other threads:[~2018-08-14 13:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-09 12:14 DxeIpl module cannot find DXE entry point Hristo Mihaylov
2018-08-09 16:40 ` Laszlo Ersek
[not found] ` <c98dc9df50b045a19439a255319a8d63@prodrive-technologies.com>
2018-08-14 13:17 ` Laszlo Ersek [this message]
[not found] ` <0C09AFA07DD0434D9E2A0C6AEB0483103BBAD3DE@shsmsx102.ccr.corp.intel.com>
2018-08-15 10:26 ` Laszlo Ersek
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-list 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=eeab6c27-9836-ac9e-946a-63edb9206505@redhat.com \
--to=devel@edk2.groups.io \
/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