Does your X driver have commit f59c3b294b0f715fc96e2bbe25893f2b31aa488b ('Register XvMC video decoding acceleration') required for XvMC?

(In reply to comment #1)
> Does your X driver have commit f59c3b294b0f715fc96e2bbe25893f2b31aa488b
> ('Register XvMC video decoding acceleration') required for XvMC?

Yes:

[    54.139] (II)         Solid
[    54.139] (II)         Copy
[    54.139] (II)         Composite (RENDER acceleration)
[    54.139] (II)         UploadToScreen
[    54.139] (II)         DownloadFromScreen
[    54.140] (II) RADEON(0): Acceleration enabled
[    54.140] (**) RADEON(0): DPMS enabled
[    54.140] (==) RADEON(0): Silken mouse enabled
[    54.169] (II) RADEON(0): Set up textured video
[    54.169] (II) RADEON(0): [XvMC] Associated with Radeon Textured Video.
[    54.170] (II) RADEON(0): [XvMC] Extension initialized.

The latest commit in my X driver is:

commit 104b2d7c071f29266b1bc4184a74e9714d14febc
Author: Alex Deucher <alexander.deucher@amd.com>
Date:   Mon Aug 1 10:05:30 2011 -0400

    kms: fix possible leak in pageflip code

Does adding

 -vc ffmpeg12mc

to the mplayer command line help?

(In reply to comment #3)
> Does adding
> 
>  -vc ffmpeg12mc
> 
> to the mplayer command line help?

Yes, in the sense that I now get a video window. Albeit an almost completely green one. New output log attached.

Created attachment 49866 [details]
Verbose output from mplayer with ffmpeg12mc

This time, mplayer displayed a video window. However, the contents were unrecognisable. And green.

I stopped playback manually after a few seconds.

(In reply to comment #3)
> Does adding
> 
>  -vc ffmpeg12mc
> 
> to the mplayer command line help?

I've just tried repeating this with my RV790, and using

$ mplayer -vo xvcm <file>

also fails in the exact same way as my RV350. However, *unlike* my RV350, adding

  -vc ffmpeg12mc

makes playback work with my RV790.

Since mplayer's XvMC support is obviously working correctly, I am now assuming the problems I am seeing with xine are due to bugs in xine itself.

Also gives green and blobby playback with M66GL chip (RV535?) in my Lenovo T60p.

I think this is a duplicate of my report in bug 39309. I haven't tried xvmc yet, as vdpau is much easier to set up (and I'm lazy).

The following commit does not resolve this bug:

commit 7b181d16c3b954bf567563e90e5e94bda833fab8
Author: Christian König <deathsimple@vodafone.de>
Date:   Wed Jan 4 15:59:29 2012 +0100

    vl/mpeg2: simple fix to get xine running again
    
    Otherwise xines xxmc plugin will just display green blocks.
    
    Signed-off-by: Christian König <deathsimple@vodafone.de>

xine is still showing a green video window with my RV350.

$ mplayer -vo xvmc -vc ffmpeg12mc <MPEG2 file>

isn't working here either.

Created attachment 57314 [details]
xvmc log obtained via RADEON_DEBUG=all

Having a similar problem on a R420.
When using mplayer -vo xvmc to play an MPEG-2 file (recorded from DVB) I can only see a window filled with a majority of green squares flashing.
On stderr, the following message is shown:

r300 FP: Compiler Error:
compiler/r300_fragprog_emit.c::begin_tex(): Too many texture indirections
Using a dummy shader instead.

I then played the same video setting the RADEON_DEBUG environment variable to "all", because I don't know what can be excluded. I then cut the lines following the error message from the log, assuming those where the lines regarding the dummy shader used as a failsafe by the r300 driver.
I'm using a self-compiled git snapshot of mesa obtained on 2012-02-15 on a Slackware64 13.37 running kernel 3.2.6.
Please tell me if more info are needed.

(In reply to comment #10)
> Created attachment 57314 [details]
> xvmc log obtained via RADEON_DEBUG=all
> 
> Having a similar problem on a R420.
> When using mplayer -vo xvmc to play an MPEG-2 file (recorded from DVB) I can
> only see a window filled with a majority of green squares flashing.
> On stderr, the following message is shown:
> 
> r300 FP: Compiler Error:
> compiler/r300_fragprog_emit.c::begin_tex(): Too many texture indirections
> Using a dummy shader instead.
> 

Can you try the latest version of mesa from git?  I don't think xvmc playback works, but that error message should be fixed.  If you still see that error, please use the environment variable RADEON_DEBUG=fp,vp and post the output.

Created attachment 60474 [details]
xvmc log obtained via RADEON_DEBUG=fp,vp on mesa-git @ 20120423

(In reply to comment #11)
> Can you try the latest version of mesa from git?  I don't think xvmc playback
> works, but that error message should be fixed.  If you still see that error,
> please use the environment variable RADEON_DEBUG=fp,vp and post the output.

Still getting the same error message on a git snapshot taken a few hours ago. In the attached log I cut the text after that error message as in the first one.
Do you need more info to narrow down the issue?

Created attachment 60501 [details] [review]
Possible fix for too many indirections on r400

Do you still see the error message with this patch?

Created attachment 60517 [details]
fp,vp log on patched mesa-git @20120424 on R420 hardware

(In reply to comment #13)
> Created attachment 60501 [details] [review] [review]
> Possible fix for too many indirections on r400
> 
> Do you still see the error message with this patch?

I now see an additional "too many textures indirections" error message while playing a file in mplayer with -vo xvmc, so I guess it's not working as expected.
Attached is an updated fp,vp log.

Still no clue of what could be going awry?
This is still happening on recent git checkouts, regardless of the previous patch.
Please do tell me if you need more information to narrow down the issue.

XvMC support has been removed.