From: "Benjamin Doron" <benjamin.doron00@gmail.com>
To: devel@edk2.groups.io
Subject: Possible [BUG] PeiCore: HOBs after cache-as-RAM teardown
Date: Tue, 06 Jul 2021 22:55:20 -0700 [thread overview]
Message-ID: <Bmt0.1625637320930212739.KZH2@groups.io> (raw)
[-- Attachment #1: Type: text/plain, Size: 1403 bytes --]
Hi all,
I'm working on root-causing an issue where I'm unable to retrieve any debug logs after cache-as-RAM teardown on my MinPlatform board port for GSoC 2021. I'm using KabylakeOpenBoardPkg/PeiSerialPortLibSpiFlash.
My best guess at the moment is that it's related to HOBs, which this SerialPortLib uses. If I reinitialise the library stack, it largely works, but a HOB/context structure entry "CurrentWriteOffset" also looks like it's zeroed.
Also, GetFeatureImplemented() in MinPlatformPkg/Test/TestPointCheckLib/PeiTestPointCheckLib.c asserts with "Status = Not Found". Internally, the test point architecture uses HOBs. I don't think this should happen, so, if not for this, I would think that perhaps a pointer in the serial port library needed to be updated.
I can see that the heap is copied over to permanent memory by the PEI core dispatcher ( https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Pei/Dispatcher/Dispatcher.c#L881 ). However, I can't see that the HOB list pointer is updated, so it looks like it ( https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Pei/Hob/Hob.c#L44 ) still has the value that's copied over from the old PEI core's data ( https://github.com/tianocore/edk2/blob/master/MdeModulePkg/Core/Pei/PeiMain/PeiMain.c#L348 ).
Does this look like a bug, or might there be something else that I'm missing?
Best regards,
Benjamin
[-- Attachment #2: Type: text/html, Size: 1850 bytes --]
next reply other threads:[~2021-07-07 5:55 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 5:55 Benjamin Doron [this message]
2021-07-08 21:12 ` [edk2-devel] Possible [BUG] PeiCore: HOBs after cache-as-RAM teardown Michael Kubacki
2021-07-13 7:25 ` Benjamin Doron
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=Bmt0.1625637320930212739.KZH2@groups.io \
--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