From owner-freebsd-current Sat Nov 21 08:01:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA21266 for freebsd-current-outgoing; Sat, 21 Nov 1998 08:01:22 -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 IAA21261 for ; Sat, 21 Nov 1998 08:01:20 -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 QAA07974; Sat, 21 Nov 1998 16:55:20 +0100 (CET) To: Eivind Eklund cc: Barrett Richardson , garman@earthling.net, current@FreeBSD.ORG Subject: Re: more dying daemons In-reply-to: Your message of "Sat, 21 Nov 1998 16:43:44 +0100." <19981121164344.E17306@follo.net> Date: Sat, 21 Nov 1998 16:55:20 +0100 Message-ID: <7972.911663720@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG >We can't take 3.0 to be -STABLE until >this bug and the clock bug is solved. 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. I'm currently running my torture tests on some patches which reduces the rate at which we rotate the timecounter structures, this helps a lot, and a kernel option will provide tweak-room for specific bad hardware. -- 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