From owner-freebsd-stable@FreeBSD.ORG Tue Jul 25 15:59:39 2006 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1B1D916A4DD; Tue, 25 Jul 2006 15:59:39 +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 55BD943D64; Tue, 25 Jul 2006 15:59:32 +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 5F37B1147C; Tue, 25 Jul 2006 11:59:25 -0400 (EDT) Message-ID: <44C63FFE.3080300@rogers.com> Date: Tue, 25 Jul 2006 11:59:58 -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> <200607071343.14205.jhb@freebsd.org> <44AEAB61.6000104@rogers.com> <200607071526.47758.jhb@freebsd.org> In-Reply-To: <200607071526.47758.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 Cc: stable@freebsd.org Subject: Re: Still getting 'calcru: runtime went backwards' X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 25 Jul 2006 15:59:39 -0000 John Baldwin wrote: > On Friday 07 July 2006 14:43, Mike Jakubik wrote: > >> 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? >> > > Not sure. My guess would be an overflow of some sort but given the short > uptime that likely is not the case. > > Its not always instant, sometimes its after 4 hours of uptime, and its almost always on the yarrow or swi4 process. I would really like to solve this problem, would this be an issue of the motherboard or freebsd? If its the earlier, i can contact the manufacturer, but i would appreciate more information on the problem. Thanks.