public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Marco Matthies <marco-ml@gmx.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: mtrr: base is not aligned
Date: Mon, 17 Oct 2005 02:18:06 +0200	[thread overview]
Message-ID: <4352EDBE.7030503@gmx.net> (raw)
In-Reply-To: <5bdc1c8b0510161150r27a36415pf435d4f9ab6ea638@mail.gmail.com>

Hi,

i'm not an expert on this subject myself but i found it nonetheless 
interesting, here's what i found mostly by grepping and googling:

Here's someone who is also getting these huge reported memory sizes:
http://lkml.org/lkml/2005/9/12/35
Found it by googling for 983552MB, there's more there.

There's is some info on mtrr's with vesafb here:
/usr/src/linux-2.6.13-gentoo-r3/Documentation/fb/vesafb.txt, line 176
Seems to suggest trying video=vesafb:nomtrr if you're using vesafb.

Also some other reports seem to hint at Xorg as the culprit:
https://bugs.freedesktop.org/show_bug.cgi?id=4310
and others found by googling "mtrr: type mismatch for".

You might want to also grep Xorg.log for the addresses provided by
'cat /proc/mtrr' or just the prefix such as
'grep -in 0xd /var/log/Xorg.0.log' in my case, that should some results 
(Xorg.log doesn't seem to mention mtrr literally, as far as i can see).

I'm sorry that I don't have an answer to the actual problem, but I'm 
very thankful for the interesting explanations about mtrr from both of 
you (Duncan and Mark).

Cheers,
Marco
-- 
gentoo-amd64@gentoo.org mailing list



  reply	other threads:[~2005-10-17  0:17 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-15 18:18 [gentoo-amd64] mtrr: base is not aligned Mark Knecht
2005-10-16 17:26 ` [gentoo-amd64] " Duncan
2005-10-16 18:50   ` Mark Knecht
2005-10-17  0:18     ` Marco Matthies [this message]
2005-10-17 11:45       ` [gentoo-amd64] " Duncan
2005-10-17 12:13         ` [gentoo-amd64] Merged Framebuffer Sebastian Redl
2005-10-17 14:17           ` [gentoo-amd64] " Duncan

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=4352EDBE.7030503@gmx.net \
    --to=marco-ml@gmx.net \
    --cc=gentoo-amd64@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