Messages in this thread | | | From | "Rafael J. Wysocki" <> | Subject | Re: [tip:timers/urgent] Revert: Unify CLOCK_MONOTONIC and CLOCK_BOOTTIME | Date | Thu, 26 Apr 2018 09:26:52 +0200 |
| |
On Thursday, April 26, 2018 9:19:25 AM CEST Pavel Machek wrote: > Hi! > > > > > For the record, I just run plain F27, obviously with my own kernel > > > > (and a tweaked config, but it approaches just being a "make > > > > localmodconfig" of the distro config). > > > > > > So... I do have debian 8.10. > > > > Does that use systemd at all? > > pavel@duo:/data/l/linux$ systemd --version > systemd 215 > +PAM +AUDIT +SELINUX +IMA +SYSVINIT +LIBCRYPTSETUP +GCRYPT +ACL +XZ > -SECCOMP -APPARMOR
OK
> > > With 4.17-rc1, I get "networking > > > disabled" message from network manager (and broken network), about > > > half of the time.
I'm not sure if NM is affected by systemd, though.
> > > But there's more visible symptom: suspend/resume with 4.16, machine is > > > okay after resume. With 4.17-rc1, just after resume, display starts > > > dimming and screensaver will kick in. MATE desktop. > > > > Yeah, why not. It thinks that you've been inactive for the duration of system > > sleep. :-) > > Well, its rather annoying.
Yes, it is, no question about that.
> "Wake up!" (hitting a key) "OOh, I'm slowly > waking up.." (few seconds, wakeup is not instant) "and now I'm going > back to sleep".
I just wanted to say that you could expect that if the clock used by it was counting over suspend/resume.
| |