From owner-freebsd-current@FreeBSD.ORG  Mon Jun 21 19:57:39 2004
Return-Path: <owner-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 1E38D16A4CE; Mon, 21 Jun 2004 19:57:39 +0000 (GMT)
Received: from mtiwmhc12.worldnet.att.net (mtiwmhc12.worldnet.att.net
	[204.127.131.116])	by mx1.FreeBSD.org (Postfix) with ESMTP
	id 98B5A43D46; Mon, 21 Jun 2004 19:57:38 +0000 (GMT)
	(envelope-from j.e.drews@att.net)
Received: from 204.127.135.42 ([204.127.135.42])
          by worldnet.att.net (mtiwmhc12) with SMTP
          id <2004062119573111200t09b1e>; Mon, 21 Jun 2004 19:57:31 +0000
Received: from [150.148.0.27] by 204.127.135.42;
	Mon, 21 Jun 2004 19:57:34 +0000
From: j.e.drews@att.net
To: Robert Watson <rwatson@FreeBSD.org>
Date: Mon, 21 Jun 2004 19:57:34 +0000
Message-Id: <062120041957.288.40D73DAE00021BC50000012021602813029C990A9D0BD20AD206@att.net>
X-Mailer: AT&T Message Center Version 1 (May 27 2004)
X-Authenticated-Sender: ai5lLmRyZXdzQGF0dC5uZXQ=
cc: current@freebsd.org
Subject: Re: calcru: negative time ... followed by freeze
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 21 Jun 2004 19:57:39 -0000

FreeBSD CURRENT from 21 Jun 2004
Compiled with -O -pipe

Hey:

 I get this calcru also when running top. Within 30 seconds it will print a message to the effect that calcru has negative time. It happened when I was building ports simultaneously. I ignored it because I thought my clock had slowed down.


-------------- Original message from Robert Watson : -------------- 
> 
> I've now seen the following scenario happen several times in the last few 
> days while doing testing and benchmarking: I run a multi-threaded test, 
> such as super-smack, that causes a moderately high system load. I then 
> hit Ctrl-T 

> Has anyone else seen this?