From mboxrd@z Thu Jan  1 00:00:00 1970
From: John Sigler <linux.kernel@free.fr>
Subject: System clock frequency offset changes drastically across reboots
Date: Mon, 03 Sep 2007 12:21:37 +0200
Message-ID: <46DBE031.1090808@free.fr>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Cc: johnstul@us.ibm.com, tglx@linutronix.de
To: linux-kernel@vger.kernel.org,
	linux-rt-users <linux-rt-users@vger.kernel.org>
Return-path: <linux-rt-users-owner@vger.kernel.org>
Received: from smtp4-g19.free.fr ([212.27.42.30]:44458 "EHLO smtp4-g19.free.fr"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1752330AbXICKWN (ORCPT <rfc822;linux-rt-users@vger.kernel.org>);
	Mon, 3 Sep 2007 06:22:13 -0400
Sender: linux-rt-users-owner@vger.kernel.org
List-Id: linux-rt-users.vger.kernel.org

[ Re-sending... Please feel free to comment, even if you don't have
"The Solution". I'd just like to get some feedback. ]

Hello everyone,

I'm using 2.6.20.7-rt8 on a P3.

I've noticed that the frequency offset of my system clock (computed
either by ntpd, or by hand) changes drastically across reboots.

By drastically, I mean +/- 60 ppm every time I reboot.

Apparently this is caused by some imprecision in the frequency
estimation done in calculate_cpu_khz() (arch/i386/kernel/tsc.c)

My brutally crude work-around was to skip the computation altogether and
hard-code the "correct" value for cpu_khz.

http://linux.kernel.free.fr/cpu_khz.adlink

Has this issue been investigated more thoroughly by other users?

Regards.