From owner-freebsd-questions  Thu Sep  6 19:42:25 2001
Delivered-To: freebsd-questions@freebsd.org
Received: from calcon.calcon.net (calcon.net [63.149.52.2])
	by hub.freebsd.org (Postfix) with ESMTP
	id 0722137B403; Thu,  6 Sep 2001 19:42:17 -0700 (PDT)
Received: from calcon.net (vpn1.calcon.net [63.149.52.253])
	by calcon.calcon.net (8.11.2/8.11.2) with ESMTP id f872ffR07032;
	Thu, 6 Sep 2001 21:41:42 -0500
Message-ID: <3B983405.BDE54121@calcon.net>
Date: Thu, 06 Sep 2001 21:42:13 -0500
From: Douglas Egan <degan@calcon.net>
X-Mailer: Mozilla 4.75 [en] (X11; U; NetBSD 1.5 i386)
X-Accept-Language: en
MIME-Version: 1.0
To: clemensF <rabat@web.de>, Greg Lehey <grog@FreeBSD.ORG>,
	FreeBSD Questions <questions@FreeBSD.ORG>
Subject: Re: microuptime() went backwards
References: <20010830060127.L19000@spotteswoode.yi.org> <20010831111324.A57354@wantadilla.lemis.com> <20010901002955.C708@spotteswoode.yi.org> <3B92EC6D.6CC4BCD0@calcon.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-questions@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-questions.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-questions>
List-Unsubscribe: <mailto:majordomo@FreeBSD.ORG?subject=unsubscribe%20freebsd-questions>
X-Loop: FreeBSD.ORG

Using ABit KT7A-Raid MoBo.  Drives on HPT370 are ad4 and ad6.

I can get this to happen as soon as I access my drives on the HPT370 ATA
bus.  I am using 2 Western Digital 60G ATA-100 drives.  I am configuring
a vinum mirror on them.  As soon as I 'newfs -v /dev/vinum/mirror' the
messages start coming out.  It is not just a vinum problem, as it
happened when I wasn't running vinum.  Accessing the drives with vinum
is a guarantee of getting it to happen.

I am going to remove APM from the kernel to see if it goes away.  Is the
comment from a June 28, 2000 post to 'FreeBSD-stable' true? 

" > I explained this to you at Usenix, actually.  It has nothing to do
with 
> APM, it has to do with the selection of clocks available with/without APM 
> compiled into the kernel - there is probably either a bug in the TSC 
> hardware on this CPU, or (more likely) a bug in the timecounter code 
> (since people see this on !APM systems already).

s/TSC hardware/i8254 hardware/

(the TSC is disabled when APM is compiled in, and this forces the use of 
the i8254)

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