XvMC on savage

[Dag Nygren]

> I have the same problem with the Savage chipset in my MythTV machine, also in
> the same Shuttle box as you.

Nice to hear that I am not alone.

> But from what I can tell there is no XvMC problem becuse there is no XvMC.
> Rather, in all the checking I have done it seems to be that Xv is broken.  The
> logs say it is fine and all the programs that need Xv get it, but, just as
> with your machine, the CPU load is at an unacceptable level.

It might well be that I have just though I have been using XvMC then, and the 
real problem now is that Xv is somehow messed up.

At the moment I am compiling Xorg from a git checkout, just to see if it
works any better.

> I'm running Debian and I had Xorg 6.8 or 6.9 under which everything worked
> fine.  When Debian/sid moved to X.org 7 I began to have these problems.

Yep, that is what I am seeing too. 

> I think it might possibly be the fault of bad mtrr settings?  I'm not sure.  I
> get several entries in the MTRR table after X starts:
> 
> reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
> reg01: base=0x1e000000 ( 480MB), size=  32MB: uncachable, count=1
> reg02: base=0xd8000000 (3456MB), size=  64MB: write-combining, count=2
> reg03: base=0xd0000000 (3328MB), size= 128MB: write-combining, count=3
> reg05: base=0xd8000000 (3456MB), size=  64MB: write-combining, count=1

Mine are as follows:
reg00: base=0x00000000 (   0MB), size= 512MB: write-back, count=1
reg01: base=0x1e000000 ( 480MB), size=  32MB: uncachable, count=1
reg02: base=0xe8000000 (3712MB), size=  64MB: write-combining, count=2
reg03: base=0xe8000000 (3712MB), size=  64MB: write-combining, count=1
reg04: base=0xe0000000 (3584MB), size=  32MB: write-combining, count=2
reg05: base=0xe6000000 (3680MB), size=  16MB: write-combining, count=1
reg06: base=0xe4000000 (3648MB), size=  32MB: write-combining, count=1
reg07: base=0xe2000000 (3616MB), size=  32MB: write-combining, count=1

The Display memory is at 0xe0000000 .

> And this error message appears in the console log four times:
> 
> mtrr: base(0xd2000000) is not aligned on a size(0x5000000) boundary

I also have this in the log, Seems to gladly allocate MTRR:s anyway.

Wait a minute, you might be right, there is a hole in there.

reg04 covering 0xe0000000 - 0xe1ffffff
reg07 covering 0xe2000000 - 0xe3ffffff
reg06 covering 0xe4000000 - 0xe5ffffff
reg05 covering 0xe6000000 - 0xe6ffffff
Hole for 0x70000000 - 0x7fffffff (!!)

Have you tried setting this manually?

Your MTRR:s look better though, provided that your board is located
at 0xd0000000

I will certainly do that tomorrow. Too late to try this evening.

Best
Dag