Bug 76659 - Display does not return from DPMS off using ATI drivers
Summary: Display does not return from DPMS off using ATI drivers
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Radeon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Default DRI bug account
QA Contact:
Depends on:
Reported: 2014-03-26 21:16 UTC by Tyler Brock
Modified: 2014-06-06 16:54 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:

XOrg Log (54.22 KB, text/plain)
2014-03-26 21:16 UTC, Tyler Brock
no flags Details
Kernel messages in systemd journal since last boot (73.32 KB, text/plain)
2014-03-28 00:05 UTC, Tyler Brock
no flags Details
System returning from lock-screen sleep (1.76 MB, image/jpeg)
2014-03-31 14:16 UTC, Tyler Brock
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Tyler Brock 2014-03-26 21:16:54 UTC
Created attachment 96427 [details]
XOrg Log


I've got a Turks XT and the gnome power management timeout causes my screen to turn off but it often does not come back (meaning moving the mouse and/or typing on the keyboard have wake the screen but I see only black). Attempting to switch to a terminal from out of X by using ctrl-alt-fx does not seem to enable the display either but I am able to login (without seeing anything) and reboot the box. The screen is on and wakes from sleep but usually nothing is displayed. Sometimes there is a flickering line at the top of the screen.

Relevant output from lspci:
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Turks XT [Radeon HD 6670/7670]

Additional info:
xorg-server 1.15.0-5
xf86-video-ati 1:7.3.0-1

I've attached my Xorg.0.log

Not sure if any extra info would be contained other logs (and not sure where to find them) but I would be happy to follow up if needed.

Steps to reproduce:
Start Computer
Login to GDM
Leave and let computer idle
Return and try to wake computer
Screen is now permanently black
Comment 1 Alex Deucher 2014-03-26 21:20:18 UTC
Please attach your dmesg output from after the display does not come back.  Is this a regression?  If so, can you bisect the kernel?
Comment 2 Tyler Brock 2014-03-27 15:11:02 UTC
I found nothing in the logs yesterday but then when I came into work today the monitor was flickering and essentially dead. I plugged in another monitor and everything works just fine. It was just the monitor dying!

Thanks for taking a look Alex.
Comment 3 Tyler Brock 2014-03-27 23:57:16 UTC
It seems it's doing the same thing with the new monitor... there is definitely something wrong. Is there another place I can look besides the dmesg output from the systemd journal?
Comment 4 Tyler Brock 2014-03-28 00:05:44 UTC
Created attachment 96502 [details]
Kernel messages in systemd journal since last boot
Comment 5 Tyler Brock 2014-03-28 00:06:16 UTC
Comment on attachment 96502 [details]
Kernel messages in systemd journal since last boot

This was me just running "journalctl --boot -1 -k > dmesg.log"
Comment 6 Tyler Brock 2014-03-31 14:16:56 UTC
Created attachment 96662 [details]
System returning from lock-screen sleep

Today when I woke the computer it had a black screen, switching to terminal showed the terminal shifted from off center (usually the login text appears at the top left of the screen).
Comment 7 Tyler Brock 2014-04-04 15:15:52 UTC
Any thoughts Alex? I basically need to restart my computer almost every time the screen turns off. I have no problem providing any help I could give you guys in figuring this out.
Comment 8 Alex Deucher 2014-04-04 16:47:52 UTC
Does manually turning off the display also cause problems?  e.g. run:
xset dpms force off
xset dpms force on
from a terminal

Can you get remote access to the box (e.g., ssh)?  If so can you try manually turning the displays on/off?  E.g.,

DISPLAY=:0.0 xset dpms force off
DISPLAY=:0.0 xset dpms force on


DISPLAY=:0.0 xrandr --output DVI-0 --off
DISPLAY=:0.0 xrandr --output DVI-0 --auto
Comment 9 André Wöbbeking 2014-05-10 22:40:59 UTC
Hi, I think that I've the same problem. 

I've a "ATI Radeon XPRESS 200M 5975 (PCIE)" (ChipID = 0x5975) (from Xorg.0.log).

Here already DISPLAY=:0.0 xset dpms force off brings the screen back.

I'm running Kubuntu 14.04 32 bit.

Comment 10 André Wöbbeking 2014-05-11 21:51:29 UTC
I set the suspend time to two hours now but even after a much shorter time (lets say 10 minutes) the graphic is displayed and when I press any key the screen becomes black. xset q says that the monitor is still on. If I press more keys it takes a while (maybe minutes) til the sreen resumes.

I think I had similar problem on another box (with Radeon HD 5570) with Debian Sid x86_64. But it seems not to happen any more for some days now (maybe the update to Linux 3.14).
Comment 11 Tyler Brock 2014-06-06 16:54:04 UTC
I'm seeing new messages now when I look in dmesg:

[drm:radeon_dp_link_train_cr] *ERROR* clock recovery tried 5 times
[drm:radeon_dp_link_train_cr] *ERROR* clock recovery failed

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.