From owner-freebsd-current  Wed Dec 19 14:59:26 2001
Delivered-To: freebsd-current@freebsd.org
Received: from apollo.backplane.com (apollo.backplane.com [216.240.41.2])
	by hub.freebsd.org (Postfix) with ESMTP id 4EC1537B416
	for <freebsd-current@freebsd.org>; Wed, 19 Dec 2001 14:59:22 -0800 (PST)
Received: (from dillon@localhost)
	by apollo.backplane.com (8.11.6/8.9.1) id fBJMxMF90892;
	Wed, 19 Dec 2001 14:59:22 -0800 (PST)
	(envelope-from dillon)
Date: Wed, 19 Dec 2001 14:59:22 -0800 (PST)
From: Matthew Dillon <dillon@apollo.backplane.com>
Message-Id: <200112192259.fBJMxMF90892@apollo.backplane.com>
To: freebsd-current@freebsd.org
Subject: Seeing a lot of 'microuptime() went backwards' messages during heavy disk I/O
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-current.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo@FreeBSD.ORG?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo@FreeBSD.ORG?subject=subscribe%20freebsd-current>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-current>
X-Loop: FreeBSD.ORG

    I'm seeing a lot of this during heavy disk I/O (5 postmark benchmarks
    running in parallel):

microuptime() went backwards (44525.3954411 -> 44524.563978)
microuptime() went backwards (57425.4282241 -> 57424.766121)
microuptime() went backwards (57425.4282241 -> 57424.845844)
microuptime() went backwards (60724.4427887 -> 60724.686232)
microuptime() went backwards (60724.4427887 -> 60724.768808)
microuptime() went backwards (61685.4418845 -> 61685.102724)
microuptime() went backwards (61924.3906516 -> 61924.246151)
microuptime() went backwards (62344.3800035 -> 62344.415407)

    Anyone know what's up?

					-Matt
					Matthew Dillon 
					<dillon@backplane.com>

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message