From owner-freebsd-questions@FreeBSD.ORG Fri Mar 19 06:55:20 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE2BC16A4CE for ; Fri, 19 Mar 2004 06:55:19 -0800 (PST) Received: from pd5mo2so.prod.shaw.ca (shawidc-mo1.cg.shawcable.net [24.71.223.10]) by mx1.FreeBSD.org (Postfix) with ESMTP id B72A343D1F for ; Fri, 19 Mar 2004 06:55:19 -0800 (PST) (envelope-from flowers@users.sourceforge.net) Received: from pd3mr2so.prod.shaw.ca (pd3mr2so-ser.prod.shaw.ca [10.0.141.178])2003)) with ESMTP id <0HUT00867VUPUE@l-daemon> for questions@freebsd.org; Fri, 19 Mar 2004 07:49:37 -0700 (MST) Received: from pn2ml9so.prod.shaw.ca (pn2ml9so-qfe0.prod.shaw.ca [10.0.121.7]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with ESMTP id <0HUT00IL7VUPH0@l-daemon> for questions@freebsd.org; Fri, 19 Mar 2004 07:49:37 -0700 (MST) Received: from sirius (h68-144-47-89.cg.shawcable.net [68.144.47.89]) by l-daemon (iPlanet Messaging Server 5.2 HotFix 1.18 (built Jul 28 2003)) with SMTP id <0HUT00L2EVUO38@l-daemon> for questions@freebsd.org; Fri, 19 Mar 2004 07:49:37 -0700 (MST) Date: Fri, 19 Mar 2004 07:49:33 -0700 From: Dan MacMillan In-reply-to: <200403191611.37914.satimis@icare.com.hk> To: Stephen Liu , questions@freebsd.org Message-id: MIME-version: 1.0 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2911.0) Content-type: text/plain; charset=iso-8859-1 Content-transfer-encoding: 7BIT Importance: Normal X-Priority: 3 (Normal) X-MSMail-priority: Normal Subject: RE: The clock is running too fast X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Mar 2004 14:55:20 -0000 Hola I'm sorry, I don't know what 'ntc' is. Do you mean 'ntp'? You can use ntp or not ... if your timing hardware is off, ntp will constantly try to slew the time back to where it should be, which will a) mean your systems concept of time is very non-linear and b) fill the log with warning messages. It's actually a good check to see if the timer's good (although an slmost equally good check is to sit there and look at the clock). I forgot to mention that besides changing /etc/sysctl.conf, you have to reboot. If you don't want to reboot, you will have to do "sysctl kern.timecounter.hardware=i8254" at a prompt. But I'm not sure if that's a value that can be set after the system boots. I suggested "i8254" because it's the only device that was supplying good time values on my system. If you have trouble with that device, you might also want to try "TSC". -Dan -----Original Message----- From: owner-freebsd-questions@freebsd.org [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Stephen Liu Sent: March 19, 2004 01:12 To: questions@freebsd.org Subject: Re: The clock is running too fast Hi Dan, Thanks for your advice. > I had a similar problem on one of the machines at work. Here is a memo I > made to myself to remind me of how to fix the problem in the future: > > The "ACPI-safe" Timecounter does not work (it is way, WAY too fast). To > get around this, add the following line to /etc/sysctl.conf: > > kern.timecounter.hardware=i8254 Added above line to /etc/sysctl.conf $ cat /etc/sysctl.conf vfs.usermount=1 kern.timecounter.hardware=i8254 Now only 2 lines in this file. I have adjusted the clock thereafter and will check it again later > There are multiple pieces of hardware capable of supplying timing > information to the OS. "dmesg | grep Timecounter" should give you a list > of all such devices. > > I think this is an ACPI-related problem, since that is the technology I > understand the least at the moment. $ dmesg | grep Timecounter Timecounter "i8254" frequency 1193182 Hz quality 0 Timecounter "ACPI-safe" frequency 3579545 Hz quality 1000 Timecounter "TSC" frequency 350797051 Hz quality 800 Timecounters tick every 10.000 msec Shall I run 'ntc' to synchronize the clock. B.R. Stephen > -----Original Message----- > From: owner-freebsd-questions@freebsd.org > [mailto:owner-freebsd-questions@freebsd.org]On Behalf Of Stephen Liu > Sent: March 18, 2004 21:47 > To: questions@freebsd.org > Subject: The clock is running too fast > > > Hi folks, > > AMD CUP > FreeBSD 5.2 > > The clock on KDE desktop is running on double speed compelling me to adjust > it > periodically. Kindly advise how to fix this problem. > > TIA > > B.R. > Stephen Liu _______________________________________________ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.org"