Re: TSC && HPET calibration
On Tue, 15 Jan 2008, Andrew Morton wrote: > On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko" <[EMAIL PROTECTED]> > wrote: > > > 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 > > DELL1) > > Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 > > 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 0xfed0, 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? That's not a kernel version problem. The TSCs on the CPUs are not synchronized, which means we can observe time going backwards when we read TSC on one and then on another CPU. TSC is switched off due to this. This is also unrelated to HPET. If there would be no HPET available we would use some other clocksource instead. On this box we use HPET because it's the best clocksource we have in the system. Thanks, tglx -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TSC HPET calibration
On Tue, 15 Jan 2008, Andrew Morton wrote: On Thu, 10 Jan 2008 14:36:12 +0200 Denys Fedoryshchenko [EMAIL PROTECTED] wrote: 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 DELL1) Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 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 0xfed0, 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? That's not a kernel version problem. The TSCs on the CPUs are not synchronized, which means we can observe time going backwards when we read TSC on one and then on another CPU. TSC is switched off due to this. This is also unrelated to HPET. If there would be no HPET available we would use some other clocksource instead. On this box we use HPET because it's the best clocksource we have in the system. Thanks, tglx -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TSC && HPET calibration
Latest, 2.6.24-rc7, and 2.6.23 is the same. If more information required, tell me. It is btw not latest (not based on Core2) Xeon. On Tue, 15 Jan 2008 02:17:20 -0800, Andrew Morton wrote > On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko" > <[EMAIL PROTECTED]> wrote: > > > 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 > > DELL1) > > Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 > > 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 0xfed0, 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? -- Denys Fedoryshchenko Technical Manager Virtual ISP S.A.L. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TSC && HPET calibration
On Thu, 10 Jan 2008 14:36:12 +0200 "Denys Fedoryshchenko" <[EMAIL PROTECTED]> wrote: > 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 > DELL1) > Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 > 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 0xfed0, 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? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TSC HPET calibration
On Thu, 10 Jan 2008 14:36:12 +0200 Denys Fedoryshchenko [EMAIL PROTECTED] wrote: 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 DELL1) Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 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 0xfed0, 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? -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Re: TSC HPET calibration
Latest, 2.6.24-rc7, and 2.6.23 is the same. If more information required, tell me. It is btw not latest (not based on Core2) Xeon. On Tue, 15 Jan 2008 02:17:20 -0800, Andrew Morton wrote On Thu, 10 Jan 2008 14:36:12 +0200 Denys Fedoryshchenko [EMAIL PROTECTED] wrote: 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 DELL1) Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 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 0xfed0, 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? -- Denys Fedoryshchenko Technical Manager Virtual ISP S.A.L. -- To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
TSC && HPET calibration
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 DELL1) Jan 10 13:41:51 visp-1 ACPI: HPET id: 0x8086a201 base: 0xfed0 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 0xfed0, 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. Sep 19 18:58:48 visp-1 Measured 1068 cycles TSC warp between CPUs, turning off TSC clock. Sep 19 19:16:23 visp-1 Measured 1068 cycles TSC warp between CPUs, turning off TSC clock. Sep 22 03:03:21 visp-1 Measured 912 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 12:06:21 visp-1 Measured 1176 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 12:35:16 visp-1 Measured 984 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 12:53:37 visp-1 Measured 1212 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:12:09 visp-1 Measured 1248 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:13:45 visp-1 Measured 1116 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:15:21 visp-1 Measured 1092 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:16:56 visp-1 Measured 1092 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:18:32 visp-1 Measured 984 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:20:07 visp-1 Measured 1020 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:21:43 visp-1 Measured 1116 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:23:18 visp-1 Measured 1008 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:24:54 visp-1 Measured 1032 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:26:29 visp-1 Measured 996 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:28:05 visp-1 Measured 1236 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:29:40 visp-1 Measured 1332 cycles TSC warp between CPUs, turning off TSC clock. Oct 1 13:34:24 visp-1 Measured 1152 cycles TSC warp between CPUs, turning off TSC clock. Oct 10 02:02:25 visp-1 Measured 1056 cycles TSC warp between CPUs, turning off TSC clock. Oct 10 16:07:34 visp-1 Measured 972 cycles TSC warp between CPUs, turning off TSC clock. Oct 10 16:22:40 visp-1 Measured 1140 cycles TSC warp between CPUs, turning off TSC clock. Oct 10 16:40:09 visp-1 Measured 996 cycles TSC warp between CPUs, turning off TSC clock. Oct 26 16:28:40 visp-1 Measured 1152 cycles TSC warp between CPUs, turning off TSC clock. Oct 26 17:14:13 visp-1 Measured 972 cycles TSC warp between CPUs, turning off TSC clock. Oct 26 17:24:57 visp-1 Measured 900 cycles TSC warp between CPUs, turning off TSC clock. Oct 26 19:00:51 visp-1 Measured 1020 cycles TSC warp between CPUs, turning off TSC clock. Oct 26 22:15:21 visp-1 Measured 1032 cycles TSC warp between CPUs, turning off TSC clock. Oct 26 22:29:35 visp-1 Measured 768 cycles TSC warp between CPUs, turning off TSC clock. Oct 27 10:41:49 visp-1 Measured 1032 cycles TSC warp between CPUs, turning off TSC clock. Oct 27 11:37:30 visp-1 Measured 852 cycles TSC warp between CPUs, turning off TSC clock. Oct 27 11:58:26 visp-1 Measured 1092 cycles TSC warp between CPUs, turning off TSC clock. Oct 27 13:36:39 visp-1 Measured 1044 cycles TSC warp between CPUs, turning off TSC clock. Oct 28 00:34:37 visp-1 Measured 792 cycles TSC warp between CPUs, turning off TSC clock. Nov 18 22:31:00 visp-1 Measured 936 cycles TSC warp between CPUs, turning off TSC clock. Jan 10 13:41:51 visp-1 Measured 1020 cycles TSC warp between CPUs, turning off TSC clock. cpuinfo (it is Dual Xeon with HT PowerEdge) visp-1 log # cat /proc/cpuinfo processor : 0 vendor_id : GenuineIntel cpu family : 15 model : 6 model name : Intel(R) Xeon(TM) CPU 3.20GHz stepping: 4 cpu MHz : 3192.070 cache size : 2048 KB physical id : 0 siblings: 4 core id : 0 cpu cores : 2 fdiv_bug: no hlt_bug : no f00f_bug: no coma_bug: no fpu : yes fpu_exception : yes cpuid level : 6 wp : yes flags : fpu vme de pse tsc msr pae mce cx8 apic
TSC && HPET calibration
I'm seeing the same error as reported by Sami Farin earlier today [1], but from my logs I can see that the issue is intermittent (2/3 failures). The logs indicate that the issue was introduced with 2.6.22 as TSC sync was correct for all boots with 2.6.21-6. My system is also Pentium D: Intel(R) Pentium(R) D CPU 3.20GHz Cheers, Frans Pop [1] http://lkml.org/lkml/2007/9/16/34 Jul 12 10:54:37 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 12 10:54:37 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 13 15:24:10 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 13 15:24:10 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 14 14:22:11 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 14 14:22:11 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 14 16:42:12 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 14 16:42:12 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 14 19:32:17 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 14 19:32:17 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 15 13:44:51 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 15 13:44:51 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 16 18:16:52 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 16 18:16:52 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 16 18:53:26 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 16 18:53:26 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Jul 17 21:05:13 faramir kernel: Linux version 2.6.22-1-amd64 (Debian 2.6.22-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Mon Jul 16 00:30:42 UTC 2007 Jul 17 21:05:13 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: Jul 17 21:05:13 faramir kernel: Measured 40 cycles TSC warp between CPUs, turning off TSC clock. Jul 17 21:05:13 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 18 07:30:55 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 18 07:30:55 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: Aug 18 07:30:55 faramir kernel: Measured 24 cycles TSC warp between CPUs, turning off TSC clock. Aug 18 07:30:55 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 19 06:59:50 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 19 06:59:50 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: Aug 19 06:59:50 faramir kernel: Measured 48 cycles TSC warp between CPUs, turning off TSC clock. Aug 19 06:59:50 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 20 07:47:51 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 20 07:47:51 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Aug 21 09:16:46 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 21 09:16:46 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: passed. Aug 22 10:27:29 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 22 10:27:29 faramir kernel: checking TSC synchronization [CPU#0 -> CPU#1]: Aug 22 10:27:29 faramir kernel: Measured 48 cycles TSC warp between CPUs, turning off TSC clock. Aug 22 10:27:29 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 23
TSC && HPET calibration
/var/log # grep -Ei "hpet|tsc" dmesg-2.6.19.7 dmesg.2.6.22.6-x86_64 dmesg-2.6.19.7:ACPI: HPET (v001 INTEL DQ965GF 0x15db MSFT 0x0113) @ 0x3e6f2000 dmesg-2.6.19.7:ACPI: HPET id: 0x8086a201 base: 0xfed0 dmesg-2.6.19.7:[ 34.337155] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0 dmesg-2.6.19.7:[ 34.337296] hpet0: 3 64-bit timers, 14318180 Hz [*] dmesg-2.6.19.7:[ 34.338350] Using HPET for base-timer dmesg-2.6.19.7:[ 34.594096] checking TSC synchronization across 2 CPUs: passed. dmesg-2.6.19.7:[0.215896] hpet_resources: 0xfed0 is busy dmesg-2.6.19.7:[7.794166] Time: tsc clocksource has been installed. dmesg.2.6.22.6-x86_64:ACPI: HPET 3E6F2000, 0038 (r1 INTEL DQ965GF 1741 MSFT 113) dmesg.2.6.22.6-x86_64:ACPI: HPET id: 0x8086a201 base: 0xfed0 dmesg.2.6.22.6-x86_64:[0.00] hpet clockevent registered dmesg.2.6.22.6-x86_64:[0.00] TSC calibrated against HPET dmesg.2.6.22.6-x86_64:[ 23.917469] checking TSC synchronization [CPU#0 -> CPU#1]: dmesg.2.6.22.6-x86_64:[ 23.937970] Measured 196 cycles TSC warp between CPUs, turning off TSC clock. dmesg.2.6.22.6-x86_64:[ 23.938030] Marking TSC unstable due to check_tsc_sync_source failed dmesg.2.6.22.6-x86_64:[ 23.968187] Time: hpet clocksource has been installed. dmesg.2.6.22.6-x86_64:[ 23.997754] hpet_acpi_add: no address or irqs in _CRS # grep MHz /proc/cpuinfo cpu MHz : 2797.203 cpu MHz : 2797.203 # calc 2797203000/196 ~14271443.87755102040816326531 [*] so, does TSC calibration against HPET screw up TSC synchronization? I have Intel(R) Pentium(R) D CPU 2.80GHz and DQ965GF motherboard, BIOS v.5953. -- Do what you love because life is too short for anything else. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
TSC HPET calibration
/var/log # grep -Ei hpet|tsc dmesg-2.6.19.7 dmesg.2.6.22.6-x86_64 dmesg-2.6.19.7:ACPI: HPET (v001 INTEL DQ965GF 0x15db MSFT 0x0113) @ 0x3e6f2000 dmesg-2.6.19.7:ACPI: HPET id: 0x8086a201 base: 0xfed0 dmesg-2.6.19.7:[ 34.337155] hpet0: at MMIO 0xfed0, IRQs 2, 8, 0 dmesg-2.6.19.7:[ 34.337296] hpet0: 3 64-bit timers, 14318180 Hz [*] dmesg-2.6.19.7:[ 34.338350] Using HPET for base-timer dmesg-2.6.19.7:[ 34.594096] checking TSC synchronization across 2 CPUs: passed. dmesg-2.6.19.7:[0.215896] hpet_resources: 0xfed0 is busy dmesg-2.6.19.7:[7.794166] Time: tsc clocksource has been installed. dmesg.2.6.22.6-x86_64:ACPI: HPET 3E6F2000, 0038 (r1 INTEL DQ965GF 1741 MSFT 113) dmesg.2.6.22.6-x86_64:ACPI: HPET id: 0x8086a201 base: 0xfed0 dmesg.2.6.22.6-x86_64:[0.00] hpet clockevent registered dmesg.2.6.22.6-x86_64:[0.00] TSC calibrated against HPET dmesg.2.6.22.6-x86_64:[ 23.917469] checking TSC synchronization [CPU#0 - CPU#1]: dmesg.2.6.22.6-x86_64:[ 23.937970] Measured 196 cycles TSC warp between CPUs, turning off TSC clock. dmesg.2.6.22.6-x86_64:[ 23.938030] Marking TSC unstable due to check_tsc_sync_source failed dmesg.2.6.22.6-x86_64:[ 23.968187] Time: hpet clocksource has been installed. dmesg.2.6.22.6-x86_64:[ 23.997754] hpet_acpi_add: no address or irqs in _CRS # grep MHz /proc/cpuinfo cpu MHz : 2797.203 cpu MHz : 2797.203 # calc 2797203000/196 ~14271443.87755102040816326531 [*] so, does TSC calibration against HPET screw up TSC synchronization? I have Intel(R) Pentium(R) D CPU 2.80GHz and DQ965GF motherboard, BIOS v.5953. -- Do what you love because life is too short for anything else. - To unsubscribe from this list: send the line unsubscribe linux-kernel in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
TSC HPET calibration
I'm seeing the same error as reported by Sami Farin earlier today [1], but from my logs I can see that the issue is intermittent (2/3 failures). The logs indicate that the issue was introduced with 2.6.22 as TSC sync was correct for all boots with 2.6.21-6. My system is also Pentium D: Intel(R) Pentium(R) D CPU 3.20GHz Cheers, Frans Pop [1] http://lkml.org/lkml/2007/9/16/34 Jul 12 10:54:37 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 12 10:54:37 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 13 15:24:10 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 13 15:24:10 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 14 14:22:11 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 14 14:22:11 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 14 16:42:12 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 14 16:42:12 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 14 19:32:17 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 14 19:32:17 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 15 13:44:51 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 15 13:44:51 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 16 18:16:52 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 16 18:16:52 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 16 18:53:26 faramir kernel: Linux version 2.6.21-2-amd64 (Debian 2.6.21-6) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Tue Jul 10 21:39:38 UTC 2007 Jul 16 18:53:26 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Jul 17 21:05:13 faramir kernel: Linux version 2.6.22-1-amd64 (Debian 2.6.22-1) ([EMAIL PROTECTED]) (gcc version 4.1.3 20070629 (prerelease) (Debian 4.1.2-13)) #1 SMP Mon Jul 16 00:30:42 UTC 2007 Jul 17 21:05:13 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: Jul 17 21:05:13 faramir kernel: Measured 40 cycles TSC warp between CPUs, turning off TSC clock. Jul 17 21:05:13 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 18 07:30:55 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 18 07:30:55 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: Aug 18 07:30:55 faramir kernel: Measured 24 cycles TSC warp between CPUs, turning off TSC clock. Aug 18 07:30:55 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 19 06:59:50 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 19 06:59:50 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: Aug 19 06:59:50 faramir kernel: Measured 48 cycles TSC warp between CPUs, turning off TSC clock. Aug 19 06:59:50 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 20 07:47:51 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 20 07:47:51 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Aug 21 09:16:46 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 21 09:16:46 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: passed. Aug 22 10:27:29 faramir kernel: Linux version 2.6.23-rc3 ([EMAIL PROTECTED]) (gcc version 4.1.3 20070718 (prerelease) (Debian 4.1.2-14)) #1 SMP Mon Aug 13 17:24:51 CEST 2007 Aug 22 10:27:29 faramir kernel: checking TSC synchronization [CPU#0 - CPU#1]: Aug 22 10:27:29 faramir kernel: Measured 48 cycles TSC warp between CPUs, turning off TSC clock. Aug 22 10:27:29 faramir kernel: Marking TSC unstable due to check_tsc_sync_source failed Aug 23 09:52:29 faramir
