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: <86802c440901132207l433227d9nf149506012a5721e@mail.gmail.com>
Date:	Tue, 13 Jan 2009 22:07:26 -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

On Tue, Jan 13, 2009 at 7:10 PM, James Kirin <james.kirin40@...il.com> wrote:
> Thank you for your reply, Roland. Unfortunately, this continues
> happening after having installed the most recent version of the BIOS
> available from Dell.
>
> I understand this is a problem in the BIOS and not the kernel, but is
> there a way to have the kernel work around this bug in the BIOS and
> make that memory accessible? Eg,
>
> http://www.gossamer-threads.com/lists/linux/kernel/991748#991748

please do
1. boot linux with "disable_mtrr_trim" in grub.conf etc
2. after booting input:
echo "base=0x100000000 size=0x20000000 type=write-back" >/proc/mtrr

later you could put that line in one scripts and call it from inittab
# grep mtrrfixup /etc/inittab
mtrr:345:once:/root/mtrrfixup.sh

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/