All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Yinghai Lu <yinghai@kernel.org>
Cc: "Ozan Çağlayan" <ozan@pardus.org.tr>,
	"Thomas Gleixner" <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	linux-kernel@vger.kernel.org
Subject: Re: [BUG 2.6.29_rc8] BIOS Bug: CPU MTRRs don't cover all of memory, losing 0MB of RAM.
Date: Tue, 17 Mar 2009 10:43:32 +0100	[thread overview]
Message-ID: <20090317094332.GE6477@elte.hu> (raw)
In-Reply-To: <49BED813.1090405@kernel.org>


* Yinghai Lu <yinghai@kernel.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

  reply	other threads:[~2009-03-17  9:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-16 13:48 [BUG 2.6.29_rc8] BIOS Bug: CPU MTRRs don't cover all of memory, losing 0MB of RAM Ozan Çağlayan
2009-03-16 18:21 ` Yinghai Lu
2009-03-16 20:17   ` Ozan Çağlayan
2009-03-16 22:00     ` Yinghai Lu
2009-03-16 22:42       ` Ozan Çağlayan
2009-03-16 22:52         ` Yinghai Lu
2009-03-17  9:43           ` Ingo Molnar [this message]
2009-03-16 23:33         ` [PATCH] x86: workaround system with stange var MTRR -v2 Yinghai Lu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090317094332.GE6477@elte.hu \
    --to=mingo@elte.hu \
    --cc=akpm@linux-foundation.org \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ozan@pardus.org.tr \
    --cc=tglx@linutronix.de \
    --cc=yinghai@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.