Computer can not enter suspend mode, freezes instead (ubuntu 18)
My problem is similar to this one: Ubuntu 18.04, my PC doesn't enter sleep mode. I will try to provide a bit more details.
When I try to suspend the computer (by closing the lid, pushing the power button or using keyboard shortcut), it has a good chance of not working. Sometimes it works fine, but it is maybe one time out of ten. Here is what happens when it does not work:
- First, the displays turn off. My screen is black, but the computer does not enter sleep mode (the fans are turning, the LEDs are on...)
- When I move the mouse or press a key, the screens turns on again. I can see the battery icon and the "application" icon (top right and top left of screen), but can not see the task bar. My wallpaper is also missing, replaced by only purple. Cursor moves but clicks have no effects.
- Ctrl-Alt-F1 prompts the login screen, but I am back to the previous situation after entering my credentials.
- I could enter a terminal session (ctrl-alt-F3 for instance) and log in. I then tried to use the "shutdown" or "reboot" commands, but both output the message "Failed to power off/reboot system via logind: there's already a shutdown or sleep operation in progress"
- Using shutdown -c does not seem to work on this "sleep operation in progress"
- When I try "sudo shutdown -f", the terminal freezes (does not ask for password) and I have to maintain power button to shut down. It actually does it even if I only type "sudo".
- If I try "startx", the screen turns black for 30 seconds more or less then comes back to the terminal session.
Eventually the only way I have to reboot is to maintain power button to force shutdown.
My configuration : MSI GS60 with Ubuntu 18.04 64bit, Intel® Core™ i7-4720HQ CPU @ 2.60GHz × 8, Intel® Haswell Mobile (graphic chipset). I also have a Nvidia 970M, but I deactivated it (I only use it on windows). I have a dual boot with windows 10. edit: 16G RAM
Thanks in advance for any solution one could provide :)
suspend 18.04
add a comment |
My problem is similar to this one: Ubuntu 18.04, my PC doesn't enter sleep mode. I will try to provide a bit more details.
When I try to suspend the computer (by closing the lid, pushing the power button or using keyboard shortcut), it has a good chance of not working. Sometimes it works fine, but it is maybe one time out of ten. Here is what happens when it does not work:
- First, the displays turn off. My screen is black, but the computer does not enter sleep mode (the fans are turning, the LEDs are on...)
- When I move the mouse or press a key, the screens turns on again. I can see the battery icon and the "application" icon (top right and top left of screen), but can not see the task bar. My wallpaper is also missing, replaced by only purple. Cursor moves but clicks have no effects.
- Ctrl-Alt-F1 prompts the login screen, but I am back to the previous situation after entering my credentials.
- I could enter a terminal session (ctrl-alt-F3 for instance) and log in. I then tried to use the "shutdown" or "reboot" commands, but both output the message "Failed to power off/reboot system via logind: there's already a shutdown or sleep operation in progress"
- Using shutdown -c does not seem to work on this "sleep operation in progress"
- When I try "sudo shutdown -f", the terminal freezes (does not ask for password) and I have to maintain power button to shut down. It actually does it even if I only type "sudo".
- If I try "startx", the screen turns black for 30 seconds more or less then comes back to the terminal session.
Eventually the only way I have to reboot is to maintain power button to force shutdown.
My configuration : MSI GS60 with Ubuntu 18.04 64bit, Intel® Core™ i7-4720HQ CPU @ 2.60GHz × 8, Intel® Haswell Mobile (graphic chipset). I also have a Nvidia 970M, but I deactivated it (I only use it on windows). I have a dual boot with windows 10. edit: 16G RAM
Thanks in advance for any solution one could provide :)
suspend 18.04
Hi, could you provide some additional information? First, did you set up a swap partition? If so, how large is it? I think for suspend to disk to work your swap must be active and at least as large as the amount of ram that you have. Run the command swapon and paste the output. Some of the other errata you're seeing seem to indicate you might have a bad ACPI config. Unfortunately, those are closed source and vendor locked :(
– guyfleeman
May 22 '18 at 20:15
Hi, yes I do have a swap, here is the output of swapon : NAME TYPE SIZE USED PRIO /dev/sda5 partition 6,5G 0B -2
– Philippe Cotte
May 23 '18 at 8:28
Are you trying to suspend to RAM or to disk? If it's to disk you need more swap space.
– guyfleeman
May 23 '18 at 18:56
I have the same issue I believe, compared to Ubuntu 17.10 the new version is very unstable. I'm thinking of installing 17.10 again.
– szx
Jun 18 '18 at 14:05
@guyfleeman Your tip seems to have helped OP to solve the problem. Consider posting an answer.
– Melebius
Jan 8 at 9:35
add a comment |
My problem is similar to this one: Ubuntu 18.04, my PC doesn't enter sleep mode. I will try to provide a bit more details.
When I try to suspend the computer (by closing the lid, pushing the power button or using keyboard shortcut), it has a good chance of not working. Sometimes it works fine, but it is maybe one time out of ten. Here is what happens when it does not work:
- First, the displays turn off. My screen is black, but the computer does not enter sleep mode (the fans are turning, the LEDs are on...)
- When I move the mouse or press a key, the screens turns on again. I can see the battery icon and the "application" icon (top right and top left of screen), but can not see the task bar. My wallpaper is also missing, replaced by only purple. Cursor moves but clicks have no effects.
- Ctrl-Alt-F1 prompts the login screen, but I am back to the previous situation after entering my credentials.
- I could enter a terminal session (ctrl-alt-F3 for instance) and log in. I then tried to use the "shutdown" or "reboot" commands, but both output the message "Failed to power off/reboot system via logind: there's already a shutdown or sleep operation in progress"
- Using shutdown -c does not seem to work on this "sleep operation in progress"
- When I try "sudo shutdown -f", the terminal freezes (does not ask for password) and I have to maintain power button to shut down. It actually does it even if I only type "sudo".
- If I try "startx", the screen turns black for 30 seconds more or less then comes back to the terminal session.
Eventually the only way I have to reboot is to maintain power button to force shutdown.
My configuration : MSI GS60 with Ubuntu 18.04 64bit, Intel® Core™ i7-4720HQ CPU @ 2.60GHz × 8, Intel® Haswell Mobile (graphic chipset). I also have a Nvidia 970M, but I deactivated it (I only use it on windows). I have a dual boot with windows 10. edit: 16G RAM
Thanks in advance for any solution one could provide :)
suspend 18.04
My problem is similar to this one: Ubuntu 18.04, my PC doesn't enter sleep mode. I will try to provide a bit more details.
When I try to suspend the computer (by closing the lid, pushing the power button or using keyboard shortcut), it has a good chance of not working. Sometimes it works fine, but it is maybe one time out of ten. Here is what happens when it does not work:
- First, the displays turn off. My screen is black, but the computer does not enter sleep mode (the fans are turning, the LEDs are on...)
- When I move the mouse or press a key, the screens turns on again. I can see the battery icon and the "application" icon (top right and top left of screen), but can not see the task bar. My wallpaper is also missing, replaced by only purple. Cursor moves but clicks have no effects.
- Ctrl-Alt-F1 prompts the login screen, but I am back to the previous situation after entering my credentials.
- I could enter a terminal session (ctrl-alt-F3 for instance) and log in. I then tried to use the "shutdown" or "reboot" commands, but both output the message "Failed to power off/reboot system via logind: there's already a shutdown or sleep operation in progress"
- Using shutdown -c does not seem to work on this "sleep operation in progress"
- When I try "sudo shutdown -f", the terminal freezes (does not ask for password) and I have to maintain power button to shut down. It actually does it even if I only type "sudo".
- If I try "startx", the screen turns black for 30 seconds more or less then comes back to the terminal session.
Eventually the only way I have to reboot is to maintain power button to force shutdown.
My configuration : MSI GS60 with Ubuntu 18.04 64bit, Intel® Core™ i7-4720HQ CPU @ 2.60GHz × 8, Intel® Haswell Mobile (graphic chipset). I also have a Nvidia 970M, but I deactivated it (I only use it on windows). I have a dual boot with windows 10. edit: 16G RAM
Thanks in advance for any solution one could provide :)
suspend 18.04
suspend 18.04
edited May 23 '18 at 8:59
Philippe Cotte
asked May 22 '18 at 16:09
Philippe CottePhilippe Cotte
213
213
Hi, could you provide some additional information? First, did you set up a swap partition? If so, how large is it? I think for suspend to disk to work your swap must be active and at least as large as the amount of ram that you have. Run the command swapon and paste the output. Some of the other errata you're seeing seem to indicate you might have a bad ACPI config. Unfortunately, those are closed source and vendor locked :(
– guyfleeman
May 22 '18 at 20:15
Hi, yes I do have a swap, here is the output of swapon : NAME TYPE SIZE USED PRIO /dev/sda5 partition 6,5G 0B -2
– Philippe Cotte
May 23 '18 at 8:28
Are you trying to suspend to RAM or to disk? If it's to disk you need more swap space.
– guyfleeman
May 23 '18 at 18:56
I have the same issue I believe, compared to Ubuntu 17.10 the new version is very unstable. I'm thinking of installing 17.10 again.
– szx
Jun 18 '18 at 14:05
@guyfleeman Your tip seems to have helped OP to solve the problem. Consider posting an answer.
– Melebius
Jan 8 at 9:35
add a comment |
Hi, could you provide some additional information? First, did you set up a swap partition? If so, how large is it? I think for suspend to disk to work your swap must be active and at least as large as the amount of ram that you have. Run the command swapon and paste the output. Some of the other errata you're seeing seem to indicate you might have a bad ACPI config. Unfortunately, those are closed source and vendor locked :(
– guyfleeman
May 22 '18 at 20:15
Hi, yes I do have a swap, here is the output of swapon : NAME TYPE SIZE USED PRIO /dev/sda5 partition 6,5G 0B -2
– Philippe Cotte
May 23 '18 at 8:28
Are you trying to suspend to RAM or to disk? If it's to disk you need more swap space.
– guyfleeman
May 23 '18 at 18:56
I have the same issue I believe, compared to Ubuntu 17.10 the new version is very unstable. I'm thinking of installing 17.10 again.
– szx
Jun 18 '18 at 14:05
@guyfleeman Your tip seems to have helped OP to solve the problem. Consider posting an answer.
– Melebius
Jan 8 at 9:35
Hi, could you provide some additional information? First, did you set up a swap partition? If so, how large is it? I think for suspend to disk to work your swap must be active and at least as large as the amount of ram that you have. Run the command swapon and paste the output. Some of the other errata you're seeing seem to indicate you might have a bad ACPI config. Unfortunately, those are closed source and vendor locked :(
– guyfleeman
May 22 '18 at 20:15
Hi, could you provide some additional information? First, did you set up a swap partition? If so, how large is it? I think for suspend to disk to work your swap must be active and at least as large as the amount of ram that you have. Run the command swapon and paste the output. Some of the other errata you're seeing seem to indicate you might have a bad ACPI config. Unfortunately, those are closed source and vendor locked :(
– guyfleeman
May 22 '18 at 20:15
Hi, yes I do have a swap, here is the output of swapon : NAME TYPE SIZE USED PRIO /dev/sda5 partition 6,5G 0B -2
– Philippe Cotte
May 23 '18 at 8:28
Hi, yes I do have a swap, here is the output of swapon : NAME TYPE SIZE USED PRIO /dev/sda5 partition 6,5G 0B -2
– Philippe Cotte
May 23 '18 at 8:28
Are you trying to suspend to RAM or to disk? If it's to disk you need more swap space.
– guyfleeman
May 23 '18 at 18:56
Are you trying to suspend to RAM or to disk? If it's to disk you need more swap space.
– guyfleeman
May 23 '18 at 18:56
I have the same issue I believe, compared to Ubuntu 17.10 the new version is very unstable. I'm thinking of installing 17.10 again.
– szx
Jun 18 '18 at 14:05
I have the same issue I believe, compared to Ubuntu 17.10 the new version is very unstable. I'm thinking of installing 17.10 again.
– szx
Jun 18 '18 at 14:05
@guyfleeman Your tip seems to have helped OP to solve the problem. Consider posting an answer.
– Melebius
Jan 8 at 9:35
@guyfleeman Your tip seems to have helped OP to solve the problem. Consider posting an answer.
– Melebius
Jan 8 at 9:35
add a comment |
1 Answer
1
active
oldest
votes
After formatting and setting a bigger swap, the problem is solved. I used the same size as my RAM, 16G.
add a comment |
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%2f1039089%2fcomputer-can-not-enter-suspend-mode-freezes-instead-ubuntu-18%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
After formatting and setting a bigger swap, the problem is solved. I used the same size as my RAM, 16G.
add a comment |
After formatting and setting a bigger swap, the problem is solved. I used the same size as my RAM, 16G.
add a comment |
After formatting and setting a bigger swap, the problem is solved. I used the same size as my RAM, 16G.
After formatting and setting a bigger swap, the problem is solved. I used the same size as my RAM, 16G.
answered Jan 8 at 8:50
Philippe CottePhilippe Cotte
213
213
add a comment |
add a comment |
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%2f1039089%2fcomputer-can-not-enter-suspend-mode-freezes-instead-ubuntu-18%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
Hi, could you provide some additional information? First, did you set up a swap partition? If so, how large is it? I think for suspend to disk to work your swap must be active and at least as large as the amount of ram that you have. Run the command swapon and paste the output. Some of the other errata you're seeing seem to indicate you might have a bad ACPI config. Unfortunately, those are closed source and vendor locked :(
– guyfleeman
May 22 '18 at 20:15
Hi, yes I do have a swap, here is the output of swapon : NAME TYPE SIZE USED PRIO /dev/sda5 partition 6,5G 0B -2
– Philippe Cotte
May 23 '18 at 8:28
Are you trying to suspend to RAM or to disk? If it's to disk you need more swap space.
– guyfleeman
May 23 '18 at 18:56
I have the same issue I believe, compared to Ubuntu 17.10 the new version is very unstable. I'm thinking of installing 17.10 again.
– szx
Jun 18 '18 at 14:05
@guyfleeman Your tip seems to have helped OP to solve the problem. Consider posting an answer.
– Melebius
Jan 8 at 9:35