Arch sometimes won't suspend
3
Sometimes the computer won't auto-suspend when the lid has been closed. When this happens re-closing the lid won't make it suspend until next reboot. After the reboot the auto-suspend works again. After a while it stops working again, I haven't been able to determine what changes the state from suspendable to unsuspendable.
In the unsuspendable state "sudo pm-suspend" and "sudo systemctl suspend" don't make it stay suspended.
I'm running a Lenovo X220 with Arch 64 bit.
What should I do/try to make it work as it is supposed to?
EDIT:added journalctl output:
journalctl -xn
-- Logs begin at Sun 2013-08-25 11:05:23 CEST, end at Tue 2014-03-04 20:32:31 CET. --
Mar 04 20:32:06 x220 systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE
Mar 04 20:32:06 x220 systemd[1]: Failed to start Suspend.
-- Subject: Unit systemd-suspend.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit systemd-suspend.service has failed.
--
-- The result is failed.
Mar 04 20:32:06 x220 systemd[1]: Dependency failed for Suspend.
-- Subject: Unit suspend.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit suspend.target has failed.
--
-- The result is dependency.
Mar 04 20:32:06 x220 systemd[1]: Service sleep.target is not needed anymore. Stopping.
Mar 04 20:32:06 x220 systemd[1]: Unit systemd-suspend.service entered failed state.
Mar 04 20:32:06 x220 systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has begun shutting down.
Mar 04 20:32:06 x220 systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
--
-- Unit sleep.target has finished shutting down.
Mar 04 20:32:06 x220 sudo[21989]: pam_unix(sudo:session): session closed for user root
Mar 04 20:32:06 x220 kernel: video LNXVIDEO:00: Restoring backlight state
arch-linux suspend
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
add a comment |
3
Sometimes the computer won't auto-suspend when the lid has been closed. When this happens re-closing the lid won't make it suspend until next reboot. After the reboot the auto-suspend works again. After a while it stops working again, I haven't been able to determine what changes the state from suspendable to unsuspendable.
In the unsuspendable state "sudo pm-suspend" and "sudo systemctl suspend" don't make it stay suspended.
I'm running a Lenovo X220 with Arch 64 bit.
What should I do/try to make it work as it is supposed to?
EDIT:added journalctl output:
journalctl -xn
-- Logs begin at Sun 2013-08-25 11:05:23 CEST, end at Tue 2014-03-04 20:32:31 CET. --
Mar 04 20:32:06 x220 systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE
Mar 04 20:32:06 x220 systemd[1]: Failed to start Suspend.
-- Subject: Unit systemd-suspend.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit systemd-suspend.service has failed.
--
-- The result is failed.
Mar 04 20:32:06 x220 systemd[1]: Dependency failed for Suspend.
-- Subject: Unit suspend.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit suspend.target has failed.
--
-- The result is dependency.
Mar 04 20:32:06 x220 systemd[1]: Service sleep.target is not needed anymore. Stopping.
Mar 04 20:32:06 x220 systemd[1]: Unit systemd-suspend.service entered failed state.
Mar 04 20:32:06 x220 systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has begun shutting down.
Mar 04 20:32:06 x220 systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
--
-- Unit sleep.target has finished shutting down.
Mar 04 20:32:06 x220 sudo[21989]: pam_unix(sudo:session): session closed for user root
Mar 04 20:32:06 x220 kernel: video LNXVIDEO:00: Restoring backlight state
arch-linux suspend
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
Any log that may be useful?sudo journalctlmay give you some.
– Felix Yan
Dec 30 '13 at 8:38
add a comment |
3
3
3
Sometimes the computer won't auto-suspend when the lid has been closed. When this happens re-closing the lid won't make it suspend until next reboot. After the reboot the auto-suspend works again. After a while it stops working again, I haven't been able to determine what changes the state from suspendable to unsuspendable.
In the unsuspendable state "sudo pm-suspend" and "sudo systemctl suspend" don't make it stay suspended.
I'm running a Lenovo X220 with Arch 64 bit.
What should I do/try to make it work as it is supposed to?
EDIT:added journalctl output:
journalctl -xn
-- Logs begin at Sun 2013-08-25 11:05:23 CEST, end at Tue 2014-03-04 20:32:31 CET. --
Mar 04 20:32:06 x220 systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE
Mar 04 20:32:06 x220 systemd[1]: Failed to start Suspend.
-- Subject: Unit systemd-suspend.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit systemd-suspend.service has failed.
--
-- The result is failed.
Mar 04 20:32:06 x220 systemd[1]: Dependency failed for Suspend.
-- Subject: Unit suspend.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit suspend.target has failed.
--
-- The result is dependency.
Mar 04 20:32:06 x220 systemd[1]: Service sleep.target is not needed anymore. Stopping.
Mar 04 20:32:06 x220 systemd[1]: Unit systemd-suspend.service entered failed state.
Mar 04 20:32:06 x220 systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has begun shutting down.
Mar 04 20:32:06 x220 systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
--
-- Unit sleep.target has finished shutting down.
Mar 04 20:32:06 x220 sudo[21989]: pam_unix(sudo:session): session closed for user root
Mar 04 20:32:06 x220 kernel: video LNXVIDEO:00: Restoring backlight state
arch-linux suspend
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
Sometimes the computer won't auto-suspend when the lid has been closed. When this happens re-closing the lid won't make it suspend until next reboot. After the reboot the auto-suspend works again. After a while it stops working again, I haven't been able to determine what changes the state from suspendable to unsuspendable.
In the unsuspendable state "sudo pm-suspend" and "sudo systemctl suspend" don't make it stay suspended.
I'm running a Lenovo X220 with Arch 64 bit.
What should I do/try to make it work as it is supposed to?
EDIT:added journalctl output:
journalctl -xn
-- Logs begin at Sun 2013-08-25 11:05:23 CEST, end at Tue 2014-03-04 20:32:31 CET. --
Mar 04 20:32:06 x220 systemd[1]: systemd-suspend.service: main process exited, code=exited, status=1/FAILURE
Mar 04 20:32:06 x220 systemd[1]: Failed to start Suspend.
-- Subject: Unit systemd-suspend.service has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit systemd-suspend.service has failed.
--
-- The result is failed.
Mar 04 20:32:06 x220 systemd[1]: Dependency failed for Suspend.
-- Subject: Unit suspend.target has failed
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/be02cf6855d2428ba40df7e9d022f03d
--
-- Unit suspend.target has failed.
--
-- The result is dependency.
Mar 04 20:32:06 x220 systemd[1]: Service sleep.target is not needed anymore. Stopping.
Mar 04 20:32:06 x220 systemd[1]: Unit systemd-suspend.service entered failed state.
Mar 04 20:32:06 x220 systemd[1]: Stopping Sleep.
-- Subject: Unit sleep.target has begun shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
--
-- Unit sleep.target has begun shutting down.
Mar 04 20:32:06 x220 systemd[1]: Stopped target Sleep.
-- Subject: Unit sleep.target has finished shutting down
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: http://www.freedesktop.org/wiki/Software/systemd/catalog/9d1aaa27d60140bd96365438aad20286
--
-- Unit sleep.target has finished shutting down.
Mar 04 20:32:06 x220 sudo[21989]: pam_unix(sudo:session): session closed for user root
Mar 04 20:32:06 x220 kernel: video LNXVIDEO:00: Restoring backlight state
arch-linux suspend
arch-linux suspend
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
edited Mar 4 '14 at 22:40
Gunnish
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
asked Dec 29 '13 at 16:51
GunnishGunnish
1287
1287
Any log that may be useful?sudo journalctlmay give you some.
– Felix Yan
Dec 30 '13 at 8:38
add a comment |
Any log that may be useful?sudo journalctlmay give you some.
– Felix Yan
Dec 30 '13 at 8:38
Any log that may be useful?
sudo journalctl may give you some.– Felix Yan
Dec 30 '13 at 8:38
Any log that may be useful?
sudo journalctl may give you some.– Felix Yan
Dec 30 '13 at 8:38
add a comment |
1 Answer
1
active
oldest
votes
0
Mine would suspend but immediately resume. The fix for me was to disable (d) Wake-on-LAN:
$ sudo ethtool -s eno1 wol d
$ sudo ethtool eno1 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "106"
};
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: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
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
});
}
});
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f107027%2farch-sometimes-wont-suspend%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
0
Mine would suspend but immediately resume. The fix for me was to disable (d) Wake-on-LAN:
$ sudo ethtool -s eno1 wol d
$ sudo ethtool eno1 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
add a comment |
0
Mine would suspend but immediately resume. The fix for me was to disable (d) Wake-on-LAN:
$ sudo ethtool -s eno1 wol d
$ sudo ethtool eno1 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
add a comment |
0
0
0
Mine would suspend but immediately resume. The fix for me was to disable (d) Wake-on-LAN:
$ sudo ethtool -s eno1 wol d
$ sudo ethtool eno1 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
Mine would suspend but immediately resume. The fix for me was to disable (d) Wake-on-LAN:
$ sudo ethtool -s eno1 wol d
$ sudo ethtool eno1 | grep Wake-on
Supports Wake-on: pumbg
Wake-on: d
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
answered Jan 25 '15 at 14:04
Thomas LeonardThomas Leonard
1214
1214
add a comment |
add a comment |
draft saved
draft discarded
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- 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.
draft saved
draft discarded
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%2funix.stackexchange.com%2fquestions%2f107027%2farch-sometimes-wont-suspend%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
Any log that may be useful?
sudo journalctlmay give you some.– Felix Yan
Dec 30 '13 at 8:38