On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko" <denys@visp.net.lb> wrote:

quoted text
> Hi
> 
> I have same issue, but it's never passed synchronization.
> 
> Jan 10 12:59:44 visp-1 Time: tsc clocksource has been installed.
> Jan 10 13:41:51 visp-1 ACPI: HPET 000F29CD, 0038 (r1 DELL   PE_SC3          1 
> DELL        1)
> Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed00000
> Jan 10 13:41:51 visp-1 hpet clockevent registered
> Jan 10 13:41:51 visp-1 checking TSC synchronization [CPU#0 -> CPU#1]: passed.
> Jan 10 13:41:51 visp-1 checking TSC synchronization [CPU#0 -> CPU#2]:
> Jan 10 13:41:51 visp-1 Measured 1020 cycles TSC warp between CPUs, turning 
> off TSC clock.
> Jan 10 13:41:51 visp-1 Marking TSC unstable due to: check_tsc_sync_source 
> failed.
> Jan 10 13:41:51 visp-1 hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
> Jan 10 13:41:51 visp-1 hpet0: 3 64-bit timers, 14318180 Hz
> Jan 10 13:41:51 visp-1 Time: hpet clocksource has been installed.
> 
> grep Measures
> Sep 19 14:31:28 visp-1 Measured 1044 cycles TSC warp between CPUs, turning 
> off TSC clock.
> Sep 19 18:22:46 visp-1 Measured 996 cycles TSC warp between CPUs, turning off 
> TSC clock.
> Sep 19 18:35:44 visp-1 Measured 1080 cycles TSC warp between CPUs, turning 
> off TSC clock.

Which kernel version?
--
unsubscribe notice
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/