From owner-freebsd-questions@FreeBSD.ORG Wed Mar 10 14:52:31 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 6C17F16A4CE for ; Wed, 10 Mar 2004 14:52:31 -0800 (PST) Received: from mail.filmkern.com (206-169-45-174.gen.twtelecom.net [206.169.45.174]) by mx1.FreeBSD.org (Postfix) with SMTP id 369D543D39 for ; Wed, 10 Mar 2004 14:52:31 -0800 (PST) (envelope-from darom@filmkern.com) Received: (qmail 3371 invoked by uid 5004); 10 Mar 2004 14:52:31 -0800 Received: from darom@filmkern.com by mail by uid 5001 with qmail-scanner-1.16 (spamassassin: 2.54. Clear:. Processed in 0.025578 secs); 10 Mar 2004 22:52:31 -0000 Received: from unknown (HELO filmkern.com) (127.0.0.1) by 0 with SMTP; 10 Mar 2004 14:52:30 -0800 Received: from 206.169.45.183 (SquirrelMail authenticated user darom@filmkern.com) by mail.filmkern.com with HTTP; Wed, 10 Mar 2004 14:52:30 -0800 (PST) Message-ID: <16220.206.169.45.183.1078959150.squirrel@mail.filmkern.com> Date: Wed, 10 Mar 2004 14:52:30 -0800 (PST) From: "Denis R." To: In-Reply-To: <404F92E7.2090702@ukug.uk.freebsd.org> References: <22997.206.169.45.183.1078952848.squirrel@mail.filmkern.com> <404F92E7.2090702@ukug.uk.freebsd.org> X-Priority: 3 Importance: Normal X-Mailer: SquirrelMail (version 1.2.11) MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit cc: freebsd-questions@freebsd.org Subject: Re: SOLVED :-) Re: Wierd time changes X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: darom@filmkern.com List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Mar 2004 22:52:31 -0000 Mark, No clue from sysctl -a. Yes, I've looked through archives and google. Since I don't see a lot of performance improvement from using the second CPU, I will leave this issue alone for now. Hopefully, someone will post a sweet solution to this bugging issue. Thanks for your help, Denis > Only to try with different value for kern.timecounter.method, but that's > just a guess. Does the output from ''sysctl -a kern.timecounter'' yield > any clues? > > Apart from that I really can't be of any help. I take it you've done the > obvious and searched the mailing list and Google?