Normal operation: system had clock skew, drifting sometimes forward and
sometimes backward; synchronization lost several times per hour.
Disabled kerneld in startup files, instead manually loading required
modules; rebooted. xntpd quickly reached equilibrium and never lost
synchronization over 5 hours of operation.
(Late addendum: it lost sync overnight; that would appear to be normal
for xntpd slowly converging on the best skew adjustment.)
Note that the test system in question never actually demand-loads/unloads
modules except during system boot and shutdown. This suggests that it is
the attempt to flush unreferenced "autoclean"-flagged modules that is
causing the clock skew.
--S.qPYXh154654=_/vger.rutgers.edu
Content-Type: text/plain; charset=us-ascii
brandon s. allbery [os/2][linux][solaris][japh] allbery@kf8nh.apk.net
system administrator [WAY too many hats] allbery@ece.cmu.edu
carnegie mellon / electrical and computer engineering KF8NH
Kiss my bits, Billy-boy.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/