Bug 6249 - VIA ME600 + XvMC + mplayer hang
Summary: VIA ME600 + XvMC + mplayer hang
Status: RESOLVED INVALID
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/other (show other bugs)
Version: DRI git
Hardware: x86 (IA32) Linux (All)
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-03-13 23:43 UTC by Dan Smolik
Modified: 2019-10-14 13:20 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Dan Smolik 2006-03-13 23:43:53 UTC 
I have build simple video kiosk system that play whole day some video.

I have use Xorg + Mplayer 1.0.pre6 + XvMC patch + DRI from CVS. All works
absolutely great with HW accel. But after 1 sometime 3 days I found in log this
message:

 kernel: [drm:via_cmdbuf_wait] *ERROR* via_cmdbuf_wait timed out hw 1a1680
cur_addr 11fd00 next_addr 1a4d18
Mar 12 15:35:33 fish last message repeated 140 times


and after may be 1 hour system completely hang. I found some post that says that
disabling AGPDMA may help. I have upgraded to latest BIOS that may solve problem
with DMA hang. Situation is better but after few days hang. Have anybody the
same problem. I thing that this problem is HW related.

           
        Cheers
    
                Dan
Comment 1 Dan Smolik 2006-03-13 23:45:09 UTC 
I think that this problem is HW related.
Sorry.
Comment 2 chemtech 2013-03-15 13:58:33 UTC 
Dan Smolik 
Do you still experience this issue with newer drivers ?
Please check the status of your issue.
Comment 3 Martin Peres 2019-10-14 13:20:19 UTC 
Hi,

Freedesktop's Bugzilla instance is EOLed and open bugs are about to be migrated to http://gitlab.freedesktop.org.

To avoid migrating out of date bugs, I am now closing all the bugs that did not see any activity in the past year. If the issue is still happening, please create a new bug in the relevant project at https://gitlab.freedesktop.org/drm (use misc by default).

Sorry about the noise!

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.