From owner-freebsd-current Mon Sep 20 8:55:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (Postfix) with ESMTP id 1AD701557B for ; Mon, 20 Sep 1999 08:55:01 -0700 (PDT) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.3/8.9.2) with ESMTP id RAA23504; Mon, 20 Sep 1999 17:52:16 +0200 (CEST) (envelope-from phk@critter.freebsd.dk) To: Bruce Evans 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: Your message of "Tue, 21 Sep 1999 01:38:25 +1000." Date: Mon, 20 Sep 1999 17:52:16 +0200 Message-ID: <23502.937842736@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message , Bruce E vans writes: >> 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. If anybody can reproduce this reliably on a *BX chipset I have code that will block SMI interrupts we can test with... -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." FreeBSD -- It will take a long time before progress goes too far! To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message