How to debug why 'systemctl hibernate' works, but 'systemctl suspend-then-hibernate' not?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
My current setup:
- Ubuntu 18.04.1
- Encrypted partition with an LVM2 on it.
- LMV
- root (/dev/mapper/it--vg-root)
- swap (/dev/mapper/it--vg-swap_1)
- Random cryptswap that maps to /dev/dm-3, whatever that might be, that seems to be gone now.
What have I done:
- Changed the swap for the system to
/dev/mapper/it--vg-swap_1via fstab - Changed the UUID in
/etc/initramfs-tools/conf.d/resumeto the new swap partition and ransudo update-initramfs -u
- Added
resume=UUID=XXXXXXXtoGRUB_CMDLINE_LINUX_DEFAULT=variable with the UUID of the new swap partition and ransudo update-grub
- I created a file
/etc/systemd/sleep.confwith the following content:
[Sleep]
HibernateDelaySec=10
- I rebooted the whole system
Then I tested two cases:
systemctl hibernate
The system goes to hibernation properly. It boots back up, asks me for the decryption password and opens up all the windows and applications that I had open before.
systemctl suspend-then-hibernate
The systemd goes to suspend mode. My power key indicates that by blinking.
After around ten seconds (mind the config in sleep.conf) it turns back on and the screen goes to a blinking terminal cursor.
Then it goes down to what seems to be hibernation.
No indications that the system is still on. After pressing the power button the system comes back up, asking for the encryption key and continues to boot like it should after I typed it in.
After logging in all previously opened applications are not open anymore. Everything is closed and lost.
It seems like the computer was either shut down completely or the ram that was dumped after suspension was in fact empty, because the suspension already dumped it to the swap partition.
But those are just random theories.
My question is: how would I be able to debug this problem and find the problem?
If you have an answer to why this happening, I would take that, too :)
18.04 suspend hibernate
asked Feb 9 at 21:27
func0derfunc0der
1066
add a comment |
My current setup:
- Ubuntu 18.04.1
- Encrypted partition with an LVM2 on it.
- LMV
- root (/dev/mapper/it--vg-root)
- swap (/dev/mapper/it--vg-swap_1)
- Random cryptswap that maps to /dev/dm-3, whatever that might be, that seems to be gone now.
What have I done:
- Changed the swap for the system to
/dev/mapper/it--vg-swap_1via fstab - Changed the UUID in
/etc/initramfs-tools/conf.d/resumeto the new swap partition and ransudo update-initramfs -u
- Added
resume=UUID=XXXXXXXtoGRUB_CMDLINE_LINUX_DEFAULT=variable with the UUID of the new swap partition and ransudo update-grub
- I created a file
/etc/systemd/sleep.confwith the following content:
[Sleep]
HibernateDelaySec=10
- I rebooted the whole system
Then I tested two cases:
systemctl hibernate
The system goes to hibernation properly. It boots back up, asks me for the decryption password and opens up all the windows and applications that I had open before.
systemctl suspend-then-hibernate
The systemd goes to suspend mode. My power key indicates that by blinking.
After around ten seconds (mind the config in sleep.conf) it turns back on and the screen goes to a blinking terminal cursor.
Then it goes down to what seems to be hibernation.
No indications that the system is still on. After pressing the power button the system comes back up, asking for the encryption key and continues to boot like it should after I typed it in.
After logging in all previously opened applications are not open anymore. Everything is closed and lost.
It seems like the computer was either shut down completely or the ram that was dumped after suspension was in fact empty, because the suspension already dumped it to the swap partition.
But those are just random theories.
My question is: how would I be able to debug this problem and find the problem?
If you have an answer to why this happening, I would take that, too :)
18.04 suspend hibernate
asked Feb 9 at 21:27
func0derfunc0der
1066
@Terrance I ran it without-k all(update my question). But I only use one kernel, so that should be fine. I'll try it anyway ;)
– func0der
Feb 9 at 21:39
That shouldn't matter then. It only will apply to the running kernel. You just didn't have it at the time of my comment. I have all the settings correct on my system and thesuspend-then-hibernatecauses a massive non-responsive host to me. Wonder if it is a bug.
– Terrance
Feb 9 at 21:45
Tried it. Sadly it did not make any difference. Though my system responses fine for me.
– func0der
Feb 9 at 21:49
add a comment |
My current setup:
- Ubuntu 18.04.1
- Encrypted partition with an LVM2 on it.
- LMV
- root (/dev/mapper/it--vg-root)
- swap (/dev/mapper/it--vg-swap_1)
- Random cryptswap that maps to /dev/dm-3, whatever that might be, that seems to be gone now.
What have I done:
- Changed the swap for the system to
/dev/mapper/it--vg-swap_1via fstab - Changed the UUID in
/etc/initramfs-tools/conf.d/resumeto the new swap partition and ransudo update-initramfs -u
- Added
resume=UUID=XXXXXXXtoGRUB_CMDLINE_LINUX_DEFAULT=variable with the UUID of the new swap partition and ransudo update-grub
- I created a file
/etc/systemd/sleep.confwith the following content:
[Sleep]
HibernateDelaySec=10
- I rebooted the whole system
Then I tested two cases:
systemctl hibernate
The system goes to hibernation properly. It boots back up, asks me for the decryption password and opens up all the windows and applications that I had open before.
systemctl suspend-then-hibernate
The systemd goes to suspend mode. My power key indicates that by blinking.
After around ten seconds (mind the config in sleep.conf) it turns back on and the screen goes to a blinking terminal cursor.
Then it goes down to what seems to be hibernation.
No indications that the system is still on. After pressing the power button the system comes back up, asking for the encryption key and continues to boot like it should after I typed it in.
After logging in all previously opened applications are not open anymore. Everything is closed and lost.
It seems like the computer was either shut down completely or the ram that was dumped after suspension was in fact empty, because the suspension already dumped it to the swap partition.
But those are just random theories.
My question is: how would I be able to debug this problem and find the problem?
If you have an answer to why this happening, I would take that, too :)
18.04 suspend hibernate
asked Feb 9 at 21:27
func0derfunc0der
1066
My current setup:
- Ubuntu 18.04.1
- Encrypted partition with an LVM2 on it.
- LMV
- root (/dev/mapper/it--vg-root)
- swap (/dev/mapper/it--vg-swap_1)
- Random cryptswap that maps to /dev/dm-3, whatever that might be, that seems to be gone now.
What have I done:
- Changed the swap for the system to
/dev/mapper/it--vg-swap_1via fstab - Changed the UUID in
/etc/initramfs-tools/conf.d/resumeto the new swap partition and ransudo update-initramfs -u
- Added
resume=UUID=XXXXXXXtoGRUB_CMDLINE_LINUX_DEFAULT=variable with the UUID of the new swap partition and ransudo update-grub
- I created a file
/etc/systemd/sleep.confwith the following content:
[Sleep]
HibernateDelaySec=10
- I rebooted the whole system
Then I tested two cases:
systemctl hibernate
The system goes to hibernation properly. It boots back up, asks me for the decryption password and opens up all the windows and applications that I had open before.
systemctl suspend-then-hibernate
The systemd goes to suspend mode. My power key indicates that by blinking.
After around ten seconds (mind the config in sleep.conf) it turns back on and the screen goes to a blinking terminal cursor.
Then it goes down to what seems to be hibernation.
No indications that the system is still on. After pressing the power button the system comes back up, asking for the encryption key and continues to boot like it should after I typed it in.
After logging in all previously opened applications are not open anymore. Everything is closed and lost.
It seems like the computer was either shut down completely or the ram that was dumped after suspension was in fact empty, because the suspension already dumped it to the swap partition.
But those are just random theories.
My question is: how would I be able to debug this problem and find the problem?
If you have an answer to why this happening, I would take that, too :)
18.04 suspend hibernate
18.04 suspend hibernate
asked Feb 9 at 21:27
func0derfunc0der
1066
asked Feb 9 at 21:27
func0derfunc0der
1066
edited Feb 9 at 21:38
func0der
asked Feb 9 at 21:27
func0derfunc0der
1066
asked Feb 9 at 21:27
func0derfunc0der
1066
asked Feb 9 at 21:27
func0derfunc0der
1066
1066
@Terrance I ran it without-k all(update my question). But I only use one kernel, so that should be fine. I'll try it anyway ;)
– func0der
Feb 9 at 21:39
That shouldn't matter then. It only will apply to the running kernel. You just didn't have it at the time of my comment. I have all the settings correct on my system and thesuspend-then-hibernatecauses a massive non-responsive host to me. Wonder if it is a bug.
– Terrance
Feb 9 at 21:45
Tried it. Sadly it did not make any difference. Though my system responses fine for me.
– func0der
Feb 9 at 21:49
add a comment |
@Terrance I ran it without-k all(update my question). But I only use one kernel, so that should be fine. I'll try it anyway ;)
– func0der
Feb 9 at 21:39
That shouldn't matter then. It only will apply to the running kernel. You just didn't have it at the time of my comment. I have all the settings correct on my system and thesuspend-then-hibernatecauses a massive non-responsive host to me. Wonder if it is a bug.
– Terrance
Feb 9 at 21:45
Tried it. Sadly it did not make any difference. Though my system responses fine for me.
– func0der
Feb 9 at 21:49
@Terrance I ran it without
-k all (update my question). But I only use one kernel, so that should be fine. I'll try it anyway ;)– func0der
Feb 9 at 21:39
@Terrance I ran it without
-k all (update my question). But I only use one kernel, so that should be fine. I'll try it anyway ;)– func0der
Feb 9 at 21:39
That shouldn't matter then. It only will apply to the running kernel. You just didn't have it at the time of my comment. I have all the settings correct on my system and the
suspend-then-hibernate causes a massive non-responsive host to me. Wonder if it is a bug.– Terrance
Feb 9 at 21:45
That shouldn't matter then. It only will apply to the running kernel. You just didn't have it at the time of my comment. I have all the settings correct on my system and the
suspend-then-hibernate causes a massive non-responsive host to me. Wonder if it is a bug.– Terrance
Feb 9 at 21:45
Tried it. Sadly it did not make any difference. Though my system responses fine for me.
– func0der
Feb 9 at 21:49
Tried it. Sadly it did not make any difference. Though my system responses fine for me.
– func0der
Feb 9 at 21:49
add a comment |
0
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',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117004%2fhow-to-debug-why-systemctl-hibernate-works-but-systemctl-suspend-then-hibern%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Ask Ubuntu!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1117004%2fhow-to-debug-why-systemctl-hibernate-works-but-systemctl-suspend-then-hibern%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
@Terrance I ran it without
-k all(update my question). But I only use one kernel, so that should be fine. I'll try it anyway ;)– func0der
Feb 9 at 21:39
That shouldn't matter then. It only will apply to the running kernel. You just didn't have it at the time of my comment. I have all the settings correct on my system and the
suspend-then-hibernatecauses a massive non-responsive host to me. Wonder if it is a bug.– Terrance
Feb 9 at 21:45
Tried it. Sadly it did not make any difference. Though my system responses fine for me.
– func0der
Feb 9 at 21:49