Bug 20111 - RV630 : Xorg freeze after "exaCopyDirty: Pending damage region empty!"
Summary: RV630 : Xorg freeze after "exaCopyDirty: Pending damage region empty!"
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-02-13 16:21 UTC by Damien Raude-Morvan
Modified: 2011-11-07 15:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Xorg log (29.69 KB, text/plain)
2009-02-13 16:21 UTC, Damien Raude-Morvan
no flags Details
dmesg (for DRM module) (47.66 KB, text/plain)
2009-02-13 16:22 UTC, Damien Raude-Morvan
no flags Details

Description Damien Raude-Morvan 2009-02-13 16:21:39 UTC
Created attachment 22920 [details]
Xorg log

Hi,

I'm currently using radeonhd + drm built from git branch r6xx-r7xx-support.
Commit d2785466

When using EXA+DRI, I'm getting Xorg freeze just after KSplash (before loading Plasma/KDE 4.2).
Last message form Xorg.0.log is "exaCopyDirty: Pending damage region empty!"

Cheers,
-- 
Damien Raude-Morvan
Comment 1 Damien Raude-Morvan 2009-02-13 16:22:06 UTC
Created attachment 22921 [details]
dmesg (for DRM module)
Comment 2 Michel Dänzer 2009-02-14 02:47:15 UTC
> Last message form Xorg.0.log is "exaCopyDirty: Pending damage region empty!"

FWIW, this message is irrelevant for the problem and has been disabled by default in xserver Git.
Comment 3 Alex Deucher 2009-02-16 07:58:44 UTC
you might try this drm patch:
http://www.botchco.com/alex/xorg/no_wait_until.diff
Comment 4 Damien Raude-Morvan 2009-02-16 14:51:56 UTC
Hi Alex,

Thanks for taking care of this bug but today I can't reproduce it at will (with ou whithout your patch applied). Maybe you should close this issue for now, I'll reopen it if I found a clear path to reproduce it.

Thanks,
Comment 5 Jeremy Huddleston Sequoia 2011-10-16 15:57:33 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 6 Jeremy Huddleston Sequoia 2011-11-07 15:16:49 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.