From owner-freebsd-hackers Thu Oct 3 07:48:18 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id HAA00954 for hackers-outgoing; Thu, 3 Oct 1996 07:48:18 -0700 (PDT) Received: from who.cdrom.com (who.cdrom.com [204.216.27.3]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id HAA00948 for ; Thu, 3 Oct 1996 07:48:15 -0700 (PDT) Received: from pat.idt.unit.no (pat.idt.unit.no [129.241.103.5]) by who.cdrom.com (8.7.5/8.6.11) with ESMTP id HAA27972 for ; Thu, 3 Oct 1996 07:48:12 -0700 (PDT) Received: from idt.unit.no (hyll.idt.unit.no [129.241.200.3]) by pat.idt.unit.no (8.7.5/8.7.3) with ESMTP id QAA17866; Thu, 3 Oct 1996 16:37:49 +0200 (MET DST) Message-Id: <199610031437.QAA17866@pat.idt.unit.no> To: dg@root.com 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 07:11:46 -0700" References: <199610031411.HAA12090@root.com> X-Mailer: Mew version 1.03 on Emacs 19.31.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Thu, 03 Oct 1996 16:37:48 +0200 From: Tor Egge 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. All NOPs disappeared in revision 1.7 of /sys/i386/include/asmacros.h. (I'm running 2.2-current). - Tor Egge