From owner-freebsd-current  Wed Nov  1 01:27:53 1995
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id BAA05515
          for current-outgoing; Wed, 1 Nov 1995 01:27:53 -0800
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id BAA05505
          for <current@freebsd.org>; Wed, 1 Nov 1995 01:27:50 -0800
Received: from corbin.Root.COM (corbin [198.145.90.50]) by Root.COM (8.6.12/8.6.5) with ESMTP id BAA00252; Wed, 1 Nov 1995 01:27:49 -0800
Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.12/8.6.5) with SMTP id BAA10684; Wed, 1 Nov 1995 01:20:59 -0800
Message-Id: <199511010920.BAA10684@corbin.Root.COM>
To: "Garrett A. Wollman" <wollman@lcs.mit.edu>
cc: "Justin T. Gibbs" <gibbs@freefall.freebsd.org>, current@freebsd.org
Subject: Re: Time problems 
In-reply-to: Your message of "Tue, 31 Oct 95 12:47:55 EST."
             <9510311747.AA29686@halloran-eldar.lcs.mit.edu> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Wed, 01 Nov 1995 01:20:59 -0800
Sender: owner-current@freebsd.org
Precedence: bulk

>calibration.  There are two possible sources of error involved here:
>
>	1) The part of your chipset that emulates the timer/counter is
>operating at the wrong rate (or the DELAY function isn't working right
>for it).
>
>	2) Your CPU's cycle counter is not operating at the nominal
>rate, or its rate in MHz is not close to an integer.
>
>In talking to David Greenman about this problem, we found that one of
>his machines which exhibits this problem suffers from (1).  Other
>people have suggested (2) for their motherboards.  (David's
>motherboard took about 12 seconds to perform a ten-second delay.)

   It was the other way around - it too 8.5 seconds to do a DELAY(10000000).

-DG