Bug 22621 - graphics corruption after resume with radeon and with KDE 4 with compositing enabled
Summary: graphics corruption after resume with radeon and with KDE 4 with compositing ...
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-05 02:19 UTC by Martin Steigerwald
Modified: 2019-11-19 08:06 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
X.org configuration file (3.15 KB, text/plain)
2009-07-05 02:19 UTC, Martin Steigerwald
no flags Details
Window border graphics corruption after resuming from suspend to RAM (777.49 KB, image/png)
2009-07-05 02:22 UTC, Martin Steigerwald
no flags Details
Window border graphics corruption after resuming from TuxOnIce hibernation (645.25 KB, image/png)
2009-07-05 02:25 UTC, Martin Steigerwald
no flags Details

Description Martin Steigerwald 2009-07-05 02:19:49 UTC
Created attachment 27387 [details]
X.org configuration file

After resume from suspend to ram or suspend to disk using TuxOnIce there is graphics garbage around window borders. It goes away when I start systemsettings, untick the checkmark for activating desktop effect, tick it again and press "Apply". It also goes away when I disable compositing and re-enable it again afterwards. I did not see other malfunctions, just the graphics corruption while compositing is still working after resume.

I don't know whether DRI is the approbiate place to report this against. I do not even know whether it might be a KDE 4 kwin problem instead. But I had to start somewhere.

This is happening on an IBM ThinkPad T42 with radeon chipset:
martin@shambhala:~> lspci -nn | grep VGA
01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV350 [Mobility Radeon 9600 M10] [1002:4e50]

Using XOrg CVS as 7.4 is not in the version list. I use the following on a mixture of Debian Lenny/Squeeze/Sid/Experimental:

martin@shambhala:~> apt-show-versions | egrep "(libgl1-mesa-dri|xserver-xorg-video-radeon|xserver-xorg/|xserver-xorg-core/)"
libgl1-mesa-dri/sid uptodate 7.4.4-1
xserver-xorg/sid uptodate 1:7.4+3
xserver-xorg-core/sid uptodate 2:1.6.1.901-3
xserver-xorg-video-radeon/sid uptodate 1:6.12.2-2
xserver-xorg-video-radeonhd/sid uptodate 1.2.5-1

(I made sure that X.org and Mesa related packages are consistently at Sid.)

I am using radeon driver.

I attach my xorg.conf. I also attach two screenshots that demonstrate the problem.

Regarding my xorg.conf: I am using XAA, since X.org tends to use 99% CPU with EXA. Yes, I know glxgears is not a benchmark. I am using CONFIG_FB_RADEON.

My current kernel is:

martin@shambhala:~> cat /proc/version
Linux version 2.6.29.2-tp42-toi-3.0.1 (martin@shambhala) (gcc version 4.3.3 (Debian 4.3.3-3) ) #2 PREEMPT Tue Apr 28 22:08:44 CEST 2009

I do not yet use 2.6.30 since it reboots after resuming from TuxOnIce hibernation. I am building a new kernel with 2.6.30.1 and some TuxOnIce fixes that might work tough. I will report when it works and it makes any difference.

Please tell me when you need anything more.
Comment 1 Martin Steigerwald 2009-07-05 02:22:53 UTC
Created attachment 27388 [details]
Window border graphics corruption after resuming from suspend to RAM
Comment 2 Martin Steigerwald 2009-07-05 02:25:53 UTC
Created attachment 27389 [details]
Window border graphics corruption after resuming from TuxOnIce hibernation

Please note that only the area around window borders is corrupted. 

I just tried another thing: kwin --replace will also "fix" the gfx corruption.
Comment 3 Martin Peres 2019-11-19 08:06:10 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/amd/issues/52.


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.