public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: "memristor2 via groups.io" <memristor2=proton.me@groups.io>
To: "devel@edk2.groups.io" <devel@edk2.groups.io>
Subject: [edk2-devel] DxeSmmReadyToLockProtocol interface doesn't get installed
Date: Tue, 16 Apr 2024 12:51:40 +0000	[thread overview]
Message-ID: <iT5cR4KqRvncIE0QE5TQKbvA1D36ls4_IlyaG3lwoZYLrgGlQkM6-e0CrnxCTjhhVgtzejWkxFq6rVv8MdIoOTDKeIinovJpSXybfkiEeGM=@proton.me> (raw)

[-- Attachment #1: Type: text/plain, Size: 1322 bytes --]

Hello everyone,
I am developing a platform based on MinPlatformPkg everything works fine up until the BDS phase.
To be more specific what's happening is that inside the BdsDxe module when the BdsEntry function calls the platform-dependent "PlatformBootManagerBeforeConsole" function (Inside MinPlatformPkg) and eventually the ExitPmAuth() function, the execution seems to get stuck on this part of the code:
Handle = NULL;
Status = gBS->InstallProtocolInterface (
&Handle,
&gEfiDxeSmmReadyToLockProtocolGuid,
EFI_NATIVE_INTERFACE,
NULL );
I do not have a single clue why this is happening especially since it doesn't return and simply hangs. The only thing that would come to my mind would be that its dependencies aren't met which is not true in this case since other drivers also have this depex and get dispatched with no problem and if this was the case the module wouldn't even execute at the first place.
Any ideas are extremely appreciated.
Thanks,
Memristor

-=-=-=-=-=-=-=-=-=-=-=-
Groups.io Links: You receive all messages sent to this group.
View/Reply Online (#117879): https://edk2.groups.io/g/devel/message/117879
Mute This Topic: https://groups.io/mt/105555635/7686176
Group Owner: devel+owner@edk2.groups.io
Unsubscribe: https://edk2.groups.io/g/devel/unsub [rebecca@openfw.io]
-=-=-=-=-=-=-=-=-=-=-=-



[-- Attachment #2: Type: text/html, Size: 3364 bytes --]

                 reply	other threads:[~2024-04-16 12:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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='iT5cR4KqRvncIE0QE5TQKbvA1D36ls4_IlyaG3lwoZYLrgGlQkM6-e0CrnxCTjhhVgtzejWkxFq6rVv8MdIoOTDKeIinovJpSXybfkiEeGM=@proton.me' \
    --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