From: Jim McCloskey <mcclosk@ucsc.edu>
To: linux-kernel@vger.kernel.org
Subject: 2.6.10 solves mtrr problem
Date: Mon, 27 Dec 2004 21:29:15 -0800 [thread overview]
Message-ID: <20041228052915.GA9330@lapdog> (raw)
Probably well known already to the knowledgeable, but I just wanted to
report that 2.6.10 fixes a problem that I have been puzzled by since
about 2.6.7.
The problem was that mtrr ranges were not set appropriately for
the graphics card on my laptop, which is a:
----------------------------------------------------------------------
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon Mobility M6 LY (prog-if 00 [VGA])
Subsystem: Mitac: Unknown device 8170
Flags: bus master, stepping, 66MHz, medium devsel, latency 64, IRQ 11
Memory at 90000000 (32-bit, prefetchable) [size=128M]
I/O ports at c000 [size=256]
Memory at e0000000 (32-bit, non-prefetchable) [size=64K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2
----------------------------------------------------------------------
The problem was indicated in kern.log for 2.6.9:
----------------------------------------------------------------------
Dec 14 10:31:19 lapdog kernel: mtrr: 0x90000000,0x1000000 overlaps existing 0x90000000,0x200000
----------------------------------------------------------------------
which resulted in turn in the following, when the X server was started:
----------------------------------------------------------------------
(--) RADEON(0): Linear framebuffer at 0x90000000
(--) RADEON(0): VideoRAM: 16384 kByte (64 bit DDR SDRAM)
(II) RADEON(0): AGP card detected
.....
(WW) RADEON(0): Failed to set up write-combining range (0x90000000,0x1000000)
----------------------------------------------------------------------
This problem has disappeared in 2.6.10. /proc/mtrr:
----------------------------------------------------------------------
reg00: base=0x00000000 ( 0MB), size= 512MB: write-back, count=1
reg01: base=0x90000000 (2304MB), size= 16MB: write-combining, count=3
reg02: base=0xa0000000 (2560MB), size= 64MB: write-combining, count=1
----------------------------------------------------------------------
For previous 2.6 kernels, I had to run a hand-written script to
achieve this result.
Thank you,
Jim
----------------------------------------------------------------------
cat /proc/cpuinfo
processor : 0
vendor_id : GenuineIntel
cpu family : 15
model : 2
model name : Intel(R) Pentium(R) 4 CPU 1.60GHz
stepping : 4
cpu MHz : 1600.489
cache size : 512 KB
fdiv_bug : no
hlt_bug : no
f00f_bug : no
coma_bug : no
fpu : yes
fpu_exception : yes
cpuid level : 2
wp : yes
flags : fpu vme de pse tsc msr pae mce cx8 sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm
bogomips : 3153.92
======================================================================
reply other threads:[~2004-12-28 5:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20041228052915.GA9330@lapdog \
--to=mcclosk@ucsc.edu \
--cc=linux-kernel@vger.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox