Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1750889AbVLGD5e (ORCPT ); Tue, 6 Dec 2005 22:57:34 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750994AbVLGD5e (ORCPT ); Tue, 6 Dec 2005 22:57:34 -0500 Received: from mx1.redhat.com ([66.187.233.31]:40648 "EHLO mx1.redhat.com") by vger.kernel.org with ESMTP id S1750889AbVLGD5e (ORCPT ); Tue, 6 Dec 2005 22:57:34 -0500 Date: Tue, 6 Dec 2005 22:57:25 -0500 From: Dave Jones To: linux-kernel@vger.kernel.org Subject: odd tsc related msg at bootup. Message-ID: <20051207035725.GB16838@redhat.com> Mail-Followup-To: Dave Jones , linux-kernel@vger.kernel.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.2.1i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 634 Lines: 17 Whilst diagnosing an unrelated problem by looking through a users dmesg, I noticed this.. CPU#0 had 0 usecs TSC skew, fixed it up. CPU#1 had 0 usecs TSC skew, fixed it up. Which looks very strange. Taking a look at the code in arch/i386/kernel/smpboot.c:synchronize_tsc_bp() I'm puzzled at to how this happened, as we should only hit that printk with a skew of more than 2 usecs. Dave - 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/