From owner-freebsd-current@FreeBSD.ORG Fri Feb 24 05:40:38 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 354A016A422; Fri, 24 Feb 2006 05:40:38 +0000 (GMT) (envelope-from kaakun@highway.ne.jp) Received: from mx.highway.ne.jp (pip7.gate01.com [61.122.117.245]) by mx1.FreeBSD.org (Postfix) with ESMTP id E0F0143D48; Fri, 24 Feb 2006 05:40:37 +0000 (GMT) (envelope-from kaakun@highway.ne.jp) Received: from [219.0.96.106] (helo=[192.168.11.18]) by pop12.isp.us-com.jp with esmtp (Mail 4.20) id 1FCVgy-0000ek-2W; Fri, 24 Feb 2006 14:40:36 +0900 Message-ID: <43FE9BC3.5070909@highway.ne.jp> Date: Fri, 24 Feb 2006 14:38:11 +0900 From: Kazuaki Oda User-Agent: Mozilla Thunderbird 1.0.7 (X11/20051211) X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Xu References: <43FE4E26.4060507@freebsd.org> In-Reply-To: <43FE4E26.4060507@freebsd.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-current@freebsd.org Subject: Re: 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, 24 Feb 2006 05:40:38 -0000 David Xu wrote: > Just ran a stress test on 6.1-PRELEASE, and got : > > davidxu@tiger:/home/davidxu/stress2/testcases/thr1> ./thr1 > Feb 24 08:02:10 tiger login: ROOT LOGIN (root) ON ttyv1 > calcru: runtime went backwards from 39012220 usec to 39011621 usec for > pid 789 ( > thr1) > calcru: runtime went backwards from 45138436 usec to 45138007 usec for > pid 789 ( > thr1) I've been getting calcru messages on 6-STABLE when stress-testing an application linked with libpthread. As far as my experience goes, these messages are only for ones linked with libpthread. If the same application is linked with libthr, these messages go away. As I post about the same issue on -CURRENT a few days ago, I guess these messages are caused by the programs which access process states. ps(1), top(1) etc. Because if I run the following command on the test target machine, I can easily get them. % sh -c "while true; do ps ax >/dev/null; done" I hope this issue will be fixed before 6.1-RELEASE. ---- Kazuaki Oda