From owner-cvs-all@FreeBSD.ORG  Fri Apr 30 20:20:05 2004
Return-Path: <owner-cvs-all@FreeBSD.ORG>
Delivered-To: cvs-all@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 6A3AE16A4D0
	for <cvs-all@FreeBSD.org>; Fri, 30 Apr 2004 20:20:05 -0700 (PDT)
Received: from relay.pair.com (relay.pair.com [209.68.1.20])
	by mx1.FreeBSD.org (Postfix) with SMTP id B482C43D5A
	for <cvs-all@FreeBSD.org>; Fri, 30 Apr 2004 20:20:04 -0700 (PDT)
	(envelope-from silby@silby.com)
Received: (qmail 16485 invoked from network); 1 May 2004 03:20:03 -0000
Received: from niwun.pair.com (HELO localhost) (209.68.2.70)
  by relay.pair.com with SMTP; 1 May 2004 03:20:03 -0000
X-pair-Authenticated: 209.68.2.70
Date: Fri, 30 Apr 2004 22:20:06 -0500 (CDT)
From: Mike Silbersack <silby@silby.com>
To: John Baldwin <jhb@FreeBSD.org>
In-Reply-To: <20040430220507.B8726@odysseus.silby.com>
Message-ID: <20040430221434.J749@odysseus.silby.com>
References: <200404272003.i3RK3RFZ048001@repoman.freebsd.org>
 <20040430220507.B8726@odysseus.silby.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
cc: cvs-src@FreeBSD.org
cc: src-committers@FreeBSD.org
cc: cvs-all@FreeBSD.org
Subject: Re: cvs commit: src/sys/i386/isa clock.c
X-BeenThere: cvs-all@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: CVS commit messages for the entire tree <cvs-all.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/cvs-all>
List-Post: <mailto:cvs-all@freebsd.org>
List-Help: <mailto:cvs-all-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/cvs-all>,
	<mailto:cvs-all-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 01 May 2004 03:20:05 -0000


On Fri, 30 Apr 2004, Mike Silbersack wrote:

> Does this fix a bug with clock handling?  I ask because my system's clock
> has been running fast recently, and I haven't had time to investigate why
> that is occuring...
>
> Mike "Silby" Silbersack

Hm, I just learned something interesting about my clock issue... good
thing that I was saving dmesgs for warner:

Nov 13, 2003:
CPU: Mobile Intel(R) Celeron(R) CPU 1.60GHz (1594.98-MHz 686-class CPU)

Apr 10, 2004, with ACPI:
CPU: Mobile Intel(R) Celeron(R) CPU 1.60GHz (1556.71-MHz 686-class CPU)

Apr 10, 2004, without ACPI:
CPU: Mobile Intel(R) Celeron(R) CPU 1.60GHz (1575.84-MHz 686-class CPU)

today, without ACPI:
CPU: Mobile Intel(R) Celeron(R) CPU 1.60GHz (1575.84-MHz 686-class CPU)

I also noticed this today from vmstat -i:

interrupt                          total       rate
irq0: clk                         746040        986
irq8: rtc                          95484        126

That should be 1000 & 128, if I'm not mistaken.  Are these all symptoms of
some timing code during boot messing up?

Thanks,

Mike "Silby" Silbersack