I recently upgraded my netbook to the kernel 4.14.62 in -current and experienced problems with resume from hibernate. On resume, the boot process proceeds to loading the image, gives a message about suspending consoles then stalls before re-initiating with a cold boot. I see no problem with suspend to RAM. I have since reverted to the last known working kernel 4.14.56 and the problem has gone away. Unfortunately, I had avoided upgrading this device with the kernel versions released for -current between 4.14.56 and kernel 4.14.62, as I had a need to maintain a stable system without possible side effects that can arise from other upgrades (I am looking at you, boost). So I have no further information on exactly where this problem arose.
Has anybody else seen this, or am I seeing a corner case due to my particular hardware?

I have an Acer Aspire E5-475-37MN, Slackware64-current with Eric's Plasma 5. I have a 2GB swap. I normally don't use hibernation. Suspend has been working great.

I was holding up on installing the latest updates but, In the spirit of testing. I setup for resume (in lilo.conf) from hibernation and upgraded the kernel from 4.14.61 to 4.14.62. I start the process from within Plasma 5, hibernation is not available from the context menu "< Leave...", but is from the Application Launcher. (Any one know how to make it available from the desktop context menu). I also set it up to hibernate when the laptop lid is closed.

Hibernation is working here no issues.

2 members found this post helpful.

Thanks for the feedback. Good to know that others are happy.
More homework at my end required :-).

I just updated my thinkpad T440, hibernate works fine for me. (Suspend works too)

1 members found this post helpful.

According to information found, there is a conflict between 32-bit kernels and kASLR. It was said: a) that one result of this conflict is the inability to resume from hibernation, b) issuing the kernel boot option "nokaslr" eliminates the conflict.

Based on a sample of two 32-bit computers, 100% of them demonstrated --> with the "nokaslr" boot option it is possible to resume from hibernation. One of these computers was running the 4.19.26-smp kernel.

-------------------------------

According to one article[1], the kASLR kernel option has been available since kernel 3.14 was released, and it was turned on by default at about the time kernel 4.12 was released.

So, is it a problem to not run kASLR?

Apparently the ASLR ability was developed to enhance computer security, but at least some articles[1][2] say it is weak and/or useless.

1. "http://www.daniloaz.com/en/differences-between-aslr-kaslr-and-karl/"

2. "http://forums.grsecurity.net/viewtopic.php?f=7&t=3367"