From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754606AbeDZIgN (ORCPT ); Thu, 26 Apr 2018 04:36:13 -0400 Received: from mail-ot0-f194.google.com ([74.125.82.194]:40679 "EHLO mail-ot0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753780AbeDZIgI (ORCPT ); Thu, 26 Apr 2018 04:36:08 -0400 X-Google-Smtp-Source: AIpwx4/I9klQSeEJKs8rKX1PJjcRlJt3C/zcwj/M4cpVCHKFuiHbb66YazHWmsnJWUiaMU5+C2sWUwRR+SPqaTUkH2Q= MIME-Version: 1.0 In-Reply-To: References: <1996930.B4PaKZ6i1F@aspire.rjw.lan> <1858767.c2KKoU8fl2@aspire.rjw.lan> <1524726236.7572.1.camel@gmx.de> From: "Rafael J. Wysocki" Date: Thu, 26 Apr 2018 10:36:07 +0200 X-Google-Sender-Auth: kTZTKZhKNpELcoaC-vL4_Yb0YYU Message-ID: Subject: Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME To: Thomas Gleixner Cc: Mike Galbraith , "Rafael J. Wysocki" , John Stultz , Genki Sky , David Herrmann , lkml , Sergey Senozhatsky , Linus Torvalds , Peter Zijlstra , Pavel Machek , Linux PM Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner wrote: > On Thu, 26 Apr 2018, Mike Galbraith wrote: >> On Wed, 2018-04-25 at 15:03 +0200, Thomas Gleixner wrote: >> > Right, it does not matter. The real interesting one is d6ed449afdb3. >> >> FWIW, three boxen here suspend/resume fine, but repeatably exhibit the >> below after a very few minute suspend, and a short bisect fingered your >> suspect. Distro is opensuse 42.3. >> >> [ 211.113902] Restarting tasks ... done. >> [ 211.114817] PM: suspend exit >> [ 212.312993] systemd-journald[7266]: File /var/log/journal/016627c3c4784cd4812d4b7e96a34226/system.journal corrupted or uncleanly shut down, renaming and replacing. >> [ 212.313363] systemd-coredump[7264]: Detected coredump of the journal daemon itself, diverted to /var/lib/systemd/coredump/core.systemd-journal.0.0aa39276decf4f1ab6fda3464e31f9dd.582.1524720954000000. >> > > Huch, that rather looks like a genuine application bug. Well, say you set a timer to wake you up in X seconds. When you wake up, you look at a clock and see that Y seconds have passed and Y is much greater than X. I guess you'd think that something's wrong. :-)