[SOLVED] Hibernation not working on Linux Mint 19

basilky · 12-30-2018, 10:38 PM

I'm currently on Linux Mint 19.1 and it uses swap file by default instead of swap partition. Everything including suspend works fine. But resume after hibernation is not working. I have following configuration in my /etc/default/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash resume=UUID=38c97b08-a1d5-44b5-9e96-afca13595fe2 resume_offset=27854848"

where UUID is the root partition where swap file belongs and resume_offset is the offset of the swap file. System successfully hibernates. But on the next boot, it shows resuming from the UUID location and suddenly screen goes blank( https://youtu.be/ZFBHNfYhuUs ). There is no response from the system after that.I have gone through the following threads and nothing seems to work.

https://askubuntu.com/questions/1034185
https://askubuntu.com/questions/1053134

Complete system details can be found at https://termbin.com/nqpw

I have secure boot disabled and currently on kernel 4.18. Does anyone have success with hibernation using swap file or any idea on why hibernation not working?

polytropos · 12-31-2018, 08:08 AM

I got resume from a swap file working fine on ArchLinux. (Though right now I am resuming from a swap partition on Gentoo.) To resume from a swap file, I used the method mentioned in these links: https://wiki.archlinux.org/index.php...nel_parameters and https://wiki.archlinux.org/index.php/Swap#Swap_file

I don't know much about Linux Mint, but the first step in troubleshooting would be: can you resume from a swap partition?

But even before that, do your syslog files have anything to say about the hibernation? It would probably be in /var/log/messages or /var/log/syslog, or something similar. By the way, you don't know that the hibernation was successful until you have successfully resumed from it!

jsbjsb001 · 12-31-2018, 08:35 AM

I had a similar problem which after many months tracked to a failing drive. I'm not saying that this is the problem in your case, but it's how I put the pieces together that may well help you find the cause of your problem.

What I did was run the following command below which gave me my first clue (I didn't put it all together at the time, but looking back on it, it was a critical clue that ultimately helped me find and pinpoint the reason for my problem);

Code:

echo disk > /sys/power/state

It was the error message displayed that gave me my biggest clue looking back - something about it not being able to get an interrupt for the failing drive. It was the common thread (the drive failing on interrupts) among the other related problems I was also having as a result. Adding kernel parameters did help, but it didn't fix it completely.

Go through the link below and see if you can pinpoint, or at least narrow down the suspects.

https://01.org/blogs/rzhang/2015/bes...bernate-issues

basilky · 12-31-2018, 01:56 PM

Thanks for the replies.

@jsbjsb001
I don't think this is an issue with my drive. The command

Code:

echo disk > /sys/power/state

hibernates the system. But on the resume, the screen goes blank as usual.

@polytropos
I just deleted /var/log/syslog and done hibernation again. I'm attaching the newly generated syslog file (renamed to syslog.txt). My laptop is having nvidia mx150 graphics card. Is this something related with the issue? Also, the following Arch thread suggests to change boot hooks order.

Black Screen after resume from hibernation

Not sure how to do that in Ubuntu based distros.

polytropos · 12-31-2018, 08:20 PM

Hello, the log file you have supplied seems to be for a clean boot, and has no mention of the hibernation. Check the last boot's log file. At it's end it should have lines like:

Dec 30 20:53:17 [acpid] received input layer event "button/power PBTN 00000080 00000000"
Dec 30 20:53:17 [acpid] rule from /etc/acpi/events/default matched
Dec 30 20:53:17 [acpid] executing action "/etc/acpi/default.sh button/power PBTN 00000080 00000000"
Dec 30 20:53:17 [kernel] [13754.109505] PM: hibernation entry
Dec 30 20:53:17 [kernel] [13754.109795] PM: Syncing filesystems ...

(I am using initrc, instead of systemd, on Gentoo, so there may be differences, but there should be a lot of lines supplied by acipd and kernel about the hibernation attempt.)

By the way, a note about the text file. The log files are only of temporary interest, so it is best to paste it somewhere online (like on pastebin.com) and supply the link on the forum. Otherwise, you are just wasting server space. It is even easier to read as they put line numbers and syntax highlighting.

basilky · 12-31-2018, 10:49 PM

The hibernate process is not getting logged at all in syslog. I have also searched for entries in power manager log files and there are no relevant ones. After a bit of searching, I found a bug in lauchpad with same issue as of mine. It says hibernation is broken from kernel 4.13.

hibernation (freezes on resume) since 4.13.0-25.29

It's around one year after reporting and affects multiple users across multiple distributions and still not fixed.

polytropos · 01-01-2019, 04:13 AM

You too could try downgrading the kernel.

basilky · 01-07-2019, 03:40 AM

I have tried downgrading kernel to kernel 4.14, but it lead to kernel panic. Maybe because Ubuntu 18.04 doesn't support it. Also, downgrading kernel is not a great idea. I'm closing this thread as we have nothing to do with and its upon Ubuntu to fix this bug. If somebody also experience this bug, please upvote the following bug report.

hibernation (freezes on resume) since 4.13.0-25.29