Bug 606800

Summary: hibernate fails to allocate memory
Product: [Fedora] Fedora Reporter: long
Component: pm-utilsAssignee: Jaroslav Škarvada <jskarvad>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: jskala, jskarvad, opensource, pknirsch, richard
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-13 07:27:13 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Description Flags
dmesg output none

Description long 2010-06-22 14:12:10 UTC
Created attachment 425939 [details]

Description of problem:
Have system set to hibernate after a period of inactivity.  Some times it fails to hibernate complaining about memory problems.  Various logs are attached

Version-Release number of selected component (if applicable):

How reproducible:
50% of time.

Steps to Reproduce:
1. wait until system tries to hibernate on its own
Actual results:
system does not hibernate but keeps running

Expected results:
system hibernates

Additional info:

Comment 1 long 2010-06-22 14:14:45 UTC
Created attachment 425945 [details]

Comment 2 long 2010-06-22 14:15:52 UTC
Created attachment 425946 [details]
dmesg output

Comment 3 Jaroslav Škarvada 2010-08-25 13:38:35 UTC
Looks like the kernel cannot allocate enough memory to suspend. AFAIK there should be half of memory free before suspend, if there is not enough memory the kernel should swap to make a room. Maybe you have a lot of memory mlocked (not allowed to swap)? If yes - increase your RAM or do not use the software mlocking your memory.

Comment 4 long 2010-08-27 14:48:52 UTC
This is not currently happening (different hibernation failure now) but I have to say if this is the way it really works that is completely user unfriendly and almost worthless.  User shouldn't have to care what their memory usage is.

Comment 5 Jaroslav Škarvada 2010-08-27 15:47:29 UTC
That's from design. You need not care, mostly the kernel manages this correctly. The only thing you can not is to mlock more than 1/2 of memory. For more details please see kernel documentation - /usr/share/doc/kernel-doc*/Documentation/powers/swsusp.txt). The mlocked memory can not be swapped. If you need to have so much memory resident you should consider upgrading your memory.

There is nothing to fix in pm-utils, that's all kernel stuff.

Comment 6 Jaroslav Škarvada 2010-09-13 07:27:13 UTC
Not pm-utils bug.