From owner-freebsd-current Mon Sep 20 8:38:45 1999 Delivered-To: freebsd-current@freebsd.org Received: from gidora.zeta.org.au (gidora.zeta.org.au [203.26.10.25]) by hub.freebsd.org (Postfix) with SMTP id 661AB15340 for ; Mon, 20 Sep 1999 08:38:35 -0700 (PDT) (envelope-from bde@zeta.org.au) Received: (qmail 22276 invoked from network); 20 Sep 1999 15:38:32 -0000 Received: from d161.syd2.zeta.org.au (203.26.9.33) by gidora.zeta.org.au with SMTP; 20 Sep 1999 15:38:32 -0000 Date: Tue, 21 Sep 1999 01:38:25 +1000 (EST) From: Bruce Evans X-Sender: bde@alphplex.bde.org To: Poul-Henning Kamp Cc: Michael Reifenberger , Warner Losh , Andrzej Bialecki , "Rodney W. Grimes" , Matthew Dillon , N , current@FreeBSD.ORG Subject: Re: 2xPIIIx450 results & NFS results In-Reply-To: <12842.937688435@critter.freebsd.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > I remember this one too. I think the problem is that we fail to > service the RTC intr for some reason. This patch was only a > workaround, and received a verbal broadside from Bruce if I > remember right. > > Maybe it should be added under a sysctl until a better solution > is know. > > --- clock.c Sat Sep 18 22:41:40 1999 > +++ clock.c.new Sun Sep 5 13:21:35 1999 > @@ -203,4 +203,6 @@ > clkintr(struct clockframe frame) > { > + while (rtcin(RTC_INTR) & RTCIR_PERIOD) > + statclock(&frame); > if (timecounter->tc_get_timecount == i8254_get_timecount) { > disable_intr(); Use a watchdog timeout like you should for any device that may hang. Don't waste time running it every clock tick. ISTR that we thought that the bug might be caused by a bug in unwanted SMI interrupt handling. Bruce To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message