From owner-freebsd-bugs  Tue Nov  5  5:20: 5 2002
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id F14BF37B404
	for <freebsd-bugs@hub.freebsd.org>; Tue,  5 Nov 2002 05:20:03 -0800 (PST)
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by mx1.FreeBSD.org (Postfix) with ESMTP id AEB8B43E6E
	for <freebsd-bugs@hub.freebsd.org>; Tue,  5 Nov 2002 05:20:03 -0800 (PST)
	(envelope-from gnats@FreeBSD.org)
Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1])
	by freefall.freebsd.org (8.12.6/8.12.6) with ESMTP id gA5DK3x3023170
	for <freebsd-bugs@freefall.freebsd.org>; Tue, 5 Nov 2002 05:20:03 -0800 (PST)
	(envelope-from gnats@freefall.freebsd.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.12.6/8.12.6/Submit) id gA5DK31v023169;
	Tue, 5 Nov 2002 05:20:03 -0800 (PST)
Date: Tue, 5 Nov 2002 05:20:03 -0800 (PST)
Message-Id: <200211051320.gA5DK31v023169@freefall.freebsd.org>
To: freebsd-bugs@FreeBSD.org
Cc: 
From: Eirik Oeverby <ltning@anduin.net>
Subject: Re: i386/43491: microuptime () went backwards
Reply-To: Eirik Oeverby <ltning@anduin.net>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.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-bugs>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

The following reply was made to PR i386/43491; it has been noted by GNATS.

From: Eirik Oeverby <ltning@anduin.net>
To: freebsd-gnats-submit@FreeBSD.org,
	paul.leduc@appliedheuristics.com
Cc:  
Subject: Re: i386/43491: microuptime () went backwards
Date: Tue, 05 Nov 2002 14:17:22 +0100

 Hi,
 
 I see this problem on a recently installed SMP machine. It is built 
 around the Elitegroup DV6AA motherboard, twin P3-800mhz CPU's.
 I have tested with and without APM enabled in BIOS/Kernel, in all 
 possible combinations.
 The problem does not occur immediately, but only after the machine has 
 been running for a few minutes. Depending on the load (esp. IDE disk 
 I/O) it will happen sooner or later (later with less load).
 
 To those suggesting to replace the hardware:
 THIS IS NOT AN OPTION!!!
 I cannot believe that anyone can be so blatant as to suggest that people 
 should replace hardware that has worked very well in the past and/or 
 works perfectly with whatever else they throw at them.
 Sorry. Had to vent that.
 
 I will continue trying various combinations of system timing, timing 
 methods, BIOS settings, and hardware.
 
 Best regards,
 /Eirik Oeverby
 

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