[Openchrome-users] SP8000E and 1080p video?

gpeters@deepsky.com gpeters
Thu Feb 15 06:55:54 PST 2007


Folks,

How is openchrome at playing video at 1080p?  I just got XvMC working
with mplayer, and I am having difficulty playing 29.97Hz 1080p
video on it!  Top shows the CPU maxing out at 75% or so, and the video
plays at at an almost viable speed.

I'm wondering if I'm hitting a fundamental limit of the chipset I have
(which I doubt, since I'm finding resources on the net that say this
works).  I'm using mplayer, perhaps I should build Xine?  I'll try that
and report back.

I built libxvmc, libdrm et al.  The library Xorg is using for libdrm
is its own extension library, not the one from /lib.  I found that
interesting, but didn't screw around with it.  Should I?

All in all, I'm wondering if there's a part of my system I can speed
up to make this happen.

My syslog shows this interesting set of messages on X server
initialization:

agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[drm:drm_release] *ERROR* Reclaim buffers locked deadlock.
        This is probably a single thread having multiple
        DRM file descriptors open either dying or closing file descriptors
        while having the lock. I will not reclaim buffers.
        Locking context is 0x00000001
[drm:drm_release] *ERROR* Reclaim buffers locked deadlock.
        This is probably a single thread having multiple
        DRM file descriptors open either dying or closing file descriptors
        while having the lock. I will not reclaim buffers.
        Locking context is 0x00000001
agpgart: Found an AGP 3.5 compliant device at 0000:00:00.0.
agpgart: Putting AGP V3 device at 0000:00:00.0 into 8x mode
agpgart: Putting AGP V3 device at 0000:01:00.0 into 8x mode
[drm:drm_release] *ERROR* Reclaim buffers locked deadlock.
        This is probably a single thread having multiple
        DRM file descriptors open either dying or closing file descriptors
        while having the lock. I will not reclaim buffers.
        Locking context is 0x00000001

(for each of the two X server starts, one with VBEModes, then the
second one without so I can go at 1080p).

The next tidbit is: I can't play any 1920x1080 video while firefox is
running.  The failure looks like this in the X server log:

Freed 38131504 (pool 0)
Fulfilled via DRI at 38131504
Freed 38131504 (pool 2)
Freed 33538576 (pool 2)
Freed 34068528 (pool 2)
Freed 34598480 (pool 2)
Freed 35128432 (pool 2)
Freed 35658384 (pool 2)
Freed 36188336 (pool 2)
Freed 36718288 (pool 2)
Freed 37248240 (pool 2)
Freed 37778192 (pool 2)
Freed 33185280 (pool 0)
Fulfilled via DRI at 33185280
Freed 38131504 (pool 0)
Fulfilled via DRI at 39406080
Freed 33185280 (pool 2)
Freed 39406080 (pool 2)
Fulfilled via DRI at 35274256
Fulfilled via DRI at 38407728
Fulfilled via DRI at 41541200
Fulfilled via DRI at 44674672
Fulfilled via DRI at 47808144
Fulfilled via DRI at 50941616
Fulfilled via DRI at 54075088
Fulfilled via DRI at 57208560
Fulfilled via DRI at 60342032
Freed 39406080 (pool 0)
DRM memory allocation failed
(EE) VIA(0): [Xv] Port 0: Not enough resources to complete the request. Probably out of memory.

I figure this is plain and normal; I am out of memory.  Firefox is a hog.




More information about the Openchrome-users mailing list