Description of problem: AMD E350 APU unreliable when returning from suspend.
If dual screen attached and running X, the second monitor stays black after resume but xrandr shows the monitor present.
If the machine is suspended again, the computer does not return from the second suspend. Light changes from blinking to solid but does not appear to wake. This occurs if dual screen or single.
If the suspend is initiated from a console, either by pm-suspend or systemctl suspend then both screens will return reliably.
Version-Release number of selected component (if applicable):
Fedora 20 - Issue started with 3.15.3 ie regression from 3.14.9. Issue still there with 3.15.5
00:01.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Wrestler [Radeon HD 6310]
Steps to Reproduce:
1. From Mate desktop, initiate a suspend (menu, pm-suspend or systemctl suspend)
2. Wake computer (note second display stays black)
3. Suspend again
4. Wake computer
Power led changes from blinking to solid
Screens stay black from second suspend. Changing console (Alt-F2) does not display.
Computer does not respond to pings.
Computer wakes from suspend correctly as it did with 3.14.9
The computer is a thin client with no ability to look at logs once it fails. Other hardware (ie Intel) using the same rootfs image does not exhibit the fault
Still same behavior with 3.16.2.
If switched to a second console and systemctl suspend is issued.
The second display comes back after awakening in tty2.
If Alt F1 to X display, the second goes black in X and Alt F2 console.
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora 'version'
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.
Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 20 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
Thank you for reporting this bug and we are sorry it could not be fixed.