18.04 shuts off immediately after opening laptop lid to wake from sleep
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}
The computer goes to sleep just fine, I can see this from the syslogs recording sleep. It's a ThinkPad T570, so I can also see the red light on the lid glowing indicating sleep mode. However, when I open the lid within 1 second the power button goes dark. The power button never gets out of its glowing pattern indicating sleep mode nor does the keyboard backlight come on or the screen light up.
-I have tried installing a fresh copy of 18.04.1 on /dev/sda3
to dual-boot with 18.04.2 on /dev/sda2
.
-I have tried boot repair with a purge of grub that actually did work for me to be able to boot into 18.04.2 and then put it to sleep once and wake successfully (or at least I think it did). After this I removed 18.04.1 and did the same boot repair process and all was lost; waking from sleep no longer worked.
-I tried once again to install 18.04.1 on /dev/sda3
and run boot repair as before but to no avail.
-I have tried launching 18.04.2 with different kernel versions from the grub menu.
I'm not quite sure what could be causing this at this point. /var/log/syslog
shows no logs at all for the waking up process when it fails. All I see are suspending logs and then logs for when I boot up the computer from scratch after the abrupt shutdown.
This was not always the case. I successfully ran 18.04 on its own for months without this issue, and it only presented itself at least 2 weeks ago.
EDIT: My /var/log/pm-suspend.log
file: http://paste.ubuntu.com/p/mdb5ZCq6Zb/
EDIT2: Upgrading to kernel 4.20 seemed to fix the problem at which point I deleted the /dev/sda3
partition with 18.04.1 and ran boot repair. Now the problem persists. 5.0.7, 4.20, 4.15, 4.12 work as kernel versions just not with resuming Ubuntu.
dmesg
output after a failed 5.0.7 resume: http://paste.ubuntu.com/p/RXQNZzZg8P/
EDIT3: There appears to be no pattern to when it successfully resumes or not. At this point I have gone as far as reinstalling 18.04.2 from scratch without proprietary drivers to no avail. Out of 50 attempts, the computer has resumed successfully maybe 4 times in total across multiple installs and configurations of my machine.
grub2 18.04 suspend power-management resume
|
show 2 more comments
The computer goes to sleep just fine, I can see this from the syslogs recording sleep. It's a ThinkPad T570, so I can also see the red light on the lid glowing indicating sleep mode. However, when I open the lid within 1 second the power button goes dark. The power button never gets out of its glowing pattern indicating sleep mode nor does the keyboard backlight come on or the screen light up.
-I have tried installing a fresh copy of 18.04.1 on /dev/sda3
to dual-boot with 18.04.2 on /dev/sda2
.
-I have tried boot repair with a purge of grub that actually did work for me to be able to boot into 18.04.2 and then put it to sleep once and wake successfully (or at least I think it did). After this I removed 18.04.1 and did the same boot repair process and all was lost; waking from sleep no longer worked.
-I tried once again to install 18.04.1 on /dev/sda3
and run boot repair as before but to no avail.
-I have tried launching 18.04.2 with different kernel versions from the grub menu.
I'm not quite sure what could be causing this at this point. /var/log/syslog
shows no logs at all for the waking up process when it fails. All I see are suspending logs and then logs for when I boot up the computer from scratch after the abrupt shutdown.
This was not always the case. I successfully ran 18.04 on its own for months without this issue, and it only presented itself at least 2 weeks ago.
EDIT: My /var/log/pm-suspend.log
file: http://paste.ubuntu.com/p/mdb5ZCq6Zb/
EDIT2: Upgrading to kernel 4.20 seemed to fix the problem at which point I deleted the /dev/sda3
partition with 18.04.1 and ran boot repair. Now the problem persists. 5.0.7, 4.20, 4.15, 4.12 work as kernel versions just not with resuming Ubuntu.
dmesg
output after a failed 5.0.7 resume: http://paste.ubuntu.com/p/RXQNZzZg8P/
EDIT3: There appears to be no pattern to when it successfully resumes or not. At this point I have gone as far as reinstalling 18.04.2 from scratch without proprietary drivers to no avail. Out of 50 attempts, the computer has resumed successfully maybe 4 times in total across multiple installs and configurations of my machine.
grub2 18.04 suspend power-management resume
1
I had similar issue on a Dell xps 9570. The kernel would go into a panic on wake up. Updated my kernel to 4.18 at the time and it solved it. I'm now running 4.19 and it's been solid as well.
– pwaterz
2 days ago
I was running 4.15, and I just installed 4.20. It works fine now! I could have tried a lower minor version. Am I likely to encounter errors with this choice?
– gopher
2 days ago
New issue. After installing 4.20 things were working fine, so I removed 18.04.1 from/dev/sda3
and reinstalled grub to update the list of operating systems. Now I have the same issue again but with the updated kernel.
– gopher
2 days ago
I've been using Long Term Support kernel 4.14 and have been very happy with it. I recently upgraded 4.14.98 to 4.14.110 with no problems. You might want to try it when all else fails: askubuntu.com/questions/119080/…
– WinEunuuchs2Unix
2 days ago
@WinEunuuchs2Unix sadly testing both 4.14 and 4.19 LTS kernels did not fix anything.
– gopher
2 days ago
|
show 2 more comments
The computer goes to sleep just fine, I can see this from the syslogs recording sleep. It's a ThinkPad T570, so I can also see the red light on the lid glowing indicating sleep mode. However, when I open the lid within 1 second the power button goes dark. The power button never gets out of its glowing pattern indicating sleep mode nor does the keyboard backlight come on or the screen light up.
-I have tried installing a fresh copy of 18.04.1 on /dev/sda3
to dual-boot with 18.04.2 on /dev/sda2
.
-I have tried boot repair with a purge of grub that actually did work for me to be able to boot into 18.04.2 and then put it to sleep once and wake successfully (or at least I think it did). After this I removed 18.04.1 and did the same boot repair process and all was lost; waking from sleep no longer worked.
-I tried once again to install 18.04.1 on /dev/sda3
and run boot repair as before but to no avail.
-I have tried launching 18.04.2 with different kernel versions from the grub menu.
I'm not quite sure what could be causing this at this point. /var/log/syslog
shows no logs at all for the waking up process when it fails. All I see are suspending logs and then logs for when I boot up the computer from scratch after the abrupt shutdown.
This was not always the case. I successfully ran 18.04 on its own for months without this issue, and it only presented itself at least 2 weeks ago.
EDIT: My /var/log/pm-suspend.log
file: http://paste.ubuntu.com/p/mdb5ZCq6Zb/
EDIT2: Upgrading to kernel 4.20 seemed to fix the problem at which point I deleted the /dev/sda3
partition with 18.04.1 and ran boot repair. Now the problem persists. 5.0.7, 4.20, 4.15, 4.12 work as kernel versions just not with resuming Ubuntu.
dmesg
output after a failed 5.0.7 resume: http://paste.ubuntu.com/p/RXQNZzZg8P/
EDIT3: There appears to be no pattern to when it successfully resumes or not. At this point I have gone as far as reinstalling 18.04.2 from scratch without proprietary drivers to no avail. Out of 50 attempts, the computer has resumed successfully maybe 4 times in total across multiple installs and configurations of my machine.
grub2 18.04 suspend power-management resume
The computer goes to sleep just fine, I can see this from the syslogs recording sleep. It's a ThinkPad T570, so I can also see the red light on the lid glowing indicating sleep mode. However, when I open the lid within 1 second the power button goes dark. The power button never gets out of its glowing pattern indicating sleep mode nor does the keyboard backlight come on or the screen light up.
-I have tried installing a fresh copy of 18.04.1 on /dev/sda3
to dual-boot with 18.04.2 on /dev/sda2
.
-I have tried boot repair with a purge of grub that actually did work for me to be able to boot into 18.04.2 and then put it to sleep once and wake successfully (or at least I think it did). After this I removed 18.04.1 and did the same boot repair process and all was lost; waking from sleep no longer worked.
-I tried once again to install 18.04.1 on /dev/sda3
and run boot repair as before but to no avail.
-I have tried launching 18.04.2 with different kernel versions from the grub menu.
I'm not quite sure what could be causing this at this point. /var/log/syslog
shows no logs at all for the waking up process when it fails. All I see are suspending logs and then logs for when I boot up the computer from scratch after the abrupt shutdown.
This was not always the case. I successfully ran 18.04 on its own for months without this issue, and it only presented itself at least 2 weeks ago.
EDIT: My /var/log/pm-suspend.log
file: http://paste.ubuntu.com/p/mdb5ZCq6Zb/
EDIT2: Upgrading to kernel 4.20 seemed to fix the problem at which point I deleted the /dev/sda3
partition with 18.04.1 and ran boot repair. Now the problem persists. 5.0.7, 4.20, 4.15, 4.12 work as kernel versions just not with resuming Ubuntu.
dmesg
output after a failed 5.0.7 resume: http://paste.ubuntu.com/p/RXQNZzZg8P/
EDIT3: There appears to be no pattern to when it successfully resumes or not. At this point I have gone as far as reinstalling 18.04.2 from scratch without proprietary drivers to no avail. Out of 50 attempts, the computer has resumed successfully maybe 4 times in total across multiple installs and configurations of my machine.
grub2 18.04 suspend power-management resume
grub2 18.04 suspend power-management resume
edited yesterday
gopher
asked 2 days ago
gophergopher
718
718
1
I had similar issue on a Dell xps 9570. The kernel would go into a panic on wake up. Updated my kernel to 4.18 at the time and it solved it. I'm now running 4.19 and it's been solid as well.
– pwaterz
2 days ago
I was running 4.15, and I just installed 4.20. It works fine now! I could have tried a lower minor version. Am I likely to encounter errors with this choice?
– gopher
2 days ago
New issue. After installing 4.20 things were working fine, so I removed 18.04.1 from/dev/sda3
and reinstalled grub to update the list of operating systems. Now I have the same issue again but with the updated kernel.
– gopher
2 days ago
I've been using Long Term Support kernel 4.14 and have been very happy with it. I recently upgraded 4.14.98 to 4.14.110 with no problems. You might want to try it when all else fails: askubuntu.com/questions/119080/…
– WinEunuuchs2Unix
2 days ago
@WinEunuuchs2Unix sadly testing both 4.14 and 4.19 LTS kernels did not fix anything.
– gopher
2 days ago
|
show 2 more comments
1
I had similar issue on a Dell xps 9570. The kernel would go into a panic on wake up. Updated my kernel to 4.18 at the time and it solved it. I'm now running 4.19 and it's been solid as well.
– pwaterz
2 days ago
I was running 4.15, and I just installed 4.20. It works fine now! I could have tried a lower minor version. Am I likely to encounter errors with this choice?
– gopher
2 days ago
New issue. After installing 4.20 things were working fine, so I removed 18.04.1 from/dev/sda3
and reinstalled grub to update the list of operating systems. Now I have the same issue again but with the updated kernel.
– gopher
2 days ago
I've been using Long Term Support kernel 4.14 and have been very happy with it. I recently upgraded 4.14.98 to 4.14.110 with no problems. You might want to try it when all else fails: askubuntu.com/questions/119080/…
– WinEunuuchs2Unix
2 days ago
@WinEunuuchs2Unix sadly testing both 4.14 and 4.19 LTS kernels did not fix anything.
– gopher
2 days ago
1
1
I had similar issue on a Dell xps 9570. The kernel would go into a panic on wake up. Updated my kernel to 4.18 at the time and it solved it. I'm now running 4.19 and it's been solid as well.
– pwaterz
2 days ago
I had similar issue on a Dell xps 9570. The kernel would go into a panic on wake up. Updated my kernel to 4.18 at the time and it solved it. I'm now running 4.19 and it's been solid as well.
– pwaterz
2 days ago
I was running 4.15, and I just installed 4.20. It works fine now! I could have tried a lower minor version. Am I likely to encounter errors with this choice?
– gopher
2 days ago
I was running 4.15, and I just installed 4.20. It works fine now! I could have tried a lower minor version. Am I likely to encounter errors with this choice?
– gopher
2 days ago
New issue. After installing 4.20 things were working fine, so I removed 18.04.1 from
/dev/sda3
and reinstalled grub to update the list of operating systems. Now I have the same issue again but with the updated kernel.– gopher
2 days ago
New issue. After installing 4.20 things were working fine, so I removed 18.04.1 from
/dev/sda3
and reinstalled grub to update the list of operating systems. Now I have the same issue again but with the updated kernel.– gopher
2 days ago
I've been using Long Term Support kernel 4.14 and have been very happy with it. I recently upgraded 4.14.98 to 4.14.110 with no problems. You might want to try it when all else fails: askubuntu.com/questions/119080/…
– WinEunuuchs2Unix
2 days ago
I've been using Long Term Support kernel 4.14 and have been very happy with it. I recently upgraded 4.14.98 to 4.14.110 with no problems. You might want to try it when all else fails: askubuntu.com/questions/119080/…
– WinEunuuchs2Unix
2 days ago
@WinEunuuchs2Unix sadly testing both 4.14 and 4.19 LTS kernels did not fix anything.
– gopher
2 days ago
@WinEunuuchs2Unix sadly testing both 4.14 and 4.19 LTS kernels did not fix anything.
– gopher
2 days ago
|
show 2 more comments
1 Answer
1
active
oldest
votes
sleep is for all intents and puposes broken on ubuntu 18.04/.1/.2
the symptoms will vary depending on the hardware. what I did to fix it was switching to ubuntu 18.10.
19.04 is right around the corner (18th of april) and should also provide the same fix.
hope this helps.
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
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%2f1132298%2f18-04-shuts-off-immediately-after-opening-laptop-lid-to-wake-from-sleep%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
sleep is for all intents and puposes broken on ubuntu 18.04/.1/.2
the symptoms will vary depending on the hardware. what I did to fix it was switching to ubuntu 18.10.
19.04 is right around the corner (18th of april) and should also provide the same fix.
hope this helps.
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
add a comment |
sleep is for all intents and puposes broken on ubuntu 18.04/.1/.2
the symptoms will vary depending on the hardware. what I did to fix it was switching to ubuntu 18.10.
19.04 is right around the corner (18th of april) and should also provide the same fix.
hope this helps.
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
add a comment |
sleep is for all intents and puposes broken on ubuntu 18.04/.1/.2
the symptoms will vary depending on the hardware. what I did to fix it was switching to ubuntu 18.10.
19.04 is right around the corner (18th of april) and should also provide the same fix.
hope this helps.
sleep is for all intents and puposes broken on ubuntu 18.04/.1/.2
the symptoms will vary depending on the hardware. what I did to fix it was switching to ubuntu 18.10.
19.04 is right around the corner (18th of april) and should also provide the same fix.
hope this helps.
answered yesterday
tatsutatsu
588634
588634
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
add a comment |
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
Thanks for the heads up. Is there any official communication from canonical on this?
– gopher
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
nnnnnnnnnnnnope
– tatsu
yesterday
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%2f1132298%2f18-04-shuts-off-immediately-after-opening-laptop-lid-to-wake-from-sleep%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
1
I had similar issue on a Dell xps 9570. The kernel would go into a panic on wake up. Updated my kernel to 4.18 at the time and it solved it. I'm now running 4.19 and it's been solid as well.
– pwaterz
2 days ago
I was running 4.15, and I just installed 4.20. It works fine now! I could have tried a lower minor version. Am I likely to encounter errors with this choice?
– gopher
2 days ago
New issue. After installing 4.20 things were working fine, so I removed 18.04.1 from
/dev/sda3
and reinstalled grub to update the list of operating systems. Now I have the same issue again but with the updated kernel.– gopher
2 days ago
I've been using Long Term Support kernel 4.14 and have been very happy with it. I recently upgraded 4.14.98 to 4.14.110 with no problems. You might want to try it when all else fails: askubuntu.com/questions/119080/…
– WinEunuuchs2Unix
2 days ago
@WinEunuuchs2Unix sadly testing both 4.14 and 4.19 LTS kernels did not fix anything.
– gopher
2 days ago