From: "Roger Heflin" <rheflin@atipa.com>
To: "'Lee Revell'" <rlrevell@joe-job.com>,
       "'linux-kernel'" <linux-kernel@vger.kernel.org>
Subject: RE: Dual core Athlons and unsynced TSCs
Date: Fri, 13 Jan 2006 09:10:36 -0600
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
Content-Transfer-Encoding: 7bit
Thread-Index: AcYXxZRC9OaNBs5sT0insUgU6cqR2wAjb+3w
In-Reply-To: <1137104260.2370.85.camel@mindpipe>
Message-ID: <EXCHG2003rmTIVvLVKi00000c7b@EXCHG2003.microtech-ks.com>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1074
Lines: 30

 
> -----Original Message-----
> From: linux-kernel-owner@vger.kernel.org 
> [mailto:linux-kernel-owner@vger.kernel.org] On Behalf Of Lee Revell
> Sent: Thursday, January 12, 2006 4:18 PM
> To: linux-kernel
> Subject: Dual core Athlons and unsynced TSCs
> 
> It's been known for quite some time that the TSCs are not 
> synced between cores on Athlon X2 machines and this screws up 
> the kernel's timekeeping, as it still uses the TSC as the 
> default time source on these machines.
> 
> This problem still seems to be present in the latest kernels. 
>  What is the plan to fix it?  Is the fix simply to make the 
> kernel use the ACPI PM timer by default on Athlon X2?


Do we know if this also affects dual-core opterons?

The symptoms are that the clocks run at 2x the speed, correct?

                               Roger

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/