Red Hat Bugzilla – Bug 753611
Hibernate ceased working after upgrade from Fedora 15
Last modified: 2012-11-13 10:04:09 EST
Description of problem:
SSIA, system hibernated fine on Fedora 15, now it begins to hibernate, screen goes blank, then doesn't poweroff (likewise for suspend to RAM).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Hibernate (or suspend to RAM)
Blank screen, fan spins.
Hibernates/suspends. Later wakes up again,
Worked fine on Fedora 15.
Hardware info: http://www.smolts.org/client/show/pub_4177bc21-d587-47d3-8157-642476ed31a3
kernel-3.3.0-4.fc16 has been pushed to the Fedora 16 stable repository.
Please retest with this update.
[Mass hibernate bug update]
Dave Airlied has found an issue causing some corruption in the i915 fbdev after a resume from hibernate. I have included his patch in this scratch build:
This will probably not solve all of the issues being tracked at the moment, but it is worth testing when the build completes. If this seems to clear up the issues you see with hibernate, please report your results in the bug.
The machine in question (comment #0) has a Radeon graphics adapter i.e. shouldn't be affected by the i915 fbdev corruption.
With kernel-3.3.0-4.fc16, it hibernates but takes really long to do so (hard to guess what's happening as it doesn't have a harddisk activity LED and the drive is pretty quiet). Still not viable to use hibernation due to bug #744275.
# Mass update to all open bugs.
Kernel 3.6.2-1.fc16 has just been pushed to updates.
This update is a significant rebase from the previous version.
Please retest with this kernel, and let us know if your problem has been fixed.
In the event that you have upgraded to a newer release and the bug you reported
is still present, please change the version field to the newest release you have
encountered the issue with. Before doing so, please ensure you are testing the
latest kernel update in that release and attach any new and relevant information
you may have gathered.
If you are not the original bug reporter and you still experience this bug,
please file a new report, as it is possible that you may be seeing a
(Please don't clone this bug, a fresh bug referencing this bug in the comment is sufficient).
With no response, we are closing this bug under the assumption that it is no longer an issue. If you still experience this bug, please feel free to reopen the bug report.