From: "Víctor Gonzalo" <victor.gonzalo@anddroptable.net>
To: linux-efi@vger.kernel.org
Subject: Increasing EFI_MMAP_NR_SLACK_SLOTS
Date: Fri, 3 Sep 2021 01:26:41 +0300 [thread overview]
Message-ID: <CAGRPHE+Jn4UAV3THuK6nwF4G0R5LxT2EhQndTUqw8fOPMjWZPw@mail.gmail.com> (raw)
Hello
I had an issue in a big server in which no linux distro I tried was
able to boot. It failed with the messages:
EFI stub: ERROR: exit_boot() failed!
EFI stub: ERROR: efi_main() failed!
Digging through the rabbit hole I reached the error in the call to
efi_bs_call(get_memory_map) inside efi_exit_boot_services() in
efi-stub-helper.c which returned EFI_BUFFER_TOO_SMALL, so everything
collapsed after that.
It looks like despite what the comment suggests, the headroom was not enough.
I fixed it by increasing the value of EFI_MMAP_NR_SLACK_SLOTS to 16.
Is this the right approach to fix the issue?
Would it be ok to change the value in the mainline?
Thanks
- Víctor
next reply other threads:[~2021-09-02 22:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-02 22:26 Víctor Gonzalo [this message]
2022-04-13 17:38 ` Increasing EFI_MMAP_NR_SLACK_SLOTS Ard Biesheuvel
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=CAGRPHE+Jn4UAV3THuK6nwF4G0R5LxT2EhQndTUqw8fOPMjWZPw@mail.gmail.com \
--to=victor.gonzalo@anddroptable.net \
--cc=linux-efi@vger.kernel.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 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).