From: "H. Peter Anvin" <hpa@kernel.org>
To: Michal Hocko <mhocko@suse.cz>
Cc: Arnaud Lacombe <lacombar@gmail.com>,
x86@kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: x86-32 PAE-enabled kernel fails to boot with 64GB of RAM
Date: Tue, 06 Dec 2011 10:13:10 -0800 [thread overview]
Message-ID: <4EDE5B36.2000203@kernel.org> (raw)
In-Reply-To: <20111206102628.GC1342@tiehlicka.suse.cz>
On 12/06/2011 02:26 AM, Michal Hocko wrote:
>
> Quoting from Documentation/vm/highmem.txt:
> "
> The general recommendation is that you don't use more than 8GiB on a
> 32-bit machine - although more might work for you and your workload,
> you're pretty much on your own - don't expect kernel developers to
> really care much if things come apart.
> "
>
Still, I suspect the failure to cap the memory space... it still
*should* at least limp along. But yes, at some point the wheels really
will just come off the bus.
Does specifying a kernel"mem=" option (thereby capping the memory
artificially) work?
-hpa
next prev parent reply other threads:[~2011-12-06 18:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-06 7:23 x86-32 PAE-enabled kernel fails to boot with 64GB of RAM Arnaud Lacombe
2011-12-06 10:26 ` Michal Hocko
2011-12-06 18:13 ` H. Peter Anvin [this message]
2011-12-21 6:34 ` Yuhong Bao
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=4EDE5B36.2000203@kernel.org \
--to=hpa@kernel.org \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.cz \
--cc=x86@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