From owner-freebsd-current  Sat Nov 21 08:55:52 1998
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id IAA26824
          for freebsd-current-outgoing; Sat, 21 Nov 1998 08:55:52 -0800 (PST)
          (envelope-from owner-freebsd-current@FreeBSD.ORG)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.15.68.22])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA26819
          for <current@FreeBSD.ORG>; Sat, 21 Nov 1998 08:55:49 -0800 (PST)
          (envelope-from bde@godzilla.zeta.org.au)
Received: (from bde@localhost)
	by godzilla.zeta.org.au (8.8.7/8.8.7) id DAA21545;
	Sun, 22 Nov 1998 03:54:46 +1100
Date: Sun, 22 Nov 1998 03:54:46 +1100
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199811211654.DAA21545@godzilla.zeta.org.au>
To: eivind@yes.no, phk@critter.freebsd.dk
Subject: Re: more dying daemons
Cc: current@FreeBSD.ORG, garman@earthling.net, terbart@aye.net
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

>If by "the clock bug" you mean the "calcru negative..." it has been
>nailed.  Many thanks to msmith, wosch & wpaul for help in tracking
>it down.
>
>It is as predicted caused by hardclock() interrupts being disabled
>for far too long.  This seems to happen on some specific types of
>hardware, the PLIP code for the parallel port being the most readily
>available.

Erm, it is caused by _non_-hardclock() interrupts being disabled for
for too long.  This is normal for non-slow hardware connected through
a slow interface (some IDE confirguations, ISA ethernet) and for buggy
software like PLIP.

The bug is inhibited by hardclock interrupts being disabled for far too
long, since the timecounters normally don't rotate unless hardclock()
is called.

Bruce

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message