Created attachment 306609 [details] Suspend configuration Almost every time I hibernate my PC while firefox is working, the hibernate freezes on "Snapshotting system..." (I'm running hibernate with splash) If firefox is down, hibernation works well. Hibernate-Ram works very well. My kernel version is 3.2.1-gentoo-r2, but the problem appeared also with previous kernels. I am using the userspace software suspend (version 0.8-r1). I attach the configuration files and the output of emerge --info. Thanks
Created attachment 306611 [details] Hibernate configuration
Created attachment 306613 [details] Output of emerge --info
Hello, please turn of the splash screen for future tests - maybe some usefull information got hidden. Do you have as many swap space as real ram? Please post me the output of `free` which displays the amount of ram and the swap size. Linux just safes used memory pages, which enables speedups during suspend and the possibility of suspending 4GB Ram on a 2GB swap partition (i.e. my notebook), but that only works if my used RAM (after compression) fits on the swap space. Thanks
Hello Michael, I made new tries without splash, but no useful information appears. In my tries, hibernate always freeze on "s2disk: Snapshotting system..." when there are Mozilla application running (Firefox or Thunderbird), but everything works without any problem when I hibernated before starting these applications. My swap partition is large as twice the ram size, so I think the problem is not related to the size of the swap partition. Here is the output of free (this is taken just before an unsuccessful hibernation). total used free shared buffers cached Mem: 1032728 927104 105624 0 55976 406612 -/+ buffers/cache: 464516 568212 Swap: 2104508 0 2104508 I also tried to increase the log verbosity in /etc/hibernate/common.conf, but this turns out be not useful since the freeze does not concern the hibernate_scripts, but the s2disk command. Let me know if you need anything else. Thanks
Hello, is this still an issue with suspend-1.0_p20150622?
No, it is not
Ok, closing then.