From owner-freebsd-smp Mon Feb 8 19:12:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA22543 for freebsd-smp-outgoing; Mon, 8 Feb 1999 19:12:33 -0800 (PST) (envelope-from owner-freebsd-smp@FreeBSD.ORG) Received: from fire.starkreality.com (fire.starkreality.com [208.24.48.226]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA22530 for ; Mon, 8 Feb 1999 19:12:31 -0800 (PST) (envelope-from caesar@starkreality.com) Received: from armageddon (armageddon.starkreality.com [208.24.48.227]) by fire.starkreality.com (8.9.2/8.9.2) with SMTP id VAA20539; Mon, 8 Feb 1999 21:12:35 -0600 (CST) Message-Id: <4.1.19990208211126.00c5ab40@fire.starkreality.com> X-Sender: caesar@fire.starkreality.com X-Mailer: QUALCOMM Windows Eudora Pro Version 4.1 Date: Mon, 08 Feb 1999 21:12:24 -0600 To: Chuck Robey From: "William S. Duncanson" Subject: Re: Problems keeping time Cc: freebsd-smp@FreeBSD.ORG In-Reply-To: References: <4.1.19990208181440.03d1d4c0@fire.starkreality.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-smp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hmm...doesn't appear to be working. I'm grepping through the source trying to find the valid values for this parameter, but haven't been able to find it yet. At 20:02 2/8/99 -0500, Chuck Robey wrote: >On Mon, 8 Feb 1999, William S. Duncanson wrote: > >> I just upgraded a FreeBSD box to a SMP system (basically, I swapped out the >> MB and added a processor). Now, I'm having horrendous problems with the >> kernel clock drifting (it's running fast, about 7 seconds every 10 >> minutes). So far, xntpd seems to be keeping everything relatively close, >> but it's updating the clock every 10 minutes or so. ntpq claims that all >> of the configured peers are "insane". I'm pretty sure that this is a SMP >> issue, since it worked fine with a single processor (4.0-current). So, the >> question is, how do I fix this? >> >> Here's my kernel config. I added the "CLK_USE_I8254_CALIBRATION" after I >> noticed the problem, but it doesn't appear to have fixed it: > >I have a smp system too. I've never had to use this method, but I >recall Poul-Henning talking about it, so I'll pass it on. You can tweak >the method used to keep time via a sysctl: > >sysctl -w kern.timecounter.method=1 > >I don't know more than that, you can either experiment (and let us know >if it worked) or wait for Poul-Henning to comment. > >----------------------------+----------------------------------------------- >Chuck Robey | Interests include any kind of voice or data >chuckr@glue.umd.edu | communications topic, C programming, and Unix. >213 Lakeside Drive Apt T-1 | >Greenbelt, MD 20770 | I run picnic (FreeBSD-current) >(301) 220-2114 | and jaunt (Solaris7). >----------------------------+----------------------------------------------- > > > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-smp" in the body of the message William S. Duncanson caesar@starkreality.com The driving force behind the NC is the belief that the companies who brought us things like Unix, relational databases, and Windows can make an appliance that is inexpensive and easy to use if they choose to do that. -- Scott Adams To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message