Date: Fri, 30 Apr 2004 22:20:06 -0500 (CDT) From: Mike Silbersack <silby@silby.com> To: John Baldwin <jhb@FreeBSD.org> Cc: cvs-all@FreeBSD.org Subject: Re: cvs commit: src/sys/i386/isa clock.c Message-ID: <20040430221434.J749@odysseus.silby.com> In-Reply-To: <20040430220507.B8726@odysseus.silby.com> References: <200404272003.i3RK3RFZ048001@repoman.freebsd.org> <20040430220507.B8726@odysseus.silby.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040430221434.J749>