On Mon, Dec 19, 2016 at 10:12 AM, Paolo Galtieri <pgaltieri@gmail.com> wrote:

I have a question regarding what is supposed to happen when I close the lid of a laptop. I always assumed that closing the lid would cause the system to go into suspend mode and wake up when the lid was opened. What I mean by suspend is that the system should be doing very little so as to not consume battery. However, what I have observed with my laptop when I upgraded to F25 is that the system is still active. I have an ssh session into the laptop from another system and this session is still active after I close the lid. So the question is what is supposed to happen when I close my laptop's lid?

Using 'journalctl -f' I get this

Dec 29 10:17:33 f25h kernel: atkbd serio0: Unknown key pressed (translated set 2, code 0xd8 on isa0060/serio0).
Dec 29 10:17:33 f25h kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Dec 29 10:17:33 f25h kernel: atkbd serio0: Unknown key released (translated set 2, code 0xd8 on isa0060/serio0).
Dec 29 10:17:33 f25h kernel: atkbd serio0: Use 'setkeycodes e058 <keycode>' to make it known.
Dec 29 10:17:33 f25h systemd-logind[799]: Lid closed.
Dec 29 10:17:33 f25h systemd-logind[799]: Suspending...

This is F25 Workstation, default out of the box behavior. If it's not sleeping, or as it is in my case with recent kernels (regression [1]), it wakes back up, goes to sleep, wakes back up, goes back to sleep, etc. until battery dies; then you've got a kernel/ACPI bug. Step 1 would be to make sure you have the latest firmware updates for your laptop. And then add 'no_console_suspend ignore_loglevel' and reboot. Then close the lid, leave it closed for maybe 5 minutes, open it back up, and find somewhere to post both dmesg and 'journalctl -b -o short-monotonic > journal.log' since they capture different things.

It may be that the kernel doesn't recognize the lid is being closed, in which case it won't even try to suspend. Or it might be some other problem. I note I have a bunch of atkbd complaints in my kernel messages but there doesn't seem to be a negative effect other than noise.

[1]
https://bugzilla.kernel.org/show_bug.cgi?id=185521

Chris Murphy