From: David Holloway <daveh@dholloway.com>
To: daveh@dholloway.com
Cc: grub-devel@gnu.org
Subject: Re: grub EFI "too little memory"
Date: Tue, 17 Jun 2008 01:58:16 -0700 [thread overview]
Message-ID: <48577CA8.5000604@dholloway.com> (raw)
In-Reply-To: <48576165.1000002@dholloway.com>
David Holloway wrote:
> Intended for Robert Millan, et. al.
>
> I have an Intel 1U server board that fails with the current version of
> grub with the message "too little memory", as in line 312 of CVS
> version 1.4 of grub2/kern/efi/mm.c
> The board is described here:
> http://www.intel.com/design/telecom/products/cbp/ipserver/9979/overview.htm
>
>
> I added some debug and I think "required_pages" at line 312 has a
> value of 1MB (256 pages), consistent with MIN_HEAP.
> mmap from the EFI shell reports just 38 pages of LoaderData and just
> 196 pages of LoaderCode.
>
> It's my intention to bone up on EFI, but I'm not there yet.
>
> The question: does just 38 pages of LoaderData make sense in this
> implemetation? is MIN_HEAP too large or does this EFI implementation
> provide too little memory to be practical?
I diagnosed the root problem.
The NSW1U board requires 7872 bytes for its memory map during the EFI
GetMemoryMap call, but only 4096 are supplied.
Obviously my short term solution is to increase MEMORY_MAP_SIZE from
0x1000 to 0x2000, but one wonders what the robust solution should be
instead. In fact, I now have the NSW1U server board working after this
change.
I'm now filing a bug report on the matter.
https://savannah.gnu.org/bugs/index.php?23615
next prev parent reply other threads:[~2008-06-17 8:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200806170307.m5H37DjU073382@shoebox.dholloway.com>
2008-06-17 7:01 ` grub EFI "too little memory" David Holloway
2008-06-17 8:52 ` Bean
2008-06-17 8:58 ` David Holloway [this message]
2008-06-17 13:26 ` Andrei E. Warkentin
2008-06-17 17:22 ` David Holloway
2008-06-17 19:09 ` Andrei E. Warkentin
2008-06-17 12:35 ` Robert Millan
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=48577CA8.5000604@dholloway.com \
--to=daveh@dholloway.com \
--cc=grub-devel@gnu.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.