Date: Fri, 07 Jul 2006 15:44:03 -0500 From: Stephen Montgomery-Smith <stephen@math.missouri.edu> To: Mike Jakubik <mikej@rogers.com> Cc: stable@freebsd.org, freebsd-current@freebsd.org, obrien@freebsd.org, John Baldwin <jhb@freebsd.org> Subject: Re: Still getting 'calcru: runtime went backwards' Message-ID: <44AEC793.6000406@math.missouri.edu> In-Reply-To: <44AEAB61.6000104@rogers.com> References: <20060629193346.GA2548@dragon.NUXI.org> <44AD6756.4070008@rogers.com> <44ADC08B.8000408@rogers.com> <200607071343.14205.jhb@freebsd.org> <44AEAB61.6000104@rogers.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?44AEC793.6000406>