From: Matt Fleming <matt@console-pimps.org>
To: "Mantas Mikulėnas" <grawity@gmail.com>
Cc: Yinghai Lu <yinghai@kernel.org>,
Matt Fleming <matt.fleming@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-efi@vger.kernel.org
Subject: Re: Loading initrd above 4G causes freeze on boot
Date: Wed, 13 Aug 2014 19:44:49 +0100 [thread overview]
Message-ID: <20140813184449.GV15082@console-pimps.org> (raw)
In-Reply-To: <CAPWNY8WdA+Q+WjXirGOsrYjMGp+69sCqYa8ST7_owQeVhQkT0w@mail.gmail.com>
On Wed, 13 Aug, at 07:38:14PM, Mantas Mikulėnas wrote:
>
> Here you go.
>
> [ 0.000000] BIOS-e820: [mem 0x0000000100000000-0x0000000137ffffff] usable
[...]
> [ 0.000000] reserve setup_data: [mem 0x0000000100000000-0x0000000137ffffff] usable
[...]
> [ 0.000000] efi: mem201: type=7, attr=0xf, range=[0x0000000100000000-0x0000000138000000) (896MB)
Nothing crazy here, unless we're getting the calculation wrong and
reading past the buffer, the code looks OK though. Or something like the
last page or so of that memory isn't actually free even though the
firmware tells us it is.
At this point, I think modifying the max address is the best way to
debug this further, and figure out what address causes the hang.
--
Matt Fleming, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-08-13 18:44 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-09 14:23 Loading initrd above 4G causes freeze on boot Mantas Mikulėnas
2014-08-09 16:44 ` Yinghai Lu
2014-08-09 19:23 ` Matt Fleming
2014-08-09 22:45 ` Mantas Mikulėnas
2014-08-10 5:55 ` Yinghai Lu
2014-08-10 18:43 ` Mantas Mikulėnas
2014-08-13 14:02 ` Matt Fleming
2014-08-13 16:38 ` Mantas Mikulėnas
2014-08-13 18:44 ` Matt Fleming [this message]
2014-08-20 17:05 ` Matt Fleming
2014-08-20 19:05 ` Mantas Mikulėnas
2014-08-20 19:53 ` Michael Brown
2014-08-20 20:30 ` Matt Fleming
2014-08-21 20:23 ` [edk2] " Laszlo Ersek
2014-08-22 14:24 ` Harald Hoyer
2014-08-22 14:43 ` Mantas Mikulėnas
2014-08-24 19:19 ` Mantas Mikulėnas
2014-08-25 10:55 ` Matt Fleming
2014-08-25 11:08 ` Mantas Mikulėnas
2014-08-25 12:53 ` Matt Fleming
2014-08-25 18:22 ` Yinghai Lu
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=20140813184449.GV15082@console-pimps.org \
--to=matt@console-pimps.org \
--cc=grawity@gmail.com \
--cc=linux-efi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matt.fleming@intel.com \
--cc=yinghai@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