Bug 20892 - Background corruption with EXA on RV670 when moving windows in KDE 4.2
Summary: Background corruption with EXA on RV670 when moving windows in KDE 4.2
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Driver/radeonhd (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Luc Verhaegen
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-26 14:23 UTC by Alain Perrot
Modified: 2011-10-31 16:37 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
Desktop background corruption after moving a window (359.33 KB, image/png)
2009-03-26 14:23 UTC, Alain Perrot
no flags Details
Same desktop background area without corruption (237.02 KB, image/png)
2009-03-26 14:24 UTC, Alain Perrot
no flags Details
Xorg log file (58.28 KB, text/plain)
2009-04-09 16:18 UTC, Torsten Evers
no flags Details

Description Alain Perrot 2009-03-26 14:23:08 UTC
Created attachment 24293 [details]
Desktop background corruption after moving a window

Hi,

Using the radeonhd driver with EXA acceleration enabled on my Radeon HD 3870 (RV670) card, I have desktop background corruption when I move windows in KDE 4.2
with desktop effects disabled.

The corruption does not always appear immediately when starting moving a window, but shaking the window will trigger the corruption for sure.

Once the background is corrupted, a refresh (for example by clicking on it) will restore it.

With EXA acceleration disabled, the problem disappears.

The radeon driver does not have this issue with EXA acceleration enabled.

I have tested latest radeon and radeonhd drivers from their git master branch, with the drm modules from the git r6xx-r7xx-support branch.
Comment 1 Alain Perrot 2009-03-26 14:24:57 UTC
Created attachment 24294 [details]
Same desktop background area without corruption
Comment 2 Torsten Evers 2009-04-09 15:21:49 UTC
I can second this bug and reported it already on ML and @freenode in #radeonhd channel. I made a video showing the corruption:
http://www.nightwulf.org/radeonhd.avi

The corruptions aren't that massive, when using xrender with kwin but they don't disappear completly.

Greets, 
Torsten
Comment 3 Alex Deucher 2009-04-09 15:49:18 UTC
Do you have similar problems with radeon (xf86-video-ati) as well?  If not that might help isolate the problem.
Comment 4 Torsten Evers 2009-04-09 16:18:29 UTC
Created attachment 24687 [details]
Xorg log file
Comment 5 Torsten Evers 2009-04-09 17:14:49 UTC
(In reply to comment #4)
> Created an attachment (id=24687) [details]
> Xorg log file
> 

sorry, rest of the text was lost while saving. As you can see in the attached log file, EXA works with xf86-video-ati and it doesn't produce artifacts. Video looks good and xvinfo seconds, that XV works.

In opposite to the original poster, I have a R680 (=HD3870X2 with 2xRV670).
Comment 6 Parag 2009-04-11 15:30:29 UTC
Happens to me on a RHD 4670 (RV730XT) on KDE 4.2.2 desktop. Don't need to do any thing specific - appears randomly. Have not tested radeon enough to comment on whether it happens there - will try radeon shortly.
Comment 7 Alex Deucher 2009-04-12 21:09:17 UTC
Can you narrow down the problem to a particular accel hook?  try the following options to selectively disable hooks:

Option "EXANoComposite"
Option "EXANoUploadToScreen"
Option "EXANoDownloadFromScreen"
Comment 8 Alain Perrot 2009-04-13 03:42:15 UTC
(In reply to comment #7)
> Can you narrow down the problem to a particular accel hook?  try the following
> options to selectively disable hooks:
> 
> Option "EXANoComposite"
> Option "EXANoUploadToScreen"
> Option "EXANoDownloadFromScreen"
> 

I have just tried these options with latest radeonhd driver from git.

I have tested with each option alone, with the three options together, and with both EXANoUploadToScreen and EXANoDownloadFromScreen.

In all cases, the result is the same as with none of these options: the background corruption is still there (on a side note, EXANoDownloadFromScreen has a major impact on performance).

One more thing I have just noticed, enabling KWin 4.2 desktop effects using XRender composition (since OpenGL is not possible yet on R6xx) reduces significantly the background corruption (I've only tested this with none of the three options). But XRender desktop effects have an impact on performances with the radeonhd driver while they run smoothly with the radeon (xf86-video-ati) driver.
Comment 9 Parag 2009-04-13 15:59:05 UTC
I can confirm that radeon driver does not have any similar issues.
Comment 10 Torsten Evers 2009-04-13 16:10:30 UTC
(In reply to comment #8)
> (In reply to comment #7)
> > Can you narrow down the problem to a particular accel hook?  try the following
> > options to selectively disable hooks:
> > 
> > Option "EXANoComposite"
> > Option "EXANoUploadToScreen"
> > Option "EXANoDownloadFromScreen"
> > 
> 
> I have just tried these options with latest radeonhd driver from git.
> 
> I have tested with each option alone, with the three options together, and with
> both EXANoUploadToScreen and EXANoDownloadFromScreen.
> 
> In all cases, the result is the same as with none of these options: the
> background corruption is still there (on a side note, EXANoDownloadFromScreen
> has a major impact on performance).
> 
> One more thing I have just noticed, enabling KWin 4.2 desktop effects using
> XRender composition (since OpenGL is not possible yet on R6xx) reduces
> significantly the background corruption (I've only tested this with none of the
> three options). But XRender desktop effects have an impact on performances with
> the radeonhd driver while they run smoothly with the radeon (xf86-video-ati)
> driver.
> 

I can second that behaviour of radeonhd. None of the options affects the issue this bug report is about but has impacts on performance (of course). Using kwin as a composite manager via xrender reduces the problems which is caused in my opinion simply by an increased rate of desktop upgrades. These are caused by all that fancy shadow and fading effects.

Greets,

Torsten
Comment 11 Jeremy Huddleston Sequoia 2011-10-16 15:59:02 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 12 Alain Perrot 2011-10-17 10:29:15 UTC
(In reply to comment #11)
> 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.

As said in the original bug report, the radeon driver (which you refer to as xf86-video-ati) was not affected by this issue.

I have not used radeonhd for more than 2 years, and it has not seen any commit for more than one year according to its git repository, so WONTFIX is definitively OK for me.


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.