I have a Red Hat Linux 9 and receiving next message in XFree86 Log:
(ww) ATI (0): Failed to set up write-combining range (0xf6000000, 0x800000).

What's the problem?

Michael S. Androsov
EXPOCENTR

[ Post a follow-up to this message ]

androsov@expocentr.ru (Michael S. Androsov) writes:[vbcol=seagreen]
>I have a Red Hat Linux 9 and receiving next message in XFree86 Log:
>(ww) ATI (0): Failed to set up write-combining range (0xf6000000, 0x800000).[/vbcol
]

What kind of processor?   XFree86 uses the MTRR registers to set the
video aperture memory to "write combining" type.  This allows the processor
to combine multiple writes before pushing the cache-line back to the
video processor.

This can happen generally because (1) your CPU doesn't support MTRR's  or
(2) all the available MTRR's are already used for other purposes (which
situation can arise when for example there are multiple discontigous
ranges of physical memory).  On linux, you can look at /proc/mtrr to
see the current usage.

$ cat /proc/mtrr
reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg02: base=0xec000000 (3776MB), size=  64MB: write-combining, count=1
$

If your CPU doesn't support the MTRR, performance may degrade somewhat, but
functionally things should still be fine.

scott

[ Post a follow-up to this message ]

My processor is Intel Pentium 4 (two processors in server). Follow is
output of cat command:
eg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
reg01: base=0x400020000 (16384MB), size=  64KB: uncachable, count=1
reg02: base=0x400040000 (16384MB), size=  64KB: uncachable, count=1
reg03: base=0x400060000 (16384MB), size=  64KB: uncachable, count=1
reg04: base=0x400080000 (16384MB), size=  64KB: uncachable, count=1
reg05: base=0x4000a0000 (16384MB), size=  64KB: uncachable, count=1
reg06: base=0x4000c0000 (16384MB), size=  64KB: uncachable, count=1
reg07: base=0x4000e0000 (16384MB), size=  64KB: uncachable, count=1

Michael S. Androsov
EXPOCENTR



scott@slp53.sl.home (Scott Lurndal) wrote in message news:<Jsi6d.3931$nj.2793@newssvr13.news
.prodigy.com>...
> androsov@expocentr.ru (Michael S. Androsov) writes: 
>
> What kind of processor?   XFree86 uses the MTRR registers to set the
> video aperture memory to "write combining" type.  This allows the processo
r
> to combine multiple writes before pushing the cache-line back to the
> video processor.
>
> This can happen generally because (1) your CPU doesn't support MTRR's  or
> (2) all the available MTRR's are already used for other purposes (which
> situation can arise when for example there are multiple discontigous
> ranges of physical memory).  On linux, you can look at /proc/mtrr to
> see the current usage.
>
> $ cat /proc/mtrr
> reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
> reg02: base=0xec000000 (3776MB), size=  64MB: write-combining, count=1
> $
>
> If your CPU doesn't support the MTRR, performance may degrade somewhat, bu
t
> functionally things should still be fine.
>
> scott

[ Post a follow-up to this message ]

androsov@expocentr.ru (Michael S. Androsov) writes:
>My processor is Intel Pentium 4 (two processors in server). Follow is
>output of cat command:
>eg00: base=0x00000000 (   0MB), size=2048MB: write-back, count=1
>reg01: base=0x400020000 (16384MB), size=  64KB: uncachable, count=1
>reg02: base=0x400040000 (16384MB), size=  64KB: uncachable, count=1
>reg03: base=0x400060000 (16384MB), size=  64KB: uncachable, count=1
>reg04: base=0x400080000 (16384MB), size=  64KB: uncachable, count=1
>reg05: base=0x4000a0000 (16384MB), size=  64KB: uncachable, count=1
>reg06: base=0x4000c0000 (16384MB), size=  64KB: uncachable, count=1
>reg07: base=0x4000e0000 (16384MB), size=  64KB: uncachable, count=1
>
>Michael S. Androsov
>EXPOCENTR

Strassvichya.

Something else  on your system is using all of the
MTRR registers.   (Note that regs 1-7 contain mappings to 64k
chunks of memory starting at 2GB.  It appear that these are mapped
every 128k.   Do you have some custom hardware on this system?
These are rather unusual mappings.

There are only 8 registers, so when X.org/XF86 tries to set up
a write-combining region for the AGP aperature, it fails.  The
only consequence of that failure will be reduced graphics performance.

scott

[ Post a follow-up to this message ]

Hello!
My server is Compaq (HP) ProLiant DL380 with 2 GB RAM and hardware
RAID 5X72 Gb. This server is file server. I'm stopped other services.
Some personnels access to this server across SSH telnet session. Rest
users access this server with Samba service.
That's all about this server.

Michael S. Androsov
EXPOCENTR


scott@slp53.sl.home (Scott Lurndal) wrote in message news:<HCBbd.13139$nj.206@newssvr13.news
.prodigy.com>...
> androsov@expocentr.ru (Michael S. Androsov) writes: 
>
> Strassvichya.
>
>   Something else  on your system is using all of the
> MTRR registers.   (Note that regs 1-7 contain mappings to 64k
> chunks of memory starting at 2GB.  It appear that these are mapped
> every 128k.   Do you have some custom hardware on this system?
> These are rather unusual mappings.
>
> There are only 8 registers, so when X.org/XF86 tries to set up
> a write-combining region for the AGP aperature, it fails.  The
> only consequence of that failure will be reduced graphics performance.
>
> scott

[ Post a follow-up to this message ]