linux-kernel - Re: Modern Suspend on Dell Latitude 5285 does not resume

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJZ5v0j6H+R869-h0FnnL3NTyOFoPODSbvEeug_YPcBdz+BCcg@mail.gmail.com>
Date:   Fri, 21 Jul 2017 01:05:05 +0200
From:   "Rafael J. Wysocki" <rafael@...nel.org>
To:     Nico Schottelius <nico.schottelius@...leich.ch>
Cc:     Mario Limonciello <Mario.Limonciello@...l.com>,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
        Linux PM <linux-pm@...r.kernel.org>,
        Andy Shevchenko <andriy.shevchenko@...ux.intel.com>,
        Darren Hart <dvhart@...radead.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Srinivas Pandruvada <srinivas.pandruvada@...ux.intel.com>,
        Mika Westerberg <mika.westerberg@...ux.intel.com>,
        Tom Lanyon <tom@...shoeco.com>,
        Jérôme de Bretagne 
        <jerome.debretagne@...il.com>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        Lv <lv.zheng@...el.com>
Subject: Re: Modern Suspend on Dell Latitude 5285 does not resume

On Fri, Jul 21, 2017 at 12:41 AM, Nico Schottelius
<nico.schottelius@...leich.ch> 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