From owner-freebsd-current@FreeBSD.ORG Fri Jul 7 18:43:28 2006 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1C0E516A51A; Fri, 7 Jul 2006 18:43:28 +0000 (UTC) (envelope-from mikej@rogers.com) Received: from H43.C18.B96.tor.eicat.ca (H43.C18.B96.tor.eicat.ca [66.96.18.43]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1D13343D58; Fri, 7 Jul 2006 18:43:26 +0000 (GMT) (envelope-from mikej@rogers.com) Received: from [127.0.0.1] (desktop.home.local [172.16.0.200]) by H43.C18.B96.tor.eicat.ca (Postfix) with ESMTP id 1807411446; Fri, 7 Jul 2006 14:42:47 -0400 (EDT) Message-ID: <44AEAB61.6000104@rogers.com> Date: Fri, 07 Jul 2006 14:43:45 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: John Baldwin References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> In-Reply-To: <200607071343.14205.jhb@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-SpamToaster-Information: This messages has been scanned by SpamToaster http://www.digitalprogression.ca X-SpamToaster: Found to be clean X-SpamToaster-SpamCheck: not spam, SpamAssassin (not cached, score=-2.49, required 3.5, ALL_TRUSTED -1.80, BAYES_00 -2.60, DK_POLICY_SIGNSOME 0.00, DNS_FROM_RFC_ABUSE 0.20, DNS_FROM_RFC_POST 1.71) X-SpamToaster-From: mikej@rogers.com X-Spam-Status: No X-Mailman-Approved-At: Fri, 07 Jul 2006 18:46:16 +0000 Cc: stable@freebsd.org, freebsd-current@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 07 Jul 2006 18:43:28 -0000 John Baldwin wrote: > That is partly because when you run top it queries the resource usage of the > various processes via fill_kinfo_proc(). When you don't run top, no one is > asking for the resource usage numbers, so the kernel doesn't waste time > calculating them. > > Right, also running ps has the same effect. But why do these messages occur? > In both cases your errors are for a long-running kernel process that's been up > since boot. What's the uptime on your box? > > Not sure what the uptime was, this box is not in production yet so i shut it off regularly. I would guess under an hour.