[systemd-bugs] [Bug 90279] New: Systemd suspend doesn't work after one successful suspend.
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri May 1 23:07:28 PDT 2015
https://bugs.freedesktop.org/show_bug.cgi?id=90279
Bug ID: 90279
Summary: Systemd suspend doesn't work after one successful
suspend.
Product: systemd
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: general
Assignee: systemd-bugs at lists.freedesktop.org
Reporter: onorua at gmail.com
QA Contact: systemd-bugs at lists.freedesktop.org
Created attachment 115509
--> https://bugs.freedesktop.org/attachment.cgi?id=115509&action=edit
systemd logs messages
Since update to Linux kernel 4.1.0-rc1 my laptop stopped to suspend after Lid
is closed properly. The first time after fresh reboot it does proper suspend,
the rest suspend tries - doesn't work. Only manual systemctl suspend works.
Here is the attached journalctl logs.
As you can see, after reboot I got proper suspend:
========
May 02 12:57:25 x systemd-logind[1518]: Lid closed.
May 02 12:57:25 x systemd-logind[1518]: Suspending...
May 02 12:57:25 x systemd[1]: Starting i3lock...
May 02 12:57:25 x systemd[1]: Started i3lock.
May 02 12:57:25 x systemd[1]: Reached target Sleep.
May 02 12:57:25 x systemd[1]: Starting Sleep.
May 02 12:57:25 x systemd[1]: Starting Suspend...
May 02 12:57:25 x systemd-sleep[2446]: Suspending system...
=========
after that, I do Lid close once again:
May 02 13:37:47 x systemd-logind[1518]: Lid closed.
then I wait for 10 seconds while my system supposed to go sleep, but as nothing
was happening I opened the Lid:
May 02 13:37:56 x systemd-logind[1518]: Lid opened.
decided to check maybe it needs some time to sleep or something like this:
May 02 13:37:57 x systemd-logind[1518]: Lid closed.
But almost 20 minutes of lid close did not work.
May 02 13:53:34 x systemd-logind[1518]: Lid opened.
Let me know if I can help you to debug the issue more, just let me know what to
do.
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/systemd-bugs/attachments/20150502/92cd2b9d/attachment.html>
More information about the systemd-bugs
mailing list