From owner-freebsd-hackers  Thu Oct  3 07:12:55 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id HAA29029
          for hackers-outgoing; Thu, 3 Oct 1996 07:12:55 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA29022
          for <freebsd-hackers@freebsd.org>; Thu, 3 Oct 1996 07:12:51 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.5/8.6.5) with SMTP id HAA12090; Thu, 3 Oct 1996 07:11:46 -0700 (PDT)
Message-Id: <199610031411.HAA12090@root.com>
X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol
To: Tor Egge <Tor.Egge@idt.ntnu.no>
cc: bde@zeta.org.au, freebsd-hackers@freebsd.org
Subject: Re: Interrupt lossage in FreeBSD-current. 
In-reply-to: Your message of "Thu, 03 Oct 1996 15:14:31 +0200."
             <199610031314.PAA15348@pat.idt.unit.no> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Thu, 03 Oct 1996 07:11:46 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I no longer see this as a latency issue with regard to the RTC.
>Something else was causing one RTC interrupt to be lost.

   I used to see a problem with using "DUMMY_NOPS" where the RTC interrupt
acknowledge would be missed due to the time-delay constraints not being met.
If you're using DUMMY_NOPS, then this could be your problem. If you're not,
then the problem could be caused by your system eating the inb(0x84) without
adding enough delay.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project