From owner-freebsd-current Tue Nov 12 9: 8:50 2002 Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id F10AC37B41E for ; Tue, 12 Nov 2002 09:08:45 -0800 (PST) Received: from dibbler.ne.client2.attbi.com (dibbler.ne.client2.attbi.com [24.61.41.247]) by mx1.FreeBSD.org (Postfix) with ESMTP id C218743E42 for ; Tue, 12 Nov 2002 09:08:44 -0800 (PST) (envelope-from rodrigc@attbi.com) Received: from dibbler.ne.client2.attbi.com (localhost [127.0.0.1]) by dibbler.ne.client2.attbi.com (8.12.6/8.12.6) with ESMTP id gACH8nmF001673 for ; Tue, 12 Nov 2002 12:08:49 -0500 (EST) (envelope-from rodrigc@dibbler.ne.client2.attbi.com) Received: (from rodrigc@localhost) by dibbler.ne.client2.attbi.com (8.12.6/8.12.6/Submit) id gACH8m9v001672 for freebsd-current@freebsd.org; Tue, 12 Nov 2002 12:08:48 -0500 (EST) Date: Tue, 12 Nov 2002 12:08:48 -0500 From: Craig Rodrigues To: freebsd-current@freebsd.org Subject: Re: Clock runs too fast Message-ID: <20021112120848.B1632@attbi.com> References: <20021112162717.GA6584@huckfinn.arved.de> <75486.1037117893@critter.freebsd.dk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <75486.1037117893@critter.freebsd.dk>; from phk@critter.freebsd.dk on Tue, Nov 12, 2002 at 05:18:13PM +0100 Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Tue, Nov 12, 2002 at 05:18:13PM +0100, Poul-Henning Kamp wrote: > Are you saying that the i8254 also runs twice as fast as it should ? It looks like it. Here is some additional output from dmesg. Does it give a clue? Calibrating clock(s) ... TSC clock: 400911902 Hz, i8254 clock: 1193190 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency Timecounter "i8254" frequency 1193182 Hz CLK_USE_TSC_CALIBRATION not specified - using old calibration method [snip] ACPI timer looks BAD min = 0, max = 5, width = 6 ACPI timer looks BAD min = 0, max = 16777210, width = 16777211 ACPI timer looks BAD min = 1, max = 16777215, width = 16777215 ACPI timer looks BAD min = 2, max = 16777204, width = 16777203 ACPI timer looks BAD min = 0, max = 16777215, width = 16777216 ACPI timer looks BAD min = 0, max = 16777215, width = 16777216 ACPI timer looks BAD min = 2, max = 16777210, width = 16777209 ACPI timer looks BAD min = 2, max = 16777208, width = 16777207 ACPI timer looks BAD min = 0, max = 16777208, width = 16777209 ACPI timer looks BAD min = 2, max = 16777215, width = 16777214 Timecounter "ACPI-safe" frequency 3579545 Hz acpi_timer0: <24-bit timer at 3.579545MHz> port 0xec08-0xec0b on acpi0 acpi_cpu0: on acpi0 [snip] Timecounters tick every 10.000 msec -- Craig Rodrigues http://www.gis.net/~craigr rodrigc@attbi.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message