Bug 20510 - BEGIN_RING without end at radeon_accel.c:859
Summary: BEGIN_RING without end at radeon_accel.c:859
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/Radeon (show other bugs)
Version: 7.4 (2008.09)
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: xf86-video-ati maintainers
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-06 10:16 UTC by Mikko C.
Modified: 2009-03-18 04:07 UTC (History)
0 users

See Also:
i915 platform:
i915 features:

Attachments

Description Mikko C. 2009-03-06 10:16:17 UTC 
I just updated mesa, drm, and xf86-video-ati to git.
Now, when I open a video (dragonplayer or smplayer) my Xorg.0.log gets flooded with these messages:

(EE) RADEON(0): BEGIN_RING without end at radeon_accel.c:859
(EE) RADEON(0): ADVANCE_RING without begin at radeon_accel.c:882

after a while it eventually becomes only:

(EE) RADEON(0): BEGIN_RING without end at radeon_accel.c:692


I've had two X crashes so far, but I'm not sure they are real crashes because I didn't find any evidence in the log, beside the above errors. Maybe X just restarts itself because the log dimension gets very big? I'm talking about 13-15 MB.

Anyway, my last update was Feb 26th, so something happened after that.
Comment 1 Mikko C. 2009-03-07 02:11:14 UTC 
Downgrading to mesa 7.3 solves the issue.
Comment 2 Tomáš Chvátal 2009-03-07 09:54:38 UTC 
I confirm this bug even on mesa-7.3
drm and driver is from trunk.
Comment 3 Tomáš Chvátal 2009-03-08 06:34:35 UTC 
Also tracked this down to that it occurs only when using XV overlay. If i use opengl for rendering the video i get flickering but no errors in xorg.log
Comment 4 Alex Deucher 2009-03-15 09:12:18 UTC 
should be fixed in a55ced5ee20c07e743c7c0978803fd10589c1531
Comment 5 Fabio Pedretti 2009-03-18 04:07:24 UTC 
What about releasing a 6.12.1 version with this fix?

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.