Red Hat Bugzilla – Bug 480526
Resume from hibernate fails on Tyan Tomcat K8E for 2.6.28 kernels
Last modified: 2009-12-18 02:38:38 EST
Description of problem:
After upgrading to kernel 220.127.116.11-9.rc2.fc10.x86_64 from 18.104.22.168-169.fc10.x86_64 on a Tyan Tomcat K8E (S2865AG2NRF), the system fails to resume from hibernate. Instead, it boots up normally ending up with the GDM login screen whereas before, the GNOME screensaver prompted the user for his password to resume the GNOME session from which the hibernate command was issued.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click "Hibernate" on the logout panel from within active GNOME session.
2. Boot system after it has powered off.
GDM login manager appears on the screen.
Lock dialog window of GNOME screensaver appears on the screen.
- Resume from hibernate used to work for kernel 22.214.171.124-169.fc10.x86_64
and earlier kernels.
- Resume from hibernate also fails for kernel 2.6.29-0.19.rc0.fc11.x86_64.
- Suspend on the same system ceased to work a some point in the F9 update
cycle for some 2.6.27.x kernel whereas it workd with the initial F9
kernel 2.6.25-14.fc9.x86_64, see bug 469580.
kernel-126.96.36.199-16.fc10.x86_64 fails as previous 2.6.28.x kernels. In /var/log/boot.log, a surprising entry can be found. After recovering file journals from the failed attempt to hibernate -or- to resume from hibernate, one reads
Enabling local filesystem quotas: [ OK ]
Enabling /etc/fstab swaps: swapon: /dev/mapper/VolGroup00-LogVol03:
software suspend data detected. Reinitializing the swap.
Setting up swapspace version 1, size = 4194300 KiB
It is thus claimed that -suspend- data has been detected in the swap partition. However, hibernation had been triggered as root from runlevel 3 executing 'pm-hibernate'. The outcome is hence the same as when clicking button "Shutdown > Hibernate" in a GNOME session.
I would like to point out that this bug is also reproducible on HP Pavilion dv1657cl with Intel Pentium-M CPU and kernel-188.8.131.52-19.fc10.i686. I haven't been able to boot a 2.6.29-rc2 kernel to test if it has been fixed in upstream or not, so perhaps someone else can provide some more information about this.
Kernel 2.6.29-0.6.rc3.fc10.x86_64 still fails to resume. However, upon selection of kernel-184.108.40.206-170.2.5.fc10.x86_64 in the boot loader menu, the still present swap image is read in correctly. The screensaver lock dialog appears and upon logging in, 'uname -r' reports 2.6.29-0.6.rc3.fc10.x86_64!
Kernel 2.6.29-0.22.rc4.git1.fc10.x86_64 equally fails to load its own hibernate image whereas alternate kernel-220.127.116.11-170.2.19.fc10.x86_64 does load both of the own and the 2.6.29 ones.
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. 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 WONTFIX if it remains open with a Fedora
'version' of '10'.
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 prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 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 please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
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.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.
Thank you for reporting this bug and we are sorry it could not be fixed.