Re: [RFC/RFT patch 0/7] timekeeping: Unify clock MONOTONIC and clock BOOTTIME
From: Thomas Gleixner
Date: Thu Apr 26 2018 - 04:51:31 EST
On Thu, 26 Apr 2018, Rafael J. Wysocki wrote:
> On Thu, Apr 26, 2018 at 9:42 AM, Thomas Gleixner <tglx@xxxxxxxxxxxxx> 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: File /var/log/journal/016627c3c4784cd4812d4b7e96a34226/system.journal corrupted or uncleanly shut down, renaming and replacing.
> >> [ 212.313363] systemd-coredump: 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. :-)
And that makes you coredump, right? Brilliant choice.