On Thu, Apr 16, 2009 at 19:51:52 +0200, J.H.M. Dassen (Ray) wrote:
> In dmesg, I've noticed the following, which may be related:
> [drm] MTRR allocation failed. Graphics performance may suffer.
Googling for this message led me to
http://linux.derkeiler.com/Mailing-Lists/Kernel/2009-04/msg09397.html
which suggests
CONFIG_MTRR_SANITIZER=y
CONFIG_MTRR_SANITIZER_ENABLE_DEFAULT=1
CONFIG_MTRR_SANITIZER_SPARE_REG_NR_DEFAULT=1
Unfortunately, this has not made any appreciable difference; the boot
messages still report
[drm] Initialized drm 1.1.0 20060810
pci 0000:00:02.0: PCI INT A -> GSI 16 (level, low) -> IRQ 16
pci 0000:00:02.0: setting latency timer to 64
mtrr: type mismatch for d0000000,10000000 old: write-back new:
write-combining
[drm] MTRR allocation failed. Graphics performance may suffer.
and the Xorg log still shows it going for EXA instead of UXA:
(II) intel(0): Integrated Graphics Chipset: Intel(R) G33
(--) intel(0): Chipset: "G33"
(--) intel(0): Linear framebuffer at 0xD0000000
(--) intel(0): IO registers at addr 0xE5600000
(WW) intel(0): libpciaccess reported 0 rom size, guessing 64kB
(==) intel(0): Using EXA for acceleration
For completeness, "cat /proc/mtrr" currently provides this map:
reg00: base=0x000000000 ( 0MB), size= 4096MB, count=1: write-back
reg01: base=0x0c0000000 ( 3072MB), size= 1024MB, count=1: uncachable
reg02: base=0x0bf800000 ( 3064MB), size= 8MB, count=1: uncachable
reg03: base=0x0bf700000 ( 3063MB), size= 1MB, count=1: uncachable
reg04: base=0x100000000 ( 4096MB), size= 1024MB, count=1: write-back
reg05: base=0x0bf600000 ( 3062MB), size= 1MB, count=1: write-through
Ray
--
Professionele hackers kunnen uw bedrijf veel schade berokkenen.
Snail-mail spam van het Nederlands Normalisatie-Instituut
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
