Re: CLOCK_MONOTONIC, BOOTTIME, suspend and screensaver regression

From: Pavel Machek
Date: Tue Apr 24 2018 - 08:08:19 EST

On Tue 2018-04-24 14:06:59, Pavel Machek wrote:
> Hi!
> In 4.17-rc1 I have weird problems with network manager... and I also
> have screensaver kicking just after resume.
> Searching the git logs:
> - The most interesting change is the consolidation of clock
> and clock BOOTTIME.
> Clock MONOTONIC behaves now exactly like clock BOOTTIME and
> does
> not longer ignore the time spent in suspend. A new
> clock
> MONOTONIC_ACTIVE is provived which behaves like
> clock MONOTONIC in
> kernels before this change. This allows applications
> to
> programmatically check for the clock MONOTONIC
> behaviour.
> As discussed in the review thread, this has the potential of
> breaking user space and we might have to revert
> this. Knock on wood
> that we can avoid that exercise.
> ...I believe you are breaking userspace for me. How can we check that?

And actually... how is it supposed to work? If monotonic behaves same
way as boottime, we'll have nasty thundering herd problem after
resume, riight?
(cesky, pictures)

Attachment: signature.asc
Description: Digital signature