From owner-freebsd-questions Tue Aug 4 00:09:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA09641 for freebsd-questions-outgoing; Tue, 4 Aug 1998 00:09:13 -0700 (PDT) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from inet.chipweb.ml.org (c1003518-a.plstn1.sfba.home.com [24.1.82.47]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id AAA09636 for ; Tue, 4 Aug 1998 00:09:11 -0700 (PDT) (envelope-from ludwigp@bigfoot.com) Message-Id: <199808040709.AAA09636@hub.freebsd.org> Received: (qmail 25568 invoked from network); 4 Aug 1998 07:08:26 -0000 Received: from speedy.chipweb.ml.org (172.16.1.1) by inet.chipweb.ml.org with SMTP; 4 Aug 1998 07:08:26 -0000 X-Sender: ludwigp@mail-r X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Tue, 04 Aug 1998 00:07:12 -0700 To: Steve Reid From: Ludwig Pummer Subject: Re: calcru: negative time Cc: questions@FreeBSD.ORG In-Reply-To: References: <199808040516.WAA05531@alpha.sea-to-sky.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG At 12:04 AM 8/4/98 -0700, Steve Reid wrote: >I've seen this happen during boot (after device probe, before syslogd >starts), but usually it takes a few hours before I start to see it. Once >it starts it usually gets progressively worse until I reboot. ditto. right now i only get one per daily security check. before reboot i got 6 or so. >Since my post about the message, I have noticed a problem.. When the >message is appearing, some processes don't get all of the CPU available >to them. Beforelight (screensaver, comes with XF86) runs sluggishly, and >raplayer (3.0 for FreeBSD, dynamicly linked) plays with somewhat broken >sound. This is with a load average well below 1, and it doesn't happen >when the message isn't appearing. I notice occasional sluggishness in DNS (this machine is my DNS server). I used to run rc5des but stopped it, thinking that was the cause of the sluggishness (it might have been partly responsible anyways. but that's another topic). Any of the developers know why this would happen? Is this only happening in 486-class CPUs? Something change between 2.2.5 and 2.2.6/2.2.7 to make this happen? --Ludwig Pummer ludwigp@bigfoot.com ludwigp@chipweb.ml.org ICQ UIN: 692441 http://chipweb.home.ml.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message