From owner-freebsd-hackers Wed Apr 16 11:20:49 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA25614 for hackers-outgoing; Wed, 16 Apr 1997 11:20:49 -0700 (PDT) Received: from dg-rtp.dg.com (dg-rtp.rtp.dg.com [128.222.1.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA25600 for ; Wed, 16 Apr 1997 11:20:44 -0700 (PDT) Received: by dg-rtp.dg.com (5.4R3.10/dg-rtp-v02) id AA19938; Wed, 16 Apr 1997 14:20:08 -0400 Received: from ponds by dg-rtp.dg.com.rtp.dg.com; Wed, 16 Apr 1997 14:20 EDT Received: from lakes.water.net (lakes [10.0.0.3]) by ponds.water.net (8.8.3/8.7.3) with ESMTP id NAA13655; Wed, 16 Apr 1997 13:41:42 -0400 (EDT) Received: (from rivers@localhost) by lakes.water.net (8.8.3/8.6.9) id NAA03099; Wed, 16 Apr 1997 13:48:15 -0400 (EDT) Date: Wed, 16 Apr 1997 13:48:15 -0400 (EDT) From: Thomas David Rivers Message-Id: <199704161748.NAA03099@lakes.water.net> To: ponds!freefall.cdrom.com!freebsd-hackers, ponds!quickweb.com!mark, ponds!lakes.water.net!rivers Subject: Re: "calcru: negative time" messages (FreeBSD-2.2.1) Content-Type: text Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > On Wed, Apr 09, 1997 at 04:36:43PM -0400, Thomas David Rivers wrote: > > > > I'm getting these messages after my install of 2.2.1: > > > > Apr 9 16:30:25 numb /kernel: calcru: negative time: -330 usec > > Apr 9 16:30:25 numb /kernel: calcru: negative time: -330 usec > > > > They don't seem to obviously coincide with anythine; can anyone > > shed some light on this? > > Do you have: > options "CLK_USE_I586_CALIBRATION" > > in your kernel? On my PPro 150, without this I would randomly get these > messages all the time. My CPU speed detection would vary greatly as well. > Since I added the above option, my CPU speed is detected correctly on > boot, and I don't get ANY calcru: negative time: messsages! Happy. > > Maybe this is it? I'm assuming it's only valid for Pentium and above CPUs, > however. > > -Mark > No, I hadn't tried that. At the time, I was running a GENERIC 2.2.1 kernel. I did rebuild a kernel with Bruce's fix to isa/clock.c; and haven't seen the problem since - could it have been blocked RTC interrupts? - Dave Rivers -