From owner-freebsd-bugs  Fri Jun  4 11:10: 5 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21])
	by hub.freebsd.org (Postfix) with ESMTP id DEDB21517C
	for <freebsd-bugs@FreeBSD.org>; Fri,  4 Jun 1999 11:10:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: (from gnats@localhost)
	by freefall.freebsd.org (8.9.3/8.9.2) id LAA72744;
	Fri, 4 Jun 1999 11:10:02 -0700 (PDT)
	(envelope-from gnats@FreeBSD.org)
Received: by hub.freebsd.org (Postfix, from userid 32767)
	id CB25A14C01; Fri,  4 Jun 1999 11:05:21 -0700 (PDT)
Message-Id: <19990604180521.CB25A14C01@hub.freebsd.org>
Date: Fri,  4 Jun 1999 11:05:21 -0700 (PDT)
From: dwhite@pond.net
To: freebsd-gnats-submit@freebsd.org
X-Send-Pr-Version: www-1.0
Subject: kern/12022: System clock timewarps
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         12022
>Category:       kern
>Synopsis:       System clock timewarps
>Confidential:   no
>Severity:       serious
>Priority:       high
>Responsible:    freebsd-bugs
>State:          open
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Fri Jun  4 11:10:01 PDT 1999
>Closed-Date:
>Last-Modified:
>Originator:     Doug White
>Release:        3.1-RELEASE and later
>Organization:
Pacific Crest Networks, Inc.
>Environment:
FreeBSD squid.pcrest.net 3.1-RELEASE FreeBSD 3.1-RELEASE #1: Mon May 10 23:00:37 PDT 1999     root@squid.pcrest.net:/usr/src/sys/compile/SQUID  i386

>Description:
The TSC time calibration code appears badly broken.  It cannot get a 
consistent read off the system TSC and miscalculates the CPU clock.  
Furthermore, it's causing the system clock to run fast at the rate of 
about 5 minutes/hour.  

Normally, the TSC should sync to 90000689 or thereabouts.  On the problem
machine, we have the following values:
May 10 19:53:45 myname /kernel: Timecounter "TSC"  frequency 84792684 Hz
May 10 19:58:23 myname /kernel: Timecounter "TSC"  frequency 78478318 Hz
May 10 20:04:29 myname /kernel: Timecounter "TSC"  frequency 90205024 Hz
May 10 20:10:49 squid /kernel: Timecounter "TSC"  frequency 82086508 Hz
May 10 20:13:09 squid /kernel: Timecounter "TSC"  frequency 83890627 Hz
May 10 22:50:53 squid /kernel: Timecounter "TSC"  frequency 87498832 Hz
May 10 22:56:12 squid /kernel.GENERIC: Timecounter "TSC"  frequency 79380441 Hz
May 10 23:01:42 squid /kernel: Timecounter "TSC"  frequency 86596730 Hz
May 10 23:03:58 squid /kernel: Timecounter "TSC"  frequency 90205040 Hz
May 11 19:40:41 squid /kernel: Timecounter "TSC"  frequency 82988540 Hz
May 11 19:43:37 squid /kernel: Timecounter "TSC"  frequency 84792851 Hz
May 11 19:46:05 squid /kernel: Timecounter "TSC"  frequency 90204971 Hz
May 11 12:36:59 squid /kernel: Timecounter "TSC"  frequency 87498777 Hz
May 11 16:18:42 squid /kernel: Timecounter "TSC"  frequency 86596851 Hz
May 12 15:54:47 squid /kernel: Timecounter "TSC"  frequency 87498803 Hz

This machine ran 3.0-RELEASE previously without any such problems.

This machine has a custom kernel without APM built in, and I believe APM
is disabled in the BIOS (not 100% sure, but this is a server.

I've also tried setting kern.timecounter.method=1 with no effect.
>How-To-Repeat:
. Find a PC.
. Boot 3.1 or later on it a few times.
. Watch the TSC go nuts.
>Fix:


>Release-Note:
>Audit-Trail:
>Unformatted:


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message