From owner-freebsd-alpha Tue Sep 21 2: 3:19 1999 Delivered-To: freebsd-alpha@freebsd.org Received: from herring.nlsystems.com (nlsys.demon.co.uk [158.152.125.33]) by hub.freebsd.org (Postfix) with ESMTP id EA5C714CC0 for ; Tue, 21 Sep 1999 02:03:15 -0700 (PDT) (envelope-from dfr@nlsystems.com) Received: from salmon.nlsystems.com (salmon.nlsystems.com [10.0.0.3]) by herring.nlsystems.com (8.9.3/8.8.8) with ESMTP id KAA64018; Tue, 21 Sep 1999 10:04:21 +0100 (BST) (envelope-from dfr@nlsystems.com) Date: Tue, 21 Sep 1999 10:04:20 +0100 (BST) From: Doug Rabson To: Valentin Nechayev Cc: freebsd-alpha@freebsd.org Subject: Re: timer bad In-Reply-To: <19990920170311.J8323@lucky.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-alpha@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Mon, 20 Sep 1999, Valentin Nechayev wrote: > System: 3.3-release on AlphaPC 164SX (SRM V5.3-3). On startup, kernel writes: > > Timecounter "alpha" frequency 391549955 Hz > > (real values on a series of successive boots was: 342MHz, 339MHz, 336MHz, > 333MHz; after poweroff and poweron: 421MHz, 391MHz). Real speed is ~533 MHz, > and hence kernel time speed on the last startup, when 391MHz was detected, > was 136% of true one (tested with ntpdate). With 3.2-RELEASE, detection > is true (531...MHz). > > I fixed it by disabling calibrate_clocks() of sys/alpha/alpha/clock.c: > > and now timer works normally. > > Is it hardware, firmware or software problem, and how to fix it? I haven't seen this before. I would guess software but you have a fairly recent SRM version. I had to add this calibration code since SRM reports an inaccurate clock frequency for some machines, causing noticable clock drift. -- Doug Rabson Mail: dfr@nlsystems.com Nonlinear Systems Ltd. Phone: +44 181 442 9037 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-alpha" in the body of the message