From owner-freebsd-current  Sun Nov 12 09:30:11 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id JAA16201
          for current-outgoing; Sun, 12 Nov 1995 09:30:11 -0800
Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id JAA16196
          for <current@freebsd.org>; Sun, 12 Nov 1995 09:30:07 -0800
Received: (from imb@localhost)
	by asstdc.scgt.oz.au (8.6.12/BSD-4.4)
	id EAA00906; Mon, 13 Nov 1995 04:29:53 +1100
From: michael butler <imb@scgt.oz.au>
Message-Id: <199511121729.EAA00906@asstdc.scgt.oz.au>
Subject: Re: calcru: negative time: %qd usec
To: bde@zeta.org.au (Bruce Evans)
Date: Mon, 13 Nov 1995 04:29:50 +1100 (EST)
Cc: current@freebsd.org
In-Reply-To: <199511121717.EAA17041@godzilla.zeta.org.au> from "Bruce Evans" at Nov 13, 95 04:17:27 am
X-Mailer: ELM [version 2.4 PL24beta]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Content-Length: 554       
Sender: owner-current@freebsd.org
Precedence: bulk

> It is caused by the clock running backwards.

That's cute :-)

> The message comes from kern_resource.c.  The bogus time [difference]
> probably comes from a bug in microtime().  Perhaps the 8254 counter is
> not being read correctly, or a time daemon is fiddling with the clock.

I am running xntpd but, with the machine under load (e.g. make world),
these messages appear at 5-10 second intervals even though there is no
time "stepping" going on .. only adjtime to correct a ~13ppm drift with
~53ppm stability (steps are very infrequent),

	michael