<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [Intel-gfx] As of kernel 4.3-rc1 system will not stay in S3 suspend [REGRESSION][BISECTED]" href="https://bugs.freedesktop.org/show_bug.cgi?id=92414#c25">Comment # 25</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [Intel-gfx] As of kernel 4.3-rc1 system will not stay in S3 suspend [REGRESSION][BISECTED]" href="https://bugs.freedesktop.org/show_bug.cgi?id=92414">bug 92414</a> from <a class="email" href="mailto:dorota.czaplejewicz@collabora.co.uk" title="Dorota Czaplejewicz <dorota.czaplejewicz@collabora.co.uk>"> Dorota Czaplejewicz</a> <pre>I have to update my comment - probably I didn't check the correct kernel, but the issue mysteriously appeared between 4.9.0 (69973b830859bc6529a7a0468ba0d80ee5117826) and 4.10.0-rc6 from drm-tip: 2017y-02m-01d-11h-09m-17s UTC (eb9b7b42023edc1b5849d1ff3bef490b492067a3). The system seems to wake up immediately, and there's nothing special in dmesg, even though kernel command line includes drm.debug=0x1f $ cat /sys/power/state freeze mem disk $ echo 'mem' > /sys/power/state bash: echo: write error: Resource temporarily unavailable $ dmesg | tail [ 174.113592] systemd-journald[521]: Failed to set ACL on /var/log/journal/fe605962ccdd4f5dafb1348d1329bf81/user-1000.journal, ignoring: Operation not supported [ 209.294939] PM: Syncing filesystems ... done. [ 209.346235] PM: Preparing system for sleep (mem) System: Fedora 24 i7-3770 CPU @ 3.40GHz Intel HD 4000 Kernel config used: <a href="https://intel-gfx-ci.01.org/CI/CI_DRM_2133/kernel.config.bz2">https://intel-gfx-ci.01.org/CI/CI_DRM_2133/kernel.config.bz2</a></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>