CLOCK_MONOTONIC change reverted

CLOCK_MONOTONIC change reverted

See e.g. Why is there a Linux kernel policy to never break user space?

Specifically also, we really want people to be testing new upstream kernels and reporting regressions. (That's probably not a very compelling activity on its own, but there are more positive reasons people play with running upstream kernels as well. For example, hoping it fixes a regression introduced in the previous version :). They will be much less willing to test and report, if we're deliberately breaking their system.

Making a change which kills logind on any suspend over 3 minutes, which then kills X / gnome-shell, definitely counts as breakage :-).

AFAIK this change also breaks rtkit, for example.

Here's another error you get if you suspend the host that's running a VM (as I mentioned on the previous LWN.net article, this causes the same problem, due to a bug somewhere in qemu/KVM):

rtkit-daemon[1218]: The canary thread is apparently starving. Taking action.
rtkit-daemon[1218]: Demoting known real-time threads.
rtkit-daemon[1218]: Demoted 0 threads.