Bug 91595 - RV410 white screen after resume
Summary: RV410 white screen after resume
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-08-10 08:45 UTC by José Jorge
Modified: 2019-11-19 09:07 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
radeontool registers ok (1.49 KB, text/plain)
2015-08-10 08:47 UTC, José Jorge
no flags Details
radeontool registers when screen is white (1.49 KB, text/plain)
2015-08-10 08:47 UTC, José Jorge
no flags Details
radeontool registers ok after hibernate and resume (1.49 KB, text/plain)
2015-08-10 08:48 UTC, José Jorge
no flags Details

Description José Jorge 2015-08-10 08:45:47 UTC
This is a Fujitsu Amilo M1437G with X700Mobile. Suspended/resumed well with UMS with a 2009 distro, but after upgrading the system to a 2015 Mageia 5 and a KMS only driver, screen is white after suspend. If then I hibernate the system through ssh, screen is ok.

Looks like the sbios does something that KMS does not, is there a way to debug this? I join the reg dumps.
Comment 1 José Jorge 2015-08-10 08:47:13 UTC
Created attachment 117604 [details]
radeontool registers ok

Just after a simple boot
Comment 2 José Jorge 2015-08-10 08:47:46 UTC
Created attachment 117605 [details]
radeontool registers when screen is white
Comment 3 José Jorge 2015-08-10 08:48:18 UTC
Created attachment 117606 [details]
radeontool registers ok after hibernate and resume
Comment 4 Martin Peres 2019-11-19 09:07:33 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/636.


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.