Bug 31230 - [RADEON:KMS:RV250:RESUME] corrupted screen after resume
Summary: [RADEON:KMS:RV250:RESUME] corrupted screen after resume
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: 2010-10-30 03:09 UTC by Johannes Obermayr
Modified: 2019-11-19 08:16 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
specific part of /var/log/messages (~13 MiB, "drm.debug=255") (574.44 KB, application/octet-stream)
2010-10-30 03:09 UTC, Johannes Obermayr
no flags Details

Description Johannes Obermayr 2010-10-30 03:09:58 UTC
Created attachment 39897 [details]
specific part of /var/log/messages (~13 MiB, "drm.debug=255")

After resume the screen is totally corrupted.
Comment 1 Jerome Glisse 2011-02-09 07:48:02 UTC
Is this still an issue with recent kernel ?
Comment 2 Johannes Obermayr 2011-02-11 10:13:25 UTC
Yes. It is still valid on 2.6.38-rc4.
Comment 3 dplasa 2014-02-05 22:22:59 UTC
Bug is still present up to current kernels (I tested up to 3.11 in ubuntu 13.10) - the screen is corrupted after a resume from pm-suspend (suspend to ram). Corrupt means: the screen content appears approx. 3 times over the screen. (Sort of like three tiles).
Also the VT is trashed, I see 3 login prompts :)

However the screen is ok/fixed after I do a pm-hibernate (suspend to disk) and resume from it.

When I used "nomodeset" and let the xorg driver do the mode setting stuff everything worked fine. Unfortunatly the recent xorg drivers have lost their capability to do their own modeset and now I'm stuck with KMS.
Comment 4 dplasa 2014-03-03 13:31:20 UTC
Here'a some images of my corrupted screen:
http://pl.vc/26q6c
http://pl.vc/2k7t5
http://pl.vc/4zpqm
Comment 5 Martin Peres 2019-11-19 08:16:07 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/164.


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.