[lkml]   [2007]   [Nov]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: constant_tsc and TSC unstable
    H. Peter Anvin wrote:
    > 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).
    >> ..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 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.

    On my core2duo I noticed that the TSC of the second core doesn't
    start counting until the CPU is activated. Since they're not
    synchronized manually anymore this makes the TSC check fail.

    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2007-11-29 22:39    [W:0.022 / U:5.364 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site