linux-kernel - Re: x86-32 PAE-enabled kernel fails to boot with 64GB of RAM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <4EDE5B36.2000203@kernel.org>
Date:	Tue, 06 Dec 2011 10:13:10 -0800
From:	"H. Peter Anvin" <hpa@...nel.org>
To:	Michal Hocko <mhocko@...e.cz>
CC:	Arnaud Lacombe <lacombar@...il.com>, x86@...nel.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: x86-32 PAE-enabled kernel fails to boot with 64GB of RAM

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/