From owner-freebsd-bugs  Sun Jun 11 15:35:15 2000
Delivered-To: freebsd-bugs@freebsd.org
Received: from newton.collab.net (24-148-31-193.na.21stcentury.net [24.148.31.193])
	by hub.freebsd.org (Postfix) with ESMTP
	id AE42837C9B0; Sun, 11 Jun 2000 15:35:11 -0700 (PDT)
	(envelope-from sussman@newton.collab.net)
Received: (from sussman@localhost)
	by newton.collab.net (8.9.3/8.9.3) id RAA06690;
	Sun, 11 Jun 2000 17:39:04 -0500 (CDT)
	(envelope-from sussman)
To: phk@FreeBSD.org
Cc: freebsd-bugs@FreeBSD.org
Subject: Re: kern/18949: infinite "microuptime() went backwards" messages -- caused by intense disk access
References: <200006101916.MAA34614@freefall.freebsd.org>
Reply-To: sussman@red-bean.com
From: Ben Collins-Sussman <sussman@newton.collab.net>
Date: 11 Jun 2000 17:39:04 -0500
In-Reply-To: phk@FreeBSD.org's message of "Sat, 10 Jun 2000 12:16:55 -0700 (PDT)"
Message-ID: <86g0qj4zcn.fsf@newton.collab.net>
Lines: 19
X-Mailer: Gnus v5.7/Emacs 20.6
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


Compiled 4.0-CURRENT kernel without apm module, and the problem seems
to be fixed.  All of the old "intense disk tests" that used to
reproducibly recreate the error now work just fine.  You can close
this issue.  Thanks!


phk@FreeBSD.org writes:

> Synopsis: infinite "microuptime() went backwards" messages -- caused by intense disk access
> 
> State-Changed-From-To: open->feedback
> State-Changed-By: phk
> State-Changed-When: Sat Jun 10 12:16:09 PDT 2000
> State-Changed-Why: 
> Please try with a kernel without APM support
> Please include dmesg and sysctl kern.timecounter output.
> 
> http://www.freebsd.org/cgi/query-pr.cgi?pr=18949


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