From nobody@FreeBSD.org  Fri Oct 27 19:21:40 2006
Return-Path: <nobody@FreeBSD.org>
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 07F2D16A403
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 27 Oct 2006 19:21:40 +0000 (UTC)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (www.freebsd.org [216.136.204.117])
	by mx1.FreeBSD.org (Postfix) with ESMTP id CBBBB43D46
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 27 Oct 2006 19:21:39 +0000 (GMT)
	(envelope-from nobody@FreeBSD.org)
Received: from www.freebsd.org (localhost [127.0.0.1])
	by www.freebsd.org (8.13.1/8.13.1) with ESMTP id k9RJLbLH039895
	for <freebsd-gnats-submit@FreeBSD.org>; Fri, 27 Oct 2006 19:21:37 GMT
	(envelope-from nobody@www.freebsd.org)
Received: (from nobody@localhost)
	by www.freebsd.org (8.13.1/8.13.1/Submit) id k9RJLbv3039885;
	Fri, 27 Oct 2006 19:21:37 GMT
	(envelope-from nobody)
Message-Id: <200610271921.k9RJLbv3039885@www.freebsd.org>
Date: Fri, 27 Oct 2006 19:21:37 GMT
From: "Jeffrey D. Brower"<Jeff@PointHere.net>
To: freebsd-gnats-submit@FreeBSD.org
Subject: Clock running at 2x speed of wall clock
X-Send-Pr-Version: www-3.0

>Number:         104867
>Category:       i386
>Synopsis:       Clock running at 2x speed of wall clock
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-i386
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Oct 27 19:30:19 GMT 2006
>Closed-Date:    Sun May 11 23:19:09 UTC 2008
>Last-Modified:  Sun May 11 23:19:09 UTC 2008
>Originator:     Jeffrey D. Brower
>Release:        FreeBSD 6.1-Release-p6 i386
>Organization:
Green Visor, Inc.
>Environment:
FreeBSD 6.1-Release-p6 i386 #1
>Description:
date command shows os time advancing exactly 2x the speed of the wall clock.

Motherboard:  ASUS P5A-B ACPI Bios Rev 1011 (current for this board)
CPU:  AMD-K6-III/450

sysctl kern.clockrate reports hz=1000, tick=1000, profhz=1024, stathz=128

kernel recompiled to include CLK_USE_I8254_CALIBRATION and the condition does not change, nor does the output of sysctl.kern.clockrate

>How-To-Repeat:
use date command.  wait exactly 1 minute. use date command.  Elapsed time will show 2 minutes have passed on the computer.
>Fix:

>Release-Note:
>Audit-Trail:

From: Bruce Cran <bruce@cran.org.uk>
To: bug-followup@FreeBSD.org, Jeff@PointHere.net
Cc:  
Subject: Re: i386/104867: Clock running at 2x speed of wall clock
Date: Fri, 09 May 2008 22:31:29 +0100

 Could you check which timecounter is being used, with the 
 kern.timecounter.hardware sysctl?  The ACPI-safe source is known to run 
 far too fast on many systems, and it's better to use i8254 instead: try 
 putting the following in /etc/sysctl.conf and rebooting
 
 kern.timecounter.hardware=i8254
 
 If the clock is still running slightly fast (e.g. 1s per minute) then 
 you can configure ntpd to track and correct the drift. There's a guide 
 to setting it up in the handbook at 
 http://www.freebsd.org/doc/en/books/handbook/network-ntp.html
 
 -- 
 Bruce Cran

From: "Jeffrey Brower" <Jeff@PointHere.net>
To: <bug-followup@FreeBSD.org>,
	<Jeff@PointHere.net>
Cc: "'Bruce Cran'" <bruce@cran.org.uk>
Subject: Re: i386/104867: Clock running at 2x speed of wall clock
Date: Fri, 9 May 2008 19:58:23 -0400

 This is a multi-part message in MIME format.
 
 ------=_NextPart_000_0692_01C8B20F.0A7D8170
 Content-Type: text/plain;
 	charset="us-ascii"
 Content-Transfer-Encoding: 7bit
 
 I verified that the timecounter was indeed i8254 after I recompiled with
 that option and it still ran double time.
  
 Everything I tried failed - even NTP gave up because it was constantly
 slewing.  No one could solve it and I never got an answer so I ended up
 pulling the box and replacing it with a more modern motherboard about a year
 and a half ago and I have had no problems since.
  
 Frankly, the board was past its prime anyway - but it was fine for a
 dedicated firewall if I could have gotten it to work.  I just needed the
 clock to be right so that the logs would match in case I needed to do
 forensics.
  
 --  Jeff
  
 
 ------=_NextPart_000_0692_01C8B20F.0A7D8170
 Content-Type: text/html;
 	charset="us-ascii"
 Content-Transfer-Encoding: quoted-printable
 
 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
 <HTML><HEAD>
 <META content=3D"text/html; charset=3Dus-ascii" =
 http-equiv=3DContent-Type>
 <META name=3DGENERATOR content=3D"MSHTML 6.00.6001.17184"></HEAD>
 <BODY>
 <DIV><SPAN class=3D578224223-09052008><FONT face=3DVerdana>I verified =
 that the=20
 timecounter was indeed i8254 after I recompiled with that option and it =
 still=20
 ran double time.</FONT></SPAN></DIV>
 <DIV><SPAN class=3D578224223-09052008><FONT=20
 face=3DVerdana></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=3D578224223-09052008><FONT face=3DVerdana>Everything I =
 tried failed=20
 - even NTP gave up because it was constantly slewing.&nbsp; No=20
 one&nbsp;could&nbsp;solve it and I never got an answer so I ended up =
 pulling the=20
 box and replacing it with a more modern motherboard about a year and a =
 half=20
 ago&nbsp;and I have had no problems since.</FONT></SPAN></DIV>
 <DIV><SPAN class=3D578224223-09052008><FONT=20
 face=3DVerdana></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=3D578224223-09052008><FONT =
 face=3DVerdana>Frankly,&nbsp;the=20
 board&nbsp;was past its prime anyway - but&nbsp;it was fine for a =
 dedicated=20
 firewall if I could have gotten it to work.&nbsp; I just needed the =
 clock to be=20
 right so that the logs would match in case I needed to do=20
 forensics.</FONT></SPAN></DIV>
 <DIV><SPAN class=3D578224223-09052008><FONT=20
 face=3DVerdana></FONT></SPAN>&nbsp;</DIV>
 <DIV><SPAN class=3D578224223-09052008><FONT face=3DVerdana>--&nbsp;=20
 Jeff</FONT></SPAN></DIV>
 <DIV><FONT face=3DVerdana></FONT>&nbsp;</DIV></BODY></HTML>
 
 ------=_NextPart_000_0692_01C8B20F.0A7D8170--
 
State-Changed-From-To: open->closed 
State-Changed-By: vwe 
State-Changed-When: Sun May 11 23:18:14 UTC 2008 
State-Changed-Why:  

according to Bruce, the issue does not occur anymore as the machine 
has been swapped. 

http://www.freebsd.org/cgi/query-pr.cgi?pr=104867 
>Unformatted:
