closing lid of laptop

[Paolo Galtieri]

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?

Any help is appreciated.

Thanks,
Paolo

[Matt Morgan]

On Mon, Dec 19, 2016 at 12:12 PM, Paolo Galtieri <pgaltieri(a)gmail.com&gt;
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?
>  
I'm not on F25 yet, but this is usually most easily controlled with Tweak
Tool (gnome-tweak-tool).

[Kseniya Blashchuk]

I'm on 25 and I have figured out with a surprise that now my laptop
discharges with the closed lid like if it's working in a a normal mode. So
I'm not sure if it suspends or sleeps. Suspend is set with the Gnome tweak
tool.
Moreover, when I open the lid I just see black screen sometimes.

On Mon, Dec 19, 2016, 8:39 PM Matt Morgan <minxmertzmomo(a)gmail.com&gt; wrote:

>  On Mon, Dec 19, 2016 at 12:12 PM, Paolo Galtieri
> <pgaltieri(a)gmail.com&gt;
>  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?
>
>
>  I'm not on F25 yet, but this is usually most easily controlled with Tweak
>  Tool (gnome-tweak-tool).
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>

[Dave Martin]

Ummm?

It does what you tell it to do.  I set mine to activate the screensaver and
shut the screen off, but suspending, shutting down, or other options are
possible.

All are useful in different cases.  Although, suspending from a logged in
session is the default I've seen most often.

It's under power options in KDE and , I believe, in Gnome.

On Mon, Dec 19, 2016 at 12:45 PM Kseniya Blashchuk <ksyblast(a)gmail.com&gt;
wrote:

>  I'm on 25 and I have figured out with a surprise that now my
> laptop
>  discharges with the closed lid like if it's working in a a normal mode. So
>  I'm not sure if it suspends or sleeps. Suspend is set with the Gnome tweak
>  tool.
>  Moreover, when I open the lid I just see black screen sometimes.
>
>  On Mon, Dec 19, 2016, 8:39 PM Matt Morgan <minxmertzmomo(a)gmail.com&gt; wrote:
>
>  On Mon, Dec 19, 2016 at 12:12 PM, Paolo Galtieri <pgaltieri(a)gmail.com&gt;
>  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?
>
>
>  I'm not on F25 yet, but this is usually most easily controlled with Tweak
>  Tool (gnome-tweak-tool).
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org
>  
-- 
-- 
Nobody believed that I could build a space station here.  So I built it
anyway. It sank into the vortex.  So I built another one.  It sank into the
vortex.  The third station burned down, fell over then sank into the
vortex.  The fourth station just vanished.  And the fifth station, THAT
stayed!

[Chris Murphy]

On Mon, Dec 19, 2016 at 10:12 AM, Paolo Galtieri <pgaltieri(a)gmail.com&gt;
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

[Paolo Galtieri]

Thanks for the information, but I don't think this is the problem since 
I don't see those messages.  What I discovered by using gnome-tweak-tool 
is that the default behavior is to not suspend on lid closed.  What's 
really confusing is that the entry under the Power section of 
gnome-tweak-tool says "Don't suspend on lid closed" and there's this 
slider to the right, which is unlabeled, so I don't know what state it's 
in.  When I moved it to the right it did suspend when I closed the lid. 
However, it has now stopped doing so.  I do see this message in the journal:

Dec 31 09:57:26 terrapin kernel: acpi device:28: Cannot transition to 
power state D3hot for parent in (unknown)

So I'm still not certain what the issue is.

Paolo

On 12/29/2016 09:32 AM, Chris Murphy wrote:
>  On Mon, Dec 19, 2016 at 10:12 AM, Paolo Galtieri <pgaltieri(a)gmail.com 
>  <mailto:[e-mail]>> 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
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org

[Chris Murphy]

On Sat, Dec 31, 2016 at 11:04 AM, Paolo Galtieri <pgaltieri(a)gmail.com&gt; wrote:
>  Thanks for the information, but I don't think this is the problem
> since I
>  don't see those messages.  What I discovered by using gnome-tweak-tool is
>  that the default behavior is to not suspend on lid closed. 
"Don't suspend on lid close" is Off by default. This is a double
negative so it means suspend on lid close is the default. I'd rather
it follow the language for Power Button which is to use an Action
pop-up menu. Seems like there are three sane possibilities: Nothing,
Suspend, Hybrid with the default being suspend.


>  What's really
>  confusing is that the entry under the Power section of gnome-tweak-tool says
>  "Don't suspend on lid closed" and there's this slider to the right,
> which is
>  unlabeled, so I don't know what state it's in. 
Weird, sounds like a font related bug or something; that slider for me
is an Off / On slider and by default is Off (slider is to the left).


-- 
Chris Murphy

[Paolo Galtieri]

One thing I did discover is that the issue is hardware dependent.  I 
have an older Dell laptop and it suspends when I close the lid.  It's my 
newer laptop, i.e. about 4 years old that is currently having the problem.

Here's the cpuinfo for the working system

processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
stepping    : 6
microcode    : 0xd1
cpu MHz        : 2000.000
cache size    : 4096 KB
physical id    : 0
siblings    : 2
core id        : 0
cpu cores    : 2
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf 
eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
lahf_lm tpr_shadow dtherm
bugs        :
bogomips    : 3990.20
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
stepping    : 6
microcode    : 0xd1
cpu MHz        : 1000.000
cache size    : 4096 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf 
eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
lahf_lm tpr_shadow dtherm
bugs        :
bogomips    : 3989.84
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

Here's the cpuinfo for the one that doesn't suspend:

processor    : 0
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
stepping    : 6
microcode    : 0xd1
cpu MHz        : 2000.000
cache size    : 4096 KB
physical id    : 0
siblings    : 2
core id        : 0
cpu cores    : 2
apicid        : 0
initial apicid    : 0
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf 
eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
lahf_lm tpr_shadow dtherm
bugs        :
bogomips    : 3990.20
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

processor    : 1
vendor_id    : GenuineIntel
cpu family    : 6
model        : 15
model name    : Intel(R) Core(TM)2 CPU         T7200  @ 2.00GHz
stepping    : 6
microcode    : 0xd1
cpu MHz        : 1000.000
cache size    : 4096 KB
physical id    : 0
siblings    : 2
core id        : 1
cpu cores    : 2
apicid        : 1
initial apicid    : 1
fpu        : yes
fpu_exception    : yes
cpuid level    : 10
wp        : yes
flags        : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca 
cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss ht tm pbe syscall 
nx lm constant_tsc arch_perfmon pebs bts rep_good nopl aperfmperf 
eagerfpu pni dtes64 monitor ds_cpl vmx est tm2 ssse3 cx16 xtpr pdcm 
lahf_lm tpr_shadow dtherm
bugs        :
bogomips    : 3989.84
clflush size    : 64
cache_alignment    : 64
address sizes    : 36 bits physical, 48 bits virtual
power management:

Paolo


On 01/01/2017 10:43 AM, Chris Murphy wrote:
>  On Sat, Dec 31, 2016 at 11:04 AM, Paolo Galtieri
> <pgaltieri(a)gmail.com&gt; wrote:
> > Thanks for the information, but I don't think this is the problem since I
> > don't see those messages.  What I discovered by using gnome-tweak-tool is
> > that the default behavior is to not suspend on lid closed.
>  "Don't suspend on lid close" is Off by default. This is a double
>  negative so it means suspend on lid close is the default. I'd rather
>  it follow the language for Power Button which is to use an Action
>  pop-up menu. Seems like there are three sane possibilities: Nothing,
>  Suspend, Hybrid with the default being suspend.
>
>
> > What's really
> > confusing is that the entry under the Power section of gnome-tweak-tool says
> > "Don't suspend on lid closed" and there's this slider to the right,
> which is
> > unlabeled, so I don't know what state it's in.
>  Weird, sounds like a font related bug or something; that slider for me
>  is an Off / On slider and by default is Off (slider is to the left).
>
>

[Paolo Galtieri]

Using gnome-tweak-tool I tried both settings for the "Don't suspend on 
lid closed" entry under the "Power" section, and in neither case does 
the system suspend on lid closed since I could still ping the system.  
So other than seeing this entry:

Dec 31 10:22:01 terrapin kernel: acpi device:28: Cannot transition to 
power state D3hot for parent in (unknown)

I don't know what to try next.

Paolo

On 12/29/2016 09:32 AM, Chris Murphy wrote:
>  On Mon, Dec 19, 2016 at 10:12 AM, Paolo Galtieri <pgaltieri(a)gmail.com 
>  <mailto:[e-mail]>> 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
>
>
>  _______________________________________________
>  users mailing list -- users(a)lists.fedoraproject.org
>  To unsubscribe send an email to users-leave(a)lists.fedoraproject.org

[Chris Murphy]

On Sat, Dec 31, 2016 at 11:29 AM, Paolo Galtieri <pgaltieri(a)gmail.com&gt; wrote:
>  Using gnome-tweak-tool I tried both settings for the "Don't
> suspend on lid
>  closed" entry under the "Power" section, and in neither case does the
> system
>  suspend on lid closed since I could still ping the system.  So other than
>  seeing this entry:
>
>  Dec 31 10:22:01 terrapin kernel: acpi device:28: Cannot transition to power
>  state D3hot for parent in (unknown) 
You might read this and see if the low level kernel commands work; and
work your way up to e.g. 'sudo systemctl suspend'  to see where the
problem starts happening.

https://01.org/blogs/rzhang/2015/best-practice-debug-linux-suspend/hibern...


-- 
Chris Murphy