From owner-freebsd-current Sat Nov 21 09:19:14 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA29036 for freebsd-current-outgoing; Sat, 21 Nov 1998 09:19:14 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from critter.freebsd.dk (critter.freebsd.dk [212.242.40.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA29031 for ; Sat, 21 Nov 1998 09:19:11 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost [127.0.0.1]) by critter.freebsd.dk (8.9.1/8.8.5) with ESMTP id SAA08298; Sat, 21 Nov 1998 18:16:23 +0100 (CET) To: Bruce Evans cc: eivind@yes.no, current@FreeBSD.ORG, garman@earthling.net, terbart@aye.net Subject: Re: more dying daemons In-reply-to: Your message of "Sun, 22 Nov 1998 03:54:46 +1100." <199811211654.DAA21545@godzilla.zeta.org.au> Date: Sat, 21 Nov 1998 18:16:21 +0100 Message-ID: <8296.911668581@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <199811211654.DAA21545@godzilla.zeta.org.au>, Bruce Evans writes: >>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. No, it is caused by hardclock being called with much smaller than 1/hz in between. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." "ttyv0" -- What UNIX calls a $20K state-of-the-art, 3D, hi-res color terminal To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message