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] [day] [month] [year] [list]
Message-ID: <20090317094332.GE6477@elte.hu>
Date:	Tue, 17 Mar 2009 10:43:32 +0100
From:	Ingo Molnar <mingo@...e.hu>
To:	Yinghai Lu <yinghai@...nel.org>
Cc:	Ozan Çağlayan <ozan@...dus.org.tr>,
	Thomas Gleixner <tglx@...utronix.de>,
	"H. Peter Anvin" <hpa@...or.com>,
	Andrew Morton <akpm@...ux-foundation.org>,
	linux-kernel@...r.kernel.org
Subject: Re: [BUG 2.6.29_rc8] BIOS Bug: CPU MTRRs don't cover all of
	memory, losing 0MB of RAM.


* Yinghai Lu <yinghai@...nel.org> wrote:

> > x86 PAT enabled: cpu 0, old 0x7040600070406, new 0x7010600070106
> >   get_mtrr: cpu0 reg00 base=0000000000 size=0010000000 write-back
> >   get_mtrr: cpu0 reg01 base=00000cff00 size=0000000100 uncachable
> >   get_mtrr: cpu0 reg02 base=00000d0000 size=0000010000 uncachable
> >   get_mtrr: cpu0 reg03 base=00000e0000 size=0000020000 uncachable
> >   get_mtrr: cpu0 reg04 base=0000000004 size=0000000001 uncachable
> >   get_mtrr: cpu0 reg05 base=0000000005 size=0000000001 uncachable
> >   get_mtrr: cpu0 reg06 base=0000000006 size=0000000001 uncachable
> >   get_mtrr: cpu0 reg07 base=0000000007 size=0000000001 uncachable
> > WARNING: BIOS bug: VAR MTRR contains strange UC entry under 1M, check with your system vendor!
> > WARNING: BIOS bug: VAR MTRR contains strange UC entry under 1M, check with your system vendor!
> > WARNING: BIOS bug: VAR MTRR contains strange UC entry under 1M, check with your system vendor!
> > WARNING: BIOS bug: VAR MTRR contains strange UC entry under 1M, check with your system vendor!
> 
> you got four wrong entries

but it's unintuitive. That warning should specify which entry is 
wrong, so that we dont get these pointless duplicated lines.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ