From owner-freebsd-bugs@FreeBSD.ORG  Sat Apr 26 12:30:26 2003
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Delivered-To: freebsd-bugs@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B635C37B401
	for <freebsd-bugs@FreeBSD.org>; Sat, 26 Apr 2003 12:30:26 -0700 (PDT)
Received: from moghedien.mukappabeta.net (moghedien.mukappabeta.net
	[194.145.150.66])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0B5E743FAF
	for <freebsd-bugs@FreeBSD.org>; Sat, 26 Apr 2003 12:30:26 -0700 (PDT)
	(envelope-from mkb@moghedien.mukappabeta.net)
Received: by moghedien.mukappabeta.net (Postfix, from userid 1000)
	id D3C8A2D2C; Sat, 26 Apr 2003 21:30:33 +0200 (CEST)
Date: Sat, 26 Apr 2003 21:30:33 +0200
From: Matthias Buelow <mkb@mukappabeta.de>
To: Simon Walton <simonw@matteworld.com>
Message-ID: <20030426193033.GI1356@moghedien.mukappabeta.net>
References: <200304252230.h3PMUGFS078258@freefall.freebsd.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <200304252230.h3PMUGFS078258@freefall.freebsd.org>
User-Agent: Mutt/1.4.1i
cc: freebsd-bugs@FreeBSD.org
Subject: Re: i386/43491: microuptime () went backwards
X-BeenThere: freebsd-bugs@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
	<mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Apr 2003 19:30:27 -0000

Simon Walton writes:

>Subject: Re: i386/43491: microuptime () went backwards
>Date: Fri, 25 Apr 2003 15:23:31 -0700
>
>    Just to add another data point - I am also
> seeing this on a dual Pentium Pro system with
> an Intel Orion chipset. Typically after a few

Just to add to the record, I have seen this to also be part
of the effects of a broken SCSI drive, apparently with the drive's
electronics gone stale.  Sometimes just a massive stream of the
above microuptime()... messages whenever the disk was accessed,
and after some time (but not always) followed by a total lockup
with a bus reset every second (but sometimes just thousands of
microuptime() messages, system was going normal apart from that,
except for time+date and the logfile filling, of course.)
Removing the drive fixed that.

-- 
Matthias Buelow
home: mkb/at/mukappabeta.de
uni:  mkb/at/informatik.uni-wuerzburg.de