linux-kernel - Re: [PATCH] trim memory not covered by WB MTRRs

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]

Date:	Thu, 14 Jun 2007 16:26:07 -0400 (EDT)
From:	Justin Piszcz <jpiszcz@...idpixels.com>
To:	Pim Zandbergen <P.Zandbergen@...roscoop.nl>
cc:	Jesse Barnes <jesse.barnes@...el.com>,
	Andi Kleen <andi@...stfloor.org>, linux-kernel@...r.kernel.org,
	"Eric W. Biederman" <ebiederm@...ssion.com>
Subject: Re: [PATCH] trim memory not covered by WB MTRRs

On Thu, 14 Jun 2007, Pim Zandbergen wrote:

> Thanks for this patch. I was having the exact same symptoms as Justin Piszcz, 
> on a different, but similar motherboard:
>
> Motherboard: GigaByte GA-G33-DS3R
> BIOS rev: F2
> Chipset: Intel G33
> Memory: 8GB
> Distro: Fedora 7 x86_64
> Kernel: kernel-2.6.21-1.3194.fc7
>
> Building vanilla 2.6.22-rc4 with your patch solved the problem.
>
> I'm now seeing this in the syslog
>
> ***************
> **** WARNING: likely BIOS bug
> **** MTRRs don't cover all of memory, trimmed 196608 pages
> ***************
>
> leaving me 7416672 kB of usable memory.
>
> If there's any way I can help with more info or testing,
> then let me know.
>
> Thanks,
> Pim
>

That's strange, I guess different chipsets 'chew' up different amounts of 
memory OR you have your DVT(?) (video-card memory/aperature) set to 256MB? 
I have mine set to 128MB, in top:

Mem:   8039576k total,  6187304k used,  1852272k free,      696k buffers

What type of memory are you using and what is your DVT set to?

Justin.
-
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/