From owner-freebsd-current Wed Nov 24 17:16:13 1999 Delivered-To: freebsd-current@freebsd.org Received: from smtp1.xs4all.nl (smtp1.xs4all.nl [194.109.127.48]) by hub.freebsd.org (Postfix) with ESMTP id 75D1815124 for ; Wed, 24 Nov 1999 17:16:04 -0800 (PST) (envelope-from niels@bakker.net) Received: from liquid.tpb.net (arctic.xs4all.nl [194.109.37.82]) by smtp1.xs4all.nl (8.9.3/8.9.3) with ESMTP id CAA04914 for ; Thu, 25 Nov 1999 02:15:14 +0100 (CET) Received: from localhost (niels@localhost) by liquid.tpb.net (8.9.3/8.9.3/Debian/GNU) with ESMTP id CAA03912 for ; Thu, 25 Nov 1999 02:15:13 +0100 Date: Thu, 25 Nov 1999 02:15:13 +0100 (CET) From: N X-Sender: niels@liquid.tpb.net To: current@FreeBSD.ORG Subject: Re: calcru() warnings... In-Reply-To: <36187.943470027@critter.freebsd.dk> Message-ID: <9911250213010.3257-100000@liquid.tpb.net> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Poul-Henning Kamp wrote: > I still hear reports of sporadic calcru() warnings. > > If any of you see these, could you try to see if they correlate > to the uptime of the machine in question ? Should they start or stop when a machine has been running a while? I see neither (negative calcru notices in dmesg start at boot time and didn't stop until the box had a kernel panic last Saturday evening, after about two weeks uptime). FWIW, the messages started occurring when I switched from a pre-signal to post-signal change kernel and world. -- Niels. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message