Comment # 69 on bug 925873 from Stanislav Brabec

> 90clock:

As far as I remember, this quirk causes only problems.

When my machine was offline, it was much better do disable this quirk (and also
the same in the shutdown sequence).


It causes problems for two reasons:

1. The quirk itself expects system clock being better that hwclock. This is
true for NTP, but not for many machines without NTP.

2. We have /etc/adjtime feature, that works much better for machines without
NTP, as it has predictable results.

If the suspend quirk saves an system time which went off over the time, user
then probably wants to adjust the clock to the correct time. adjtime
calculation thinks that the whole drift was caused by hwclock inaccuracy, and
updates seconds per day compensation to an incorrect value. Next time, the
clock will be more shifted by this time.

Imagine that system clock went 2 minutes off while going to suspend. Quirk
written this incorrect time to hwclock. Next day user discovers the shift, and
adjusts time. /etc/adjtime will be set to 2 minutes per day. 5 das later, the
system is booted, and /etc/adjtime computes need for 10 minutes correction.