From: "Sebastian Kärgel" <mailing@wodkahexe.de>
To: Sebastian Kemper <sebastian_ml@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Radeon DRI, mtrr overlaps, wrong RAM value
Date: Tue, 24 Oct 2006 19:01:04 +0200 [thread overview]
Message-ID: <20061024190104.58d6b964.mailing@wodkahexe.de> (raw)
In-Reply-To: <20061015013824.GA26893@section_eight>
Hi,
> I get the following warnings once my X server starts:
>
> mtrr: 0xd0000000,0x10000000 overlaps existing 0xd0000000,0x8000000
> mtrr: 0xd0000000,0x10000000 overlaps existing 0xd0000000,0x8000000
> mtrr: 0xd0000000,0x10000000 overlaps existing 0xd0000000,0x8000000
> mtrr: 0xd0000000,0x10000000 overlaps existing 0xd0000000,0x8000000
> mtrr: 0xd0000000,0x10000000 overlaps existing 0xd0000000,0x8000000
Same here:
mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000
mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000
mtrr: 0xd0000000,0x8000000 overlaps existing 0xd0000000,0x4000000
> In Xorg.0.log I get these warnings:
>
> (WW) RADEON(0): DRI init changed memory map, adjusting ...
> (WW) RADEON(0): MC_FB_LOCATION was: 0xd7ffd000 is: 0xd7ffd000
> (WW) RADEON(0): MC_AGP_LOCATION was: 0xffffffc0 is: 0xe07fe000
> (**) RADEON(0): GRPH_BUFFER_CNTL from 20205c5c to 203e5c5c
XOrg Version: 6.8.2: No such messages here.
> /proc/mtrr holds these values:
> reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
> reg01: base=0xe0000000 (3584MB), size= 32MB: write-combining, count=2
> reg02: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=1
reg00: base=0x00000000 ( 0MB), size=1024MB: write-back, count=1
reg01: base=0xd0000000 (3328MB), size= 64MB: write-combining, count=1
reg05: base=0xe0000000 (3584MB), size= 128MB: write-combining, count=2
Kernel: 2.6.18.1
take care,
sebastian
prev parent reply other threads:[~2006-10-24 17:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-15 1:38 Radeon DRI, mtrr overlaps, wrong RAM value Sebastian Kemper
2006-10-24 17:01 ` Sebastian Kärgel [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=20061024190104.58d6b964.mailing@wodkahexe.de \
--to=mailing@wodkahexe.de \
--cc=linux-kernel@vger.kernel.org \
--cc=sebastian_ml@gmx.net \
/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