Bug 67169 - Black screen after waking from sleep
Summary: Black screen after waking from sleep
Status: RESOLVED MOVED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: high major
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-07-22 12:04 UTC by Marco Scannadinari
Modified: 2019-11-19 08:36 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:

Attachments
xorg log (58.20 KB, text/plain)
2013-07-22 12:04 UTC, Marco Scannadinari 		no flags Details
uname -a (91 bytes, text/plain)
2013-07-22 12:13 UTC, Marco Scannadinari 		no flags Details
journalctl -b (134.13 KB, text/plain)
2013-07-22 12:13 UTC, Marco Scannadinari 		no flags Details
dmesg (52.32 KB, text/plain)
2013-07-22 12:13 UTC, Marco Scannadinari 		no flags Details
View All

Description Marco Scannadinari 2013-07-22 12:04:08 UTC 
Created attachment 82813 [details]
xorg log

Waking the screen from sleep wakes it but all i get is a black screen. I am able to type and change ttys, etc, but after `systemctl restart gdm` as root the screen gets 'No signal'.
The setting that causes this is GNOME's 'Blank screen' option in Settings>Power>Blank Screen

I can confirm that AMD's proprietary drivers fix this.
Comment 1 Marco Scannadinari 2013-07-22 12:05:42 UTC 
Possibly related to Bug 61463?
Comment 2 Alex Deucher 2013-07-22 12:09:40 UTC 
What kernel are you using?  Please attach your dmesg output.
Comment 3 Marco Scannadinari 2013-07-22 12:13:15 UTC 
Created attachment 82814 [details]
uname -a
Comment 4 Marco Scannadinari 2013-07-22 12:13:35 UTC 
Created attachment 82815 [details]
journalctl -b
Comment 5 Marco Scannadinari 2013-07-22 12:13:50 UTC 
Created attachment 82816 [details]
dmesg
Comment 6 Alex Deucher 2014-01-27 14:18:15 UTC 
Is this still an issue with a newer kernel?
Comment 7 Martin Peres 2019-11-19 08:36:26 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/356.

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.