Messages in this thread | | | Date | Thu, 26 Apr 2018 10:53:40 +0200 (CEST) | From | Thomas Gleixner <> | Subject | Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and CLOCK_BOOTTIME |
| |
On Thu, 26 Apr 2018, Rafael J. Wysocki wrote: > FWIW, here's a list of issues reported and narrowed down to the commit > in question so far I could find: > > * systemd kills daemons on resume, after >WatchdogSec seconds > of suspending (Genki Sky). [Verified that that's because systemd uses > CLOCK_MONOTONIC and expects it to not include the suspend time.] > > * systemd-journald misbehaves after resume: > systemd-journald[7266]: File /var/log/journal/016627c3c4784cd4812d4b7e96a34226/system.journal corrupted or uncleanly shut down, renaming and replacing. > ( Mike Galbraith). > > * NetworkManager reports "networking disabled" and networking is broken > after resume 50% of the time (Pavel). [May be because of systemd.] > > * MATE desktop dims the display and starts the screensaver right after > system resume (Pavel). > > * Full system hang during resume (me). [May be due to systemd or NM or both.] > > I'm not sure if all of the above can be connected to one specific thing (other > than the fact that things get confused if they expect CLOCK_MONOTONIC to not > include system suspend time).
Thanks for collecting the info. I'll amend the changelog with those.
Thanks,
tglx
| |