Bug 26552 - xorg uses up one cpu and hangs during video playback
Summary: xorg uses up one cpu and hangs during video playback
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: 7.4 (2008.09)
Hardware: Other All
: medium major
Assignee: Egbert Eich
QA Contact: Xorg Project Team
Depends on:
Reported: 2010-02-13 06:19 UTC by Wilfried Goesgens
Modified: 2011-11-07 15:22 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Description Wilfried Goesgens 2010-02-13 06:19:35 UTC
I can't get any usefull backtrace of it?
(gdb) where
#0  0x00007ffa77eeb4e7 in ?? ()
#1  0x00007ffa764b9833 in ?? ()
#2  0x0000000000010000 in ?? ()
#3  0x0000000000836aa0 in ?? ()
#4  0x0000000000000637 in ?? ()
#5  0x0000000000836b80 in ?? ()
#6  0x0000000000000000 in ?? ()

this is an AMD64 box, debian SID, 
01:00.0 VGA compatible controller: ATI Technologies Inc RV630 [Radeon HD 2600XT] (rev ff)
01:00.1 Audio device: ATI Technologies Inc RV630/M76 audio device [Radeon HD 2600 Series] (rev ff)

radeonhd pulled from GIT.

please let me know how I can provide you with more information.
Comment 1 Wilfried Goesgens 2010-02-13 06:20:49 UTC
the process won't go away with all sorts of kill.
Comment 2 Jeremy Huddleston Sequoia 2011-10-16 16:01:23 UTC
Does this issue occur with the preferred ati driver (xf86-vide-ati)?  If so, please move this to the Driver/Radeon component.  

Development of radeonhd has pretty much halted and development focus is on the ati driver.  Please see http://www.x.org/wiki/radeonhd

If the issue does not exist in the ati driver (or if there is no response to this message), this bug will be closed as WONTFIX unless someone contributes a patch.
Comment 3 Jeremy Huddleston Sequoia 2011-11-07 15:22:48 UTC
Closing due to lack of response.  Please reopen and move to the Driver/Radeon 
component if this issue persists with xf86-video-ati

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.