Laptop fails to resume from hibernation (suspend to disk) after update to 18.04

The name of the pictureThe name of the pictureThe name of the pictureClash Royale CLAN TAG#URR8PPP








up vote
3
down vote

favorite












For the beginning i say, that hibernation worked perfect on 17.10 on my hardware, and it doesn't look to me as a hardware problem now. Now when i'm putting my laptop to hibernation either by systemctl hibernate or hibernate it does write memory content somewhere on the disk, but while i'm starting it again, it looks like the kernel or initrd can't find the proper hibernation image. What i tried:



Put RESUME=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f into my /etc/initramfs-tools/conf.d/resume, and do update-initramfs -u, this actually made things worse, because it just made the boot slower and i had to wait until it will say "giving up on resume" or something like that. The UUID is correct, i checked with blkid, and i use this as a swap partition, checked with swapon --show.



I tried to remove it from /etc/initramfs-tools/conf.d/resume and add resume=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f to /etc/default/grub, and do update-grub, and also checked that it has been passed to kernel by cat /proc/cmdline, but also no luck. So how can I make ubuntu 18.04 resume after suspend? Or at least how can i debug issue more, to find out what's the problem exactly?







share|improve this question






















  • It's probably a kernel bug. Have you tried booting with previous kernels? Hold shift after the startup and select a previous kernel to start with. If hibernation worked on that remove the new kernel and kernel header.
    – Sadegh Ghasemi
    May 13 at 6:12










  • Well, i will try, but what setup should i use? the /etc/initramfs-tools/conf.d/resume, or kerel cmdline? U use 4.17.0-rc4 kernel.
    – user2819650
    May 13 at 7:46










  • @SadeghGhasemi, trying other kernels didn't help, i think the bug is somewhere in initramfs-tools, maybe it looks for hibernate image somewhere else, but i have no idea how to debug it.
    – user2819650
    May 13 at 13:47






  • 1




    Did you try adding resume=/dev/your/swap/path/here to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? (don’t forget to run update-grub after) I had the same problem as you, and that’s all I needed to do to get hibernate working in 18.04 (other than making my swap partition large enough).
    – Steve
    May 13 at 16:29











  • yes, i tried. Also, what hibernation software should i use? systemctl hibernate? hibernate? pm-hibernate? Which one? Or they all doing the same?What do you mean by large enough? I have 16gb of memory, but 8gb of swap, but it wasn't the issue for resuming before, all it may do - not to suspend, if swap isn't enough, bot now it goes to suspend and never resumes.
    – user2819650
    May 14 at 2:08














up vote
3
down vote

favorite












For the beginning i say, that hibernation worked perfect on 17.10 on my hardware, and it doesn't look to me as a hardware problem now. Now when i'm putting my laptop to hibernation either by systemctl hibernate or hibernate it does write memory content somewhere on the disk, but while i'm starting it again, it looks like the kernel or initrd can't find the proper hibernation image. What i tried:



Put RESUME=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f into my /etc/initramfs-tools/conf.d/resume, and do update-initramfs -u, this actually made things worse, because it just made the boot slower and i had to wait until it will say "giving up on resume" or something like that. The UUID is correct, i checked with blkid, and i use this as a swap partition, checked with swapon --show.



I tried to remove it from /etc/initramfs-tools/conf.d/resume and add resume=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f to /etc/default/grub, and do update-grub, and also checked that it has been passed to kernel by cat /proc/cmdline, but also no luck. So how can I make ubuntu 18.04 resume after suspend? Or at least how can i debug issue more, to find out what's the problem exactly?







share|improve this question






















  • It's probably a kernel bug. Have you tried booting with previous kernels? Hold shift after the startup and select a previous kernel to start with. If hibernation worked on that remove the new kernel and kernel header.
    – Sadegh Ghasemi
    May 13 at 6:12










  • Well, i will try, but what setup should i use? the /etc/initramfs-tools/conf.d/resume, or kerel cmdline? U use 4.17.0-rc4 kernel.
    – user2819650
    May 13 at 7:46










  • @SadeghGhasemi, trying other kernels didn't help, i think the bug is somewhere in initramfs-tools, maybe it looks for hibernate image somewhere else, but i have no idea how to debug it.
    – user2819650
    May 13 at 13:47






  • 1




    Did you try adding resume=/dev/your/swap/path/here to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? (don’t forget to run update-grub after) I had the same problem as you, and that’s all I needed to do to get hibernate working in 18.04 (other than making my swap partition large enough).
    – Steve
    May 13 at 16:29











  • yes, i tried. Also, what hibernation software should i use? systemctl hibernate? hibernate? pm-hibernate? Which one? Or they all doing the same?What do you mean by large enough? I have 16gb of memory, but 8gb of swap, but it wasn't the issue for resuming before, all it may do - not to suspend, if swap isn't enough, bot now it goes to suspend and never resumes.
    – user2819650
    May 14 at 2:08












up vote
3
down vote

favorite









up vote
3
down vote

favorite











For the beginning i say, that hibernation worked perfect on 17.10 on my hardware, and it doesn't look to me as a hardware problem now. Now when i'm putting my laptop to hibernation either by systemctl hibernate or hibernate it does write memory content somewhere on the disk, but while i'm starting it again, it looks like the kernel or initrd can't find the proper hibernation image. What i tried:



Put RESUME=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f into my /etc/initramfs-tools/conf.d/resume, and do update-initramfs -u, this actually made things worse, because it just made the boot slower and i had to wait until it will say "giving up on resume" or something like that. The UUID is correct, i checked with blkid, and i use this as a swap partition, checked with swapon --show.



I tried to remove it from /etc/initramfs-tools/conf.d/resume and add resume=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f to /etc/default/grub, and do update-grub, and also checked that it has been passed to kernel by cat /proc/cmdline, but also no luck. So how can I make ubuntu 18.04 resume after suspend? Or at least how can i debug issue more, to find out what's the problem exactly?







share|improve this question














For the beginning i say, that hibernation worked perfect on 17.10 on my hardware, and it doesn't look to me as a hardware problem now. Now when i'm putting my laptop to hibernation either by systemctl hibernate or hibernate it does write memory content somewhere on the disk, but while i'm starting it again, it looks like the kernel or initrd can't find the proper hibernation image. What i tried:



Put RESUME=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f into my /etc/initramfs-tools/conf.d/resume, and do update-initramfs -u, this actually made things worse, because it just made the boot slower and i had to wait until it will say "giving up on resume" or something like that. The UUID is correct, i checked with blkid, and i use this as a swap partition, checked with swapon --show.



I tried to remove it from /etc/initramfs-tools/conf.d/resume and add resume=UUID=cac3c850-bc33-44ab-adb4-41dcb5403e6f to /etc/default/grub, and do update-grub, and also checked that it has been passed to kernel by cat /proc/cmdline, but also no luck. So how can I make ubuntu 18.04 resume after suspend? Or at least how can i debug issue more, to find out what's the problem exactly?









share|improve this question













share|improve this question




share|improve this question








edited May 14 at 2:50

























asked May 13 at 3:33









user2819650

14616




14616











  • It's probably a kernel bug. Have you tried booting with previous kernels? Hold shift after the startup and select a previous kernel to start with. If hibernation worked on that remove the new kernel and kernel header.
    – Sadegh Ghasemi
    May 13 at 6:12










  • Well, i will try, but what setup should i use? the /etc/initramfs-tools/conf.d/resume, or kerel cmdline? U use 4.17.0-rc4 kernel.
    – user2819650
    May 13 at 7:46










  • @SadeghGhasemi, trying other kernels didn't help, i think the bug is somewhere in initramfs-tools, maybe it looks for hibernate image somewhere else, but i have no idea how to debug it.
    – user2819650
    May 13 at 13:47






  • 1




    Did you try adding resume=/dev/your/swap/path/here to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? (don’t forget to run update-grub after) I had the same problem as you, and that’s all I needed to do to get hibernate working in 18.04 (other than making my swap partition large enough).
    – Steve
    May 13 at 16:29











  • yes, i tried. Also, what hibernation software should i use? systemctl hibernate? hibernate? pm-hibernate? Which one? Or they all doing the same?What do you mean by large enough? I have 16gb of memory, but 8gb of swap, but it wasn't the issue for resuming before, all it may do - not to suspend, if swap isn't enough, bot now it goes to suspend and never resumes.
    – user2819650
    May 14 at 2:08
















  • It's probably a kernel bug. Have you tried booting with previous kernels? Hold shift after the startup and select a previous kernel to start with. If hibernation worked on that remove the new kernel and kernel header.
    – Sadegh Ghasemi
    May 13 at 6:12










  • Well, i will try, but what setup should i use? the /etc/initramfs-tools/conf.d/resume, or kerel cmdline? U use 4.17.0-rc4 kernel.
    – user2819650
    May 13 at 7:46










  • @SadeghGhasemi, trying other kernels didn't help, i think the bug is somewhere in initramfs-tools, maybe it looks for hibernate image somewhere else, but i have no idea how to debug it.
    – user2819650
    May 13 at 13:47






  • 1




    Did you try adding resume=/dev/your/swap/path/here to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? (don’t forget to run update-grub after) I had the same problem as you, and that’s all I needed to do to get hibernate working in 18.04 (other than making my swap partition large enough).
    – Steve
    May 13 at 16:29











  • yes, i tried. Also, what hibernation software should i use? systemctl hibernate? hibernate? pm-hibernate? Which one? Or they all doing the same?What do you mean by large enough? I have 16gb of memory, but 8gb of swap, but it wasn't the issue for resuming before, all it may do - not to suspend, if swap isn't enough, bot now it goes to suspend and never resumes.
    – user2819650
    May 14 at 2:08















It's probably a kernel bug. Have you tried booting with previous kernels? Hold shift after the startup and select a previous kernel to start with. If hibernation worked on that remove the new kernel and kernel header.
– Sadegh Ghasemi
May 13 at 6:12




It's probably a kernel bug. Have you tried booting with previous kernels? Hold shift after the startup and select a previous kernel to start with. If hibernation worked on that remove the new kernel and kernel header.
– Sadegh Ghasemi
May 13 at 6:12












Well, i will try, but what setup should i use? the /etc/initramfs-tools/conf.d/resume, or kerel cmdline? U use 4.17.0-rc4 kernel.
– user2819650
May 13 at 7:46




Well, i will try, but what setup should i use? the /etc/initramfs-tools/conf.d/resume, or kerel cmdline? U use 4.17.0-rc4 kernel.
– user2819650
May 13 at 7:46












@SadeghGhasemi, trying other kernels didn't help, i think the bug is somewhere in initramfs-tools, maybe it looks for hibernate image somewhere else, but i have no idea how to debug it.
– user2819650
May 13 at 13:47




@SadeghGhasemi, trying other kernels didn't help, i think the bug is somewhere in initramfs-tools, maybe it looks for hibernate image somewhere else, but i have no idea how to debug it.
– user2819650
May 13 at 13:47




1




1




Did you try adding resume=/dev/your/swap/path/here to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? (don’t forget to run update-grub after) I had the same problem as you, and that’s all I needed to do to get hibernate working in 18.04 (other than making my swap partition large enough).
– Steve
May 13 at 16:29





Did you try adding resume=/dev/your/swap/path/here to GRUB_CMDLINE_LINUX_DEFAULT in /etc/default/grub? (don’t forget to run update-grub after) I had the same problem as you, and that’s all I needed to do to get hibernate working in 18.04 (other than making my swap partition large enough).
– Steve
May 13 at 16:29













yes, i tried. Also, what hibernation software should i use? systemctl hibernate? hibernate? pm-hibernate? Which one? Or they all doing the same?What do you mean by large enough? I have 16gb of memory, but 8gb of swap, but it wasn't the issue for resuming before, all it may do - not to suspend, if swap isn't enough, bot now it goes to suspend and never resumes.
– user2819650
May 14 at 2:08




yes, i tried. Also, what hibernation software should i use? systemctl hibernate? hibernate? pm-hibernate? Which one? Or they all doing the same?What do you mean by large enough? I have 16gb of memory, but 8gb of swap, but it wasn't the issue for resuming before, all it may do - not to suspend, if swap isn't enough, bot now it goes to suspend and never resumes.
– user2819650
May 14 at 2:08















active

oldest

votes











Your Answer







StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "89"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);

else
createEditor();

);

function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
convertImagesToLinks: true,
noModals: false,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);



);








 

draft saved


draft discarded


















StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035564%2flaptop-fails-to-resume-from-hibernation-suspend-to-disk-after-update-to-18-04%23new-answer', 'question_page');

);

Post as a guest



































active

oldest

votes













active

oldest

votes









active

oldest

votes






active

oldest

votes










 

draft saved


draft discarded


























 


draft saved


draft discarded














StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1035564%2flaptop-fails-to-resume-from-hibernation-suspend-to-disk-after-update-to-18-04%23new-answer', 'question_page');

);

Post as a guest













































































Popular posts from this blog

pylint3 and pip3 broken

Missing snmpget and snmpwalk

How to enroll fingerprints to Ubuntu 17.10 with VFS491