I noticed that too since some time. System doesn't hibernate and xorg causes 100% cpu load.

Process with 100% cpu load was

...

/usr/lib/xorg-server/Xorg :0 -seat seat0 -auth /run/lightdm/root:0 -nolisten tcp vt7 -novtswitch

I have the same problem since several months. Suspend to disk causes a blank screen (as supposed to happen) and then freezes the system with 100% cpu load. However, no useful log messages could be found, so I dropped the issue.

Happens on my desktop machine, no matter how I initiate the hibernation. (pm-hibernate, systemctl hibernate, echo "disk" > /sys/power/state)

Two days ago, I started looking into this again. After some adjustments, hibernation works for now. Dropping the solution here in case it helps. The likely culprit seems to be a RAM upgrade from 16 to 32 GiB. During this process, I forgot to adjust my SWAP partition, which was also just 16GB in size.

I use ZFS, which fills a large portion of the RAM with L2ARC data, so that might have been just too big for the swap partition.

TL;DR the size of the swap partition was too small.

Am 22.01.2017 um 14:55 schrieb Andreas Innerlohninger:

In my case it had to do something with lightDM/light-locker. I solved it by switching to gdm.

On Jän 20, Carlchristian Eckert wrote:

...

I have the same problem since several months. Suspend to disk causes a blank screen (as supposed to happen) and then freezes the system with 100% cpu load. However, no useful log messages could be found, so I dropped the issue.

Happens on my desktop machine, no matter how I initiate the hibernation. (pm-hibernate, systemctl hibernate, echo "disk" > /sys/power/state)

Am 31.12.2016 um 13:42 schrieb Bruno Pagani:

Hi,

Le 31 décembre 2016 07:38:05 GMT+01:00, Peter Nabbefeld peter.nabbefeld@gmx.de a écrit :

...

Hello,

since some time, hibernation does not work, dmesg contains following messages:

[ 738.404244] ACPI Warning: _SB.PCI0.PEG0.PEGP._DSM: Argument #4 type

mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95) [ 738.404353] ACPI: _SB_.PCI0.PEG0.PEGP: failed to evaluate _DSM [ 738.404356] ACPI Warning: _SB.PCI0.PEG0.PEGP._DSM: Argument #4 type

mismatch - Found [Buffer], ACPI requires [Package] (20160422/nsarguments-95)

Some time ago, when I closed my laptop, Linux automatically hibernated,

now it does not. As my laptop becomes really warm and I don't want to stress my display, I'm using this rarely, so I cannot tell, since when hibernation doesn't work :-/

Kind regartds Peter

These messages are related to Optimus system (Nvidia implementation of dGPU power management handling is not compliant with ACPI specs). So that’s not related to your hibernation issue.

Hm, I'm using the Nouveau driver - is this message hardware-related?

Regarding this one, I’d like a precision that might be useful: is this about hibernation or suspend?

Hm, I'm usually not distinguishing those. As System doesn't need much time to wake-up, I'd assume it just suspends to RAM - but as computers are getting more power, this is probably not really visible. How can I detect, which mode it had to switch to?

Other than that, what DE do you use if applicable? What does handle lid close event? I had the issue that the lid close event wasn’t handled because KDE PM daemon isn’t inhibiting systemd one correctly, and once fixed it worked again.

Using XFCE. Don't know, what handles the lid close evenet - how can I find that out?

Kind regards Peter

Regarding the difference between hibernation (suspension to disk) and suspension to RAM: Suspension to RAM just means turning off peripherals like disk and display while keeping the RAM on. Thus from your perspective you should just see the screen go black (and hear the disk spin down, if you use a HDD).

Hibernation, on the other hand, is saving the system state to disk and powering off the device, so you should be able to see some messages while powering down, and again during boot up you could see bootloader, initramfs, and kernel messages. There should be a message about the Resume mkinitcpio hook being activated, although it may be gone too quickly for you too see it.

Happy New Year 2017!