From owner-freebsd-stable@FreeBSD.ORG Thu Jul 27 18:46:09 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 7BE1216A4E2; Thu, 27 Jul 2006 18:46:09 +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 9C79843D6D; Thu, 27 Jul 2006 18:46:08 +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 C3A411147D; Thu, 27 Jul 2006 14:45:55 -0400 (EDT) Message-ID: <44C90A1B.2050200@rogers.com> Date: Thu, 27 Jul 2006 14:46:51 -0400 From: Mike Jakubik User-Agent: Thunderbird 1.5.0.4 (Windows/20060516) MIME-Version: 1.0 To: John Baldwin References: <44C7ED5F.6060902@rogers.com> <200607271358.17333.jhb@freebsd.org> In-Reply-To: <200607271358.17333.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, AWL 0.00, 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, phk@freebsd.org Subject: Re: MFC of kern_resource.c (calru changes) 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: Thu, 27 Jul 2006 18:46:09 -0000 John Baldwin wrote: > On Wednesday 26 July 2006 18:31, Mike Jakubik wrote: > >> Are there any plans to MFC the last few commits to kern_resource.c to >> -STABLE? I have a number of machines which flood the logs with "calcru: >> negative runtime" messages every time w, ps or top is used, so im hoping >> these may fix the issue. >> > > I think it involves an ABI breakage, so I doubt it. > > Thats unfortunate, as i just finished extensively testing the system with -CURRENT. There are no calcru messages, and no negative timestamps on processes occurring. In fact, everything is working perfectly. Is there anything that can be done to address this problem on -STABLE?