Bug 429960

Summary: hibernating again after hibernate failure causes system crash
Product: [Fedora] Fedora Reporter: Michael De La Rue <mvyynqbgerqungqbgpbz.yeuhc>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: low    
Version: 7CC: triage
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-06-17 03:00:07 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Michael De La Rue 2008-01-23 23:37:56 UTC
Description of problem:
after out of memory on hibernate next hibernate crashes machine.

Version-Release number of selected component (if applicable):
2.6.23.12-52.fc7

How reproducible:
occasional 

Steps to Reproduce:
1. set up swap stupidly (2G RAM 1.9G swap)
2. use _lots of applications for a while_
3. attempt to hibernate - fails with "swsusp: Not enough free swap"
4. kill some applications
5. try again

Actual results:
Machine crashes and dies completely; sysrq (sync / unmount / reboot) appears to
work but no EIP in /var/log/messages.

Expected results:
hibernate fails initially;
after closing programmes either 
- hibernate fails without crashing
- hibernate succeeds

Additional info:
The configuration on this machine is a bit strange since it has 2G memory and
just a little less swap.

             total       used       free     shared    buffers     cached
Mem:       2075324    2021848      53476          0       5392    1394400
-/+ buffers/cache:     622056    1453268
Swap:      2064368     437368    1627000

Due to the fact that there's nothing in /var/log/messages after such a crash I
can't attach more info, but suggestions for capturing logs would be appreciated.

Comment 1 Bug Zapper 2008-05-14 15:16:58 UTC
This message is a reminder that Fedora 7 is nearing the end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 7. 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 '7'.

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 7'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 7 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. 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. If possible, it is recommended that you try the newest available Fedora distribution to see if your bug still exists.

Please read the Release Notes for the newest Fedora distribution to make sure it will meet your needs:
http://docs.fedoraproject.org/release-notes/

The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Bug Zapper 2008-06-17 03:00:05 UTC
Fedora 7 changed to end-of-life (EOL) status on June 13, 2008. 
Fedora 7 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.