From: yhlu <yinghailu@gmail.com>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Horms <horms@verge.net.au>,
"Fastboot mailing list" <fastboot@lists.osdl.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Fastboot] Kexec with latest kernel fail
Date: Thu, 9 Nov 2006 23:30:22 -0800 [thread overview]
Message-ID: <2ea3fae10611092330q551127e0oad87775964fe7251@mail.gmail.com> (raw)
In-Reply-To: <m164dnnaac.fsf@ebiederm.dsl.xmission.com>
I found the cause before your mail.
the /proc/iomem doesn't show RAM above 1M.
I have increased linuxbios table at high 0xf0000-0xf0400 to
0xf0000-0x100000. the RAM above 1M show up.
I think root cause in the latest kernel 2.6.19, e820 align increase to 0xffff.
and when it check 0xf0000-0xf0400, will make 0xf0000-0x100000
reserved, and then when it check 0xf0400-4G, it will fail to reserved
System RAM above 1M.
I will check arch/x86_64/kernel/e820.c about
void __init e820_reserve_resources(void)
tommorrow.
YH
next prev parent reply other threads:[~2006-11-10 7:30 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-10 1:41 [Fastboot] Kexec with latest kernel fail Lu, Yinghai
2006-11-10 5:24 ` Eric W. Biederman
2006-11-10 7:30 ` yhlu [this message]
2006-11-10 9:18 ` Yinghai Lu
-- strict thread matches above, loose matches on Subject: below --
2006-11-10 20:01 Lu, Yinghai
2006-11-10 1:12 Lu, Yinghai
2006-11-10 1:27 ` Horms
2006-11-09 4:07 Lu, Yinghai
2006-11-09 5:48 ` [Fastboot] " Horms
2006-11-09 6:03 ` yhlu
2006-11-09 6:04 ` yhlu
2006-11-09 6:21 ` Horms
2006-11-09 7:36 ` Yinghai Lu
2006-11-10 0:47 ` Horms
2006-11-09 16:39 ` Don Zickus
2006-11-09 17:05 ` Yinghai Lu
2006-11-09 20:06 ` Jay Lan
2006-11-09 20:11 ` Vivek Goyal
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=2ea3fae10611092330q551127e0oad87775964fe7251@mail.gmail.com \
--to=yinghailu@gmail.com \
--cc=ebiederm@xmission.com \
--cc=fastboot@lists.osdl.org \
--cc=horms@verge.net.au \
--cc=linux-kernel@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