From owner-freebsd-bugs@FreeBSD.ORG Tue Mar 7 20:50:10 2006 Return-Path: X-Original-To: freebsd-bugs@hub.freebsd.org Delivered-To: freebsd-bugs@hub.freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id A83EC16A420 for ; Tue, 7 Mar 2006 20:50:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3E63E43D45 for ; Tue, 7 Mar 2006 20:50:10 +0000 (GMT) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id k27Ko94C061503 for ; Tue, 7 Mar 2006 20:50:09 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id k27Ko9qD061502; Tue, 7 Mar 2006 20:50:09 GMT (envelope-from gnats) Date: Tue, 7 Mar 2006 20:50:09 GMT Message-Id: <200603072050.k27Ko9qD061502@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org From: Kris Kennaway Cc: Subject: Re: kern/94160: Clock running very fast on SMP RELENG_4 X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: Kris Kennaway List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 07 Mar 2006 20:50:10 -0000 The following reply was made to PR kern/94160; it has been noted by GNATS. From: Kris Kennaway To: Richard Wiwatowski Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/94160: Clock running very fast on SMP RELENG_4 Date: Tue, 7 Mar 2006 15:40:10 -0500 On Tue, Mar 07, 2006 at 08:17:59AM +0000, Richard Wiwatowski wrote: > System time on my SMP FreeBSD 4.11-STABLE machine is running about 4 > times as fast as it should. I also have two other uni-processor > systems running the same version: one keeps time using ntpd with a > local stratum 2 time source and all other machines on my internal > network synchronise to that one (newton) using timed. Today I > noticed this on the 2-processor gateway box: 4.x is no longer being supported so this problem is unlikely to ever be fixed in RELENG_5. Does the problem persist with 6.x? Kris