public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mick <michaelkintzios@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] dmesg warning about mtrr: type mismatch and allocation failed
Date: Thu, 19 Aug 2010 22:32:17 +0100	[thread overview]
Message-ID: <201008192232.27024.michaelkintzios@gmail.com> (raw)
In-Reply-To: <4C6D4412.6010800@gmail.com>

[-- Attachment #1: Type: Text/Plain, Size: 2644 bytes --]

On Thursday 19 August 2010 15:47:46 Bill Longman wrote:
> On 08/19/2010 04:37 AM, Walter Dnes wrote:
> > On Mon, Aug 16, 2010 at 05:55:04PM -0500, Paul Hartman wrote
> > 
> >> I had a similar message, it was there because of the fact that i
> >> specified the wrong (or failed to specify?) mtrr method in my kernel
> >> boot parameters for the framebuffer. I'm using uvesafb and in kernel
> >> documentation (/usr/src/linux/Documentation/fb/uvesafb.txt) it
> >> explains the values and even gives an example of this error and what
> >> 
> >> to do about it:
> >   I'm using the Intel driver, which doesn't have those settings.  And
> > 
> > no, I do not want to drop down to a generic VESA driver with no hardware
> > acceleration.  Some more Google searching has turned up a lead.
> > Apparently, it's possible to manually set the mtrr's, using cat and echo
> > with /proc/mtrr
> > 
> >   According to "lspci -v", my integrated graphics chip has
> >   
> >         Memory at fb800000 (64-bit, non-prefetchable) [size=4M]
> >         Memory at d0000000 (64-bit, prefetchable) [size=256M]
> >   
> >   My mtrr setup, however, shows up like so...
> > 
> > waltdnes@i3 ~ $ cat /proc/mtrr
> > reg00: base=0x000000000 (    0MB), size= 8192MB, count=1: write-back
> > reg01: base=0x200000000 ( 8192MB), size= 1024MB, count=1: write-back
> > reg02: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
> > reg03: base=0x0b4000000 ( 2880MB), size=   64MB, count=1: uncachable
> > reg04: base=0x0b8000000 ( 2944MB), size=  128MB, count=1: uncachable
> > reg05: base=0x1fc000000 ( 8128MB), size=   64MB, count=1: uncachable
> > 
> >   I'll read up more on how to set it up manually.  One thing that has my
> > 
> > curiousity right now... how come there's a gig of ram in write-back mode
> > *STARTING* at 8 gigs, and ending at 9 gigs minus 1 byte, when I only
> > have 8 gigs of ram in total?
> 
> You might want to have a look in your kernel Documentation directory.
> There's a file x86/mtrr.txt that gives you some info. And lots in the fb
> subdirectory. You can probably find some other info there, too. There's
> lots of the dreaded MTRR info in the kernel_parameters.txt file, so you
> can setup the MTRRs at boot time.

I've read as much as I could find, but the whole hexadecimal thing has me 
overwhelmed  O_O

I think my mtrr is OK, but I do not understand this enough to know if it would 
benefit from manual configuration.

Walter please break it into small change for me when you sort out yours - you 
could contact me off list if this is getting too O/T.
-- 
Regards,
Mick

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2010-08-19 21:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-15 23:27 [gentoo-user] dmesg warning about mtrr: type mismatch and allocation failed Walter Dnes
2010-08-16 22:28 ` [gentoo-user] " walt
2010-08-17  2:48   ` Walter Dnes
2010-08-16 22:55 ` [gentoo-user] " Paul Hartman
2010-08-19 11:37   ` Walter Dnes
2010-08-19 14:47     ` Bill Longman
2010-08-19 21:32       ` Mick [this message]
2010-08-19 21:43         ` Paul Hartman
2010-08-19 23:24           ` Peter Humphrey

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=201008192232.27024.michaelkintzios@gmail.com \
    --to=michaelkintzios@gmail.com \
    --cc=gentoo-user@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox