From owner-freebsd-current Mon Apr 1 04:05:36 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA21052 for current-outgoing; Mon, 1 Apr 1996 04:05:36 -0800 (PST) Received: from tfs.com (tfs.com [140.145.250.1]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA21047 for ; Mon, 1 Apr 1996 04:05:34 -0800 (PST) Received: from critter.tfs.com by tfs.com (smail3.1.28.1) with SMTP id m0u3iMO-0003w1C; Mon, 1 Apr 96 04:05 PST Received: from localhost.tfs.com (localhost.tfs.com [127.0.0.1]) by critter.tfs.com (8.6.12/8.6.12) with SMTP id MAA15518; Mon, 1 Apr 1996 12:05:18 GMT X-Authentication-Warning: critter.tfs.com: Host localhost.tfs.com didn't use HELO protocol To: Bruce Evans cc: freebsd-current@freefall.freebsd.org, kuku@gilberto.physik.rwth-aachen.de Subject: Re: calcru: negative time: In-reply-to: Your message of "Mon, 01 Apr 1996 21:15:40 +1000." <199604011115.VAA15805@godzilla.zeta.org.au> Date: Mon, 01 Apr 1996 12:05:18 +0000 Message-ID: <15516.828360318@critter.tfs.com> From: Poul-Henning Kamp Sender: owner-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >[deleted] > >calcru: negative time: -11929 usec > >calcru: negative time: -3909 usec > >calcru: negative time: -3842 usec > >calcru: negative time: -17709 usec > >calcru: negative time: -3480 usec > > This is caused by hardclock() interrupt latency. The problem is > especially noticable on i586's and i686's because any latency causes the > clock to go backwards; on i386's and i486's, the latency must be > 1 > clock tick (10000 usec) to cause problems. Normally the latency on > i586's is > 0 but < 10 usec and isn't detectable. There must be bugs > elsewhere to cause latencies of more than a few tens of usecs. My i386 has really high numbers here. Could this be a spl