From owner-freebsd-stable@FreeBSD.ORG Fri Jul 7 20:44:13 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 07A5216A4DF; Fri, 7 Jul 2006 20:44:13 +0000 (UTC) (envelope-from stephen@math.missouri.edu) Received: from sccmmhc91.asp.att.net (sccmmhc91.asp.att.net [204.127.203.211]) by mx1.FreeBSD.org (Postfix) with ESMTP id DAA9643D5C; Fri, 7 Jul 2006 20:44:09 +0000 (GMT) (envelope-from stephen@math.missouri.edu) Received: from [10.0.0.4] (12-216-255-142.client.mchsi.com[12.216.255.142]) by sccmmhc91.asp.att.net (sccmmhc91) with ESMTP id <20060707204405m9100860lde>; Fri, 7 Jul 2006 20:44:08 +0000 Message-ID: <44AEC793.6000406@math.missouri.edu> Date: Fri, 07 Jul 2006 15:44:03 -0500 From: Stephen Montgomery-Smith User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20060617 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Mike Jakubik References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> <44AEAB61.6000104@rogers.com> In-Reply-To: <44AEAB61.6000104@rogers.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: stable@freebsd.org, freebsd-current@freebsd.org, obrien@freebsd.org, John Baldwin 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: Fri, 07 Jul 2006 20:44:13 -0000 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? > >> 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. I used to be able to get these predictably on FreeBSD 5, except then it could actually cause a panic. If you run "top -s 0" (as root) you can get these errors arriving at a spectacular rate.