All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@infradead.org>
To: Robert Hancock <hancockr@shaw.ca>
Cc: linux-kernel@vger.kernel.org, torvalds@linux-foundation.org,
	akpm@linux-foundation.org, x86@kernel.org,
	netdev@vger.kernel.org, tytso@mit.edu, eric@anholt.net,
	airlied@redhat.com
Subject: Re: Bug/Warning report for the week of January 3rd, 2009
Date: Sat, 3 Jan 2009 16:20:00 -0800	[thread overview]
Message-ID: <20090103162000.138943b3@infradead.org> (raw)
In-Reply-To: <495FF769.3040205@shaw.ca>

On Sat, 03 Jan 2009 17:40:25 -0600
Robert Hancock <hancockr@shaw.ca> wrote:

> Arjan van de Ven wrote:
> > Rank 2: mtrr_trim_uncached_memory (warning)
> > 	Reported 420 times (9816 total reports)
> > 	BIOS bug (often in VMWare) where the MTRR's are set up
> > incorrectly or not at all This warning was last seen in version
> > 2.6.28, and first seen in 2.6.24. More info:
> > http://www.kerneloops.org/searchweek.php?search=mtrr_trim_uncached_memory
> 
> It would be useful if this warning dumped out some DMI BIOS
> information or something, so we could see what systems/boards this
> was commonly happening with.. 

yes it would; this is why Linus merged a patch to do exactly that for
2.6.29..........



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org

      reply	other threads:[~2009-01-04  0:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-03 22:03 Bug/Warning report for the week of January 3rd, 2009 Arjan van de Ven
2009-01-03 23:40 ` Robert Hancock
2009-01-04  0:20   ` Arjan van de Ven [this message]

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=20090103162000.138943b3@infradead.org \
    --to=arjan@infradead.org \
    --cc=airlied@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=eric@anholt.net \
    --cc=hancockr@shaw.ca \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=tytso@mit.edu \
    --cc=x86@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.