Looks like it was actually longer than 10 seconds as I opened the lid 1 sec after the power light began to pulse.
Fri 17 May 2019 09:48:20 AM CEST - state: open Fri 17 May 2019 09:48:21 AM CEST - state: open Fri 17 May 2019 09:48:22 AM CEST - state: open Fri 17 May 2019 09:48:23 AM CEST - state: open Fri 17 May 2019 09:48:24 AM CEST - state: open Fri 17 May 2019 09:48:25 AM CEST - state: closed Fri 17 May 2019 09:48:26 AM CEST - state: closed Fri 17 May 2019 09:48:27 AM CEST - state: closed Fri 17 May 2019 09:48:28 AM CEST - state: closed Fri 17 May 2019 09:48:29 AM CEST - state: closed Fri 17 May 2019 09:48:30 AM CEST - state: closed Fri 17 May 2019 09:48:31 AM CEST - state: closed Fri 17 May 2019 09:48:33 AM CEST - state: closed Fri 17 May 2019 09:48:34 AM CEST - state: closed Fri 17 May 2019 09:48:35 AM CEST - state: closed Fri 17 May 2019 09:48:36 AM CEST - state: closed Fri 17 May 2019 09:48:37 AM CEST - state: closed Fri 17 May 2019 09:48:38 AM CEST - state: closed Fri 17 May 2019 09:48:39 AM CEST - state: closed Fri 17 May 2019 09:48:40 AM CEST - state: closed Fri 17 May 2019 09:48:41 AM CEST - state: closed Fri 17 May 2019 09:48:42 AM CEST - state: closed Fri 17 May 2019 09:48:43 AM CEST - state: closed Fri 17 May 2019 09:48:44 AM CEST - state: closed Fri 17 May 2019 09:48:45 AM CEST - state: closed Fri 17 May 2019 09:48:46 AM CEST - state: closed Fri 17 May 2019 09:48:47 AM CEST - state: closed Fri 17 May 2019 09:48:48 AM CEST - state: closed Fri 17 May 2019 09:48:49 AM CEST - state: closed Fri 17 May 2019 09:48:50 AM CEST - state: closed Fri 17 May 2019 09:48:51 AM CEST - state: closed Fri 17 May 2019 09:48:52 AM CEST - state: closed Fri 17 May 2019 09:48:53 AM CEST - state: closed Fri 17 May 2019 09:48:54 AM CEST - state: closed Fri 17 May 2019 09:48:55 AM CEST - state: closed Fri 17 May 2019 09:49:00 AM CEST - state: open Fri 17 May 2019 09:49:02 AM CEST - state: open Fri 17 May 2019 09:49:03 AM CEST - state: open ^C On Fri, May 17, 2019 at 9:52 AM Chris Gregan <chris.gre...@canonical.com> wrote: > This is interesting. > > `echo mem > /sys/power/state` > This command was instant S3. The screen went black and the power light > immediately began to blink. > > However...for lid switch the power light takes around 10 seconds to begin > to pulse, but the state immediately switches. > > Fri 17 May 2019 09:48:22 AM CEST - state: open > Fri 17 May 2019 09:48:23 AM CEST - state: open > Fri 17 May 2019 09:48:24 AM CEST - state: open > Fri 17 May 2019 09:48:25 AM CEST - state: closed > Fri 17 May 2019 09:48:26 AM CEST - state: closed > Fri 17 May 2019 09:48:27 AM CEST - state: closed > > It seems although detection if immediate, it takes 10 seconds to process? > > On Thu, May 16, 2019 at 6:05 PM Andrea Righi <andrea.ri...@canonical.com> > wrote: > >> Hi Chris, just to make sure I understand (from a kernel perspective), >> can you confirm that `echo mem > /sys/power/state` is also fast at >> reaching the suspend state? >> >> In that case it would be interesting to check if there's a delay at >> detecting the state of the lid switch. For this, could you run the >> following command in a bash session: >> >> $ while :; do echo `date` - `cat /proc/acpi/button/lid/LID0/state`; >> sleep 1; done >> >> Close the lid, re-open it and you should notice something like this: >> >> Thu May 16 17:50:42 CEST 2019 - state: open >> Thu May 16 17:50:43 CEST 2019 - state: open >> Thu May 16 17:50:44 CEST 2019 - state: open >> Thu May 16 17:50:45 CEST 2019 - state: closed >> Thu May 16 17:50:46 CEST 2019 - state: closed >> Thu May 16 17:50:47 CEST 2019 - state: closed >> Thu May 16 17:50:48 CEST 2019 - state: open >> Thu May 16 17:50:49 CEST 2019 - state: open >> Thu May 16 17:50:50 CEST 2019 - state: open >> ^C >> >> Note that I have set the "lid close action" to do nothing, in this way >> we can better isolate the problem. Thanks. >> >> -- >> You received this bug notification because you are subscribed to the bug >> report. >> https://bugs.launchpad.net/bugs/1829399 >> >> Title: >> Lid switch triggered suspend takes much longer than UI triggered >> suspend >> >> To manage notifications about this bug go to: >> >> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions >> > > > -- > > Chris Gregan > Engineering Manager > Solutions QA/Techops > cgre...@irc.canonical.com > -- Chris Gregan Engineering Manager Solutions QA/Techops cgre...@irc.canonical.com -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/1829399 Title: Lid switch triggered suspend takes much longer than UI triggered suspend Status in linux package in Ubuntu: Incomplete Bug description: IBM T460 5.0.0-13-generic #14-Ubuntu SMP Mon Apr 15 14:59:14 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux When triggering a suspend even from the lid switch of my Lenovo T460 it takes 30 seconds to reach suspend state. Several others with different models of Lenovo laptops have also reproduced this issue. It seems this is isolated to the lid switch as UI triggered suspend (alt+power icon) is far faster. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1829399/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
