You are not logged in.

#1 2012-11-23 22:21:56

eruditorum
Member
Registered: 2012-11-12
Posts: 130

[MAYBE SOLVED] Delay between closing lid and receiving its acpi event

I configure laptop to enter S3 state on lid closing, but still I wait about 5-20 seconds after closing lid before it really enters sleep.
Sleep itself works flawlessly: it is instant if you enter it from console or X-terminal.
So the problem is "lid closed" acpi event. It is sent only after this terrible delay!

Why does this happen?

Last edited by eruditorum (2012-12-11 17:30:51)

Offline

#2 2012-11-23 22:49:11

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

You need to provide more information.  Like at the very very least, what harware you are using and how you are triggering sleep on lid close.

You should probbaly read this.

Offline

#3 2012-11-23 23:05:34

eruditorum
Member
Registered: 2012-11-12
Posts: 130

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

How I use lid to put laptop into sleep:

from /etc/acpi/handler.sh:

button/lid)
                case "$3" in
                        close)
                                echo mem >/sys/power/state
                        ;;
                        open)
                                #This will never work!
                        ;;
                esac
        ;;

from /etc/systemd/logind.conf:

HandleLidSwitch=ignore

If I disable handling lid switch by acpi daemon and give this work to systemd with "HandleLidSwitch=sleep" the latency won't go away.

Last edited by eruditorum (2012-11-23 23:41:38)

Offline

#4 2012-11-23 23:10:08

65kid
Member
From: Germany
Registered: 2011-01-26
Posts: 663

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

hehe, I just got my new Samsung Series 9 900x4d today, installed Arch just a few hours ago and noticed the same problem about 30 minutes ago. Then I look in the Arch Linux forums and someone posted about it. lol

I'm using systemd's HandleLidSwitch functionality btw.

@eruditorum: by hardware we mean your laptops' manufactor and model number (I'm guessing Samsung... wink ).

Last edited by 65kid (2012-11-23 23:11:25)

Offline

#5 2012-11-23 23:27:58

eruditorum
Member
Registered: 2012-11-12
Posts: 130

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

Samsung Series 3 laptop

~ > dmesg|grep LID
541:[    0.997323] ACPI: Lid Switch [LID0]

Last edited by eruditorum (2012-11-25 10:54:11)

Offline

#6 2012-11-23 23:47:54

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

I recall seeing this issue recently on these forums.  I am not certain, but I do think that it was also a Samsung machine.

Offline

#7 2012-11-24 01:53:20

eruditorum
Member
Registered: 2012-11-12
Posts: 130

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

Offline

#8 2012-11-25 03:03:38

cfr
Member
From: Cymru
Registered: 2011-11-27
Posts: 5,662

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

Well the thread isn't recent even if it was seen recently...


How To Ask Questions The Smart Way | Help Vampires

Arch Linux | x86_64 | GPT | EFI boot | grub2 | systemd | LVM2 on LUKS
Lenovo x121e | Intel(R) Core(TM) i3-2367M CPU @ 1.40GHz GenuineIntel | Intel Centrino Wireless-N 1000 | US keyboard with Euro | 320G 7200 RPM Seagate HDD

Offline

#9 2012-11-25 04:33:53

eruditorum
Member
Registered: 2012-11-12
Posts: 130

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

In addition, it seems that delay is different every time (on AC, on battery) but still stays in 5-20 seconds range.
Also in Windows delay existed, but was probably two times shorter (2-10 seconds).

Last edited by eruditorum (2012-11-25 09:50:09)

Offline

#10 2012-11-25 04:46:06

WonderWoofy
Member
From: Los Gatos, CA
Registered: 2012-05-19
Posts: 8,412

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

I am fairly certain I had seen a different, active thread that mentioned something similar (or rather, the same).  I cannot find it though, and I don't think that a solution was ever found.  Sorry I cannot be of more help.  It sounds like a hardware issue honestly.  I have read that microsofts implementation of acpi is kinda half assed, so it lets errors go undetected, leading to inconsistencies in the dsdt.  Maybe this has something to do with it?  I have to imagine that a system that is not getting the lid close call (but eventually gets it) is getting a delayed signal, not a delayed detection.  This would seem especially probably seeing that it is fairly common among a certain brand of machine.

Offline

#11 2012-11-25 09:48:05

eruditorum
Member
Registered: 2012-11-12
Posts: 130

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

[fix]

After latest systemd update delay became some practically constant and small amount of time (about 10 seconds.)

Last edited by eruditorum (2012-12-11 17:30:02)

Offline

#12 2013-01-25 11:00:17

mollier
Member
Registered: 2013-01-25
Posts: 2

Re: [MAYBE SOLVED] Delay between closing lid and receiving its acpi event

65kid wrote:

hehe, I just got my new Samsung Series 9 900x4d today, installed Arch just a few hours ago and noticed the same problem about 30 minutes ago. Then I look in the Arch Linux forums and someone posted about it. lol

I'm using systemd's HandleLidSwitch functionality btw.

@eruditorum: by hardware we mean your laptops' manufactor and model number (I'm guessing Samsung... wink ).

Hi,

I got the same laptop a few months ago. I've tried installing Ubuntu 12.04LTS on it, but the laptop runs too hot. I think an official bug report has been posted.
How does it perform running Arch linux? I'm probably not linux-proficient enough to run Arch, but it's worth a try.

Thanks.

Offline

Board footer

Powered by FluxBB