Hello,
following up the recent patch [0] to enable modern suspend on Dell notebooks, I
can report that this patch does *not* fix the situation on Dell Latitude
5285. I have tested with v4.12-10845-g74cbd96 and when closing the "lid"
or triggering sleep by echo mem > /sys/power/state, the system suspends,
but never wakes up again. Trying to resume with the power button does
not have any affect, as it is the case with 4.12.1.
A long power button press to forcefully shutdown the system is
necessary, at which point the notebook responds with blinking
the power LED (3x red, 5x white), which seems not to be defined in
the user manual.
Is there anything I can do to test what is going on?
Best,
Nico
p.s.: The device does also not have any backlight control available in
xorg, even though sysfs exposes a brightness setting - where is the best
place to report this? xorg bugzilla or kernel?
[0] https://lkml.org/lkml/2017/6/23/447
--
Werde Teil des modernen Arbeitens im Glarnerland auf http://www.digitalglarus.ch!
Lese Neuigkeiten auf Twitter: http://www.twitter.com/DigitalGlarus
Diskutiere mit auf Facebook: http://www.facebook.com/digitalglarus
On Thu, Jul 20, 2017 at 8:24 PM, Nico Schottelius
<[email protected]> wrote:
>
> Hello,
>
> following up the recent patch [0] to enable modern suspend on Dell notebooks, I
> can report that this patch does *not* fix the situation on Dell Latitude
> 5285. I have tested with v4.12-10845-g74cbd96 and when closing the "lid"
> or triggering sleep by echo mem > /sys/power/state, the system suspends,
> but never wakes up again. Trying to resume with the power button does
> not have any affect, as it is the case with 4.12.1.
>
> A long power button press to forcefully shutdown the system is
> necessary, at which point the notebook responds with blinking
> the power LED (3x red, 5x white), which seems not to be defined in
> the user manual.
>
> Is there anything I can do to test what is going on?
Have you tried "echo freeze > /sys/power/state" instead of "mem"?
Thanks,
Rafael
Nico,
> -----Original Message-----
> From: Nico Schottelius [mailto:[email protected]]
> Sent: Thursday, July 20, 2017 1:25 PM
> To: Linux ACPI <[email protected]>
> Cc: Linux PM <[email protected]>; Andy Shevchenko
> <[email protected]>; Darren Hart <[email protected]>; LKML
> <[email protected]>; Srinivas Pandruvada
> <[email protected]>; Mika Westerberg
> <[email protected]>; Limonciello, Mario
> <[email protected]>; Tom Lanyon <[email protected]>; J?r?me de
> Bretagne <[email protected]>; Linus Torvalds <torvalds@linux-
> foundation.org>; Zheng Lv <[email protected]>
> Subject: Modern Suspend on Dell Latitude 5285 does not resume
>
>
> Hello,
>
> following up the recent patch [0] to enable modern suspend on Dell notebooks, I
> can report that this patch does *not* fix the situation on Dell Latitude
> 5285. I have tested with v4.12-10845-g74cbd96 and when closing the "lid"
> or triggering sleep by echo mem > /sys/power/state, the system suspends,
> but never wakes up again. Trying to resume with the power button does
> not have any affect, as it is the case with 4.12.1.
>
> A long power button press to forcefully shutdown the system is
> necessary, at which point the notebook responds with blinking
> the power LED (3x red, 5x white), which seems not to be defined in
> the user manual.
>
> Is there anything I can do to test what is going on?
>
Currently the patch does not look at anything in the system to default to S2I vs S3.
This will affect systems that offer S3 and S2I (even if S3 is broken).
Have you configured /sys/power/mem_sleep to s2idle?
https://github.com/torvalds/linux/blob/master/Documentation/power/states.txt#L35
Thanks,
> Best,
>
> Nico
>
> p.s.: The device does also not have any backlight control available in
> xorg, even though sysfs exposes a brightness setting - where is the best
> place to report this? xorg bugzilla or kernel?
>
> [0] https://lkml.org/lkml/2017/6/23/447
>
> --
> Werde Teil des modernen Arbeitens im Glarnerland auf http://www.digitalglarus.ch!
> Lese Neuigkeiten auf Twitter: http://www.twitter.com/DigitalGlarus
> Diskutiere mit auf Facebook: http://www.facebook.com/digitalglarus
Good evening Mario,
> Currently the patch does not look at anything in the system to default to S2I vs S3.
> This will affect systems that offer S3 and S2I (even if S3 is broken).
>
> Have you configured /sys/power/mem_sleep to s2idle?
> https://github.com/torvalds/linux/blob/master/Documentation/power/states.txt#L35
indeed, after configuring it to s2idle, it works like charm!
Do you have any plans on defaulting to s2idle for machines that do not
properly support s3?
Best,
Nico
--
Modern, affordable, Swiss Virtual Machines can be found on http://www.datacenterlight.ch
On Fri, Jul 21, 2017 at 12:41 AM, Nico Schottelius
<[email protected]> wrote:
>
> Good evening Mario,
>
>> Currently the patch does not look at anything in the system to default to S2I vs S3.
>> This will affect systems that offer S3 and S2I (even if S3 is broken).
>>
>> Have you configured /sys/power/mem_sleep to s2idle?
>> https://github.com/torvalds/linux/blob/master/Documentation/power/states.txt#L35
>
> indeed, after configuring it to s2idle, it works like charm!
>
> Do you have any plans on defaulting to s2idle for machines that do not
> properly support s3?
Yes, we do.
Thanks,
Rafael