linux-kernel - Re: memory beyond4GB invisible to the system even though CONFIG

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: <496FA083.3050304@kernel.org>
Date:	Thu, 15 Jan 2009 12:45:55 -0800
From:	Yinghai Lu <yinghai@...nel.org>
To:	James Kirin <james.kirin40@...il.com>
CC:	Roland Dreier <rdreier@...co.com>, linux-kernel@...r.kernel.org
Subject: Re: memory beyond4GB invisible to the system even though CONFIG_HIGHMEM64G=y

James Kirin wrote:
> I tried disabing CONFIG_MTRR_SANITIZER and CONFIG_X86_PAT in the
> kernel, and now a different kernel panic occurs:
> 
> [... ] Write protecting the kernel text: 3040k
> [...] Write protecting the kernel read-only data: 1352k
> [... ] khelper used greatest stack depth: 6724 bytes left
> [ ...] Kernel panic - not syncing: No init found. Try passing init=
> option to kernel.
> 
> Is an "init=" option necessary when using disable_mtrr_trim?

that is not related...

YH
--
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/