From: "H. Peter Anvin" <hpa@zytor.com>
To: "\"Paul Rolland (ポール・ロラン)\"" <rol@witbe.net>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: constant_tsc and TSC unstable
Date: Thu, 29 Nov 2007 11:04:39 -0800 [thread overview]
Message-ID: <474F0D47.7020006@zytor.com> (raw)
In-Reply-To: <20071129171142.56c7890a@tux.DEF.witbe.net>
Paul Rolland (ポール・ロラン) wrote:
> Hello,
>
> I've a machine with a Core2Duo CPU. /proc/cpuinfo reports the flag
> constant_tsc, but at boot time, I have the log :
>
> ...
> Total of 2 processors activated (6919.15 BogoMIPS).
> ENABLING IO-APIC IRQs
> ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
> checking TSC synchronization [CPU#0 -> CPU#1]:
> Measured 3978592228 cycles TSC warp between CPUs, turning off TSC clock.
> Marking TSC unstable due to: check_tsc_sync_source failed.
> Brought up 2 CPUs
> ...
>
> This machine is running 2.6.23.1-21.fc7. I know I should report to Fedora,
> but I was wondering if this is a bug or a feature ;)
>
constant_tsc means the TSC doesn't change with CPU core frequency.
The problem you're having is that the TSCs of your two cores are
completely different, over a second apart. This is a bug, unrelated to
constant_tsc.
-hpa
next prev parent reply other threads:[~2007-11-29 19:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-29 16:11 constant_tsc and TSC unstable Paul Rolland
2007-11-29 19:04 ` H. Peter Anvin [this message]
2007-11-29 21:26 ` Michael Tokarev
2007-11-30 6:59 ` Paul Rolland
2007-11-30 7:04 ` H. Peter Anvin
2007-11-29 21:36 ` Patrick McHardy
2007-11-29 23:29 ` Pallipadi, Venkatesh
2007-11-30 6:52 ` Paul Rolland (ポール・ロラン)
2007-12-06 0:35 ` Pallipadi, Venkatesh
2007-11-30 0:30 ` Frans Pop
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=474F0D47.7020006@zytor.com \
--to=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rol@witbe.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox