Description of problem: Left machine to hibernate overnight and it repeatedly failed. I'll attach the pm-suspend.log that shows the memory allocation failure. If this is useful here is the free report when I got back in: [long@kite tmp]$ free -m total used free shared buffers cached Mem: 7869 7470 398 0 30 3906 -/+ buffers/cache: 3533 4335 Swap: 9999 2172 7827 Version-Release number of selected component (if applicable): pm-utils-1.4.1-18.fc17.x86_64 How reproducible: Not every night Steps to Reproduce: 1. Leave system running to hibernate after 99 minutes 2. 3. Actual results: System was still running next morning Expected results: System was hibernated Additional info:
Created attachment 696574 [details] pm-suspend.log
I think there is not enough free resources to successfully hibernate: RAM used: 7644800 RAM total: 8058092 SWAP used: 2288704 SWAP total: 10239996 You can try to increase your SWAP or free more RAM. Your used RAM + used SWAP needs to fit the SWAP (and it seems to be tight). Also (IMHO) the kernel needs to free 1/2 of you RAM to be able to hibernate. If extensive amount of RAM is mlocked (memory that cannot be swapped) the hibernation may fail.
I would like to revisit this as it happened again last night. The pm-suspend.log says: total used free shared buffers cached Mem: 8058136 7638052 420084 0 16296 4136352 -/+ buffers/cache: 3485404 4572732 Swap: 10239996 1167432 9072564 That says I have 9072564 of free swap which is more than enough to store RAM. I also have 4572732 of free RAM if buffers/cache are thrown away which is more than half my total of RAM. So I should be meeting all of the conditions for hibernation? Or can buffers/cache be mlocked? Should pm-suspend.log show how much memory is mlocked when it runs?
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. 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 '17'. 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 17'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 17 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 to Fedora 17's end of life. 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 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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.