linux-kernel - Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and CLOCK

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: Windows password security audit tool. GUI, reports in PDF.

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

Message-ID: <20180425184140.6b6e524d@vmware.local.home>
Date:   Wed, 25 Apr 2018 18:41:40 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     "Rafael J. Wysocki" <rjw@...ysocki.net>
Cc:     Linus Torvalds <torvalds@...ux-foundation.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Mark Salyzyn <salyzyn@...roid.com>,
        Ingo Molnar <mingo@...nel.org>,
        Peter Zijlstra <peterz@...radead.org>,
        John Stultz <john.stultz@...aro.org>,
        Peter Anvin <hpa@...or.com>,
        Michael Kerrisk <mtk.manpages@...il.com>,
        Prarit Bhargava <prarit@...hat.com>,
        Pavel Machek <pavel@....cz>, Kevin Easton <kevin@...rana.org>,
        Dmitry Torokhov <dmitry.torokhov@...il.com>,
        Petr Mladek <pmladek@...e.com>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        SergeySenozhatsky <sergey.senozhatsky@...il.com>,
        Jonathan Corbet <corbet@....net>,
        linux-tip-commits@...r.kernel.org
Subject: Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and
 CLOCK_BOOTTIME

On Wed, 25 Apr 2018 22:57:12 +0200
"Rafael J. Wysocki" <rjw@...ysocki.net> wrote:

> FWIW, I run (64-bit) OpenSUSE 42.3 on the failing machine (Acer Aspire S5) with
> my own kernel (custom config based on the distro one).
> 
> The problem here is that the machine doesn't resume from S2R.  It appears to
> just hang somewhere around where we return to user space.  However, to trigger
> the issue it needs to stay in suspend for several minutes (not sure how many
> exactly).  If it is just back-to-back suspend/resume, it will resume correctly.

I guess the question that needs to be asked is, have you tried a kernel
with this commit reverted and it works? I'd play a bit going back and
forth between two kernels, one with the commit and one without and no
other differences, to make sure that is indeed the problem commit.

-- Steve