public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tilman Schmidt <tilman@imap.cc>
To: Arnaldo Carvalho de Melo <acme@redhat.com>
Cc: "Renato S. Yamane" <renatoyamane@mandic.com.br>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: clocksource tsc unstable
Date: Mon, 09 Jul 2007 23:26:25 +0200	[thread overview]
Message-ID: <4692A801.6050203@imap.cc> (raw)
In-Reply-To: <46925970.8080602@redhat.com>

[-- Attachment #1: Type: text/plain, Size: 2818 bytes --]

Now that you mention it - I am seeing something similar with
kernel 2.6.22 on an Intel Pentium D 940 dual core processor
(arbitrary selection of dmesg lines that appeared relevant):

<5>[    0.000000] Linux version 2.6.22-testing (ts@xenon) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP PREEMPT Mon Jul 9 10:57:22 CEST 2007
<6>[   56.367608] hpet0: at MMIO 0xfed00000, IRQs 2, 8, 0
<6>[   56.367867] hpet0: 3 64-bit timers, 14318180 Hz
<4>[   56.428897] Calibrating delay using timer specific routine.. 6399.40 BogoMIPS (lpj=3199704)
<4>[   56.438058] CPU0: Intel(R) Pentium(R) D CPU 3.20GHz stepping 04
<4>[   56.509321] CPU1: Intel(R) Pentium(R) D CPU 3.20GHz stepping 04
<6>[   56.510299] Total of 2 processors activated (12793.06 BogoMIPS).
<4>[   56.510527] ENABLING IO-APIC IRQs
<6>[   56.510792] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
<6>[   56.622869] checking TSC synchronization [CPU#0 -> CPU#1]:
<4>[   56.642971] Measured 16 cycles TSC warp between CPUs, turning off TSC clock.
<4>[    0.152000] Marking TSC unstable due to: check_tsc_sync_source failed.
<6>[    0.153000] Brought up 2 CPUs
<4>[    0.241000] migration_cost=2000

2.6.22-rc6-mm1 has it too, though without the backward jump in
printk timestamps:

<5>[    0.000000] Linux version 2.6.22-rc6-mm1-testing (ts@xenon) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #10 SMP PREEMPT Thu Jul 5 23:41:32 CEST 2007
<6>[    0.160000] Total of 2 processors activated (12791.39 BogoMIPS).
<4>[    0.160000] ENABLING IO-APIC IRQs
<6>[    0.161000] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
<6>[    0.171000] checking TSC synchronization [CPU#0 -> CPU#1]:
<4>[    0.171005] Measured 96 cycles TSC warp between CPUs, turning off TSC clock.
<4>[    0.171005] Marking TSC unstable due to: check_tsc_sync_source failed.
<6>[    0.172000] Brought up 2 CPUs

2.6.21.6 is fine here, though:

<5>[    0.000000] Linux version 2.6.21.6-noinitrd (ts@xenon) (gcc version 4.1.2 20061115 (prerelease) (SUSE Linux)) #1 SMP PREEMPT Sat Jul 7 16:40:13 CEST 2007
<6>[   59.776179] Total of 2 processors activated (12794.21 BogoMIPS).
<4>[   59.776403] ENABLING IO-APIC IRQs
<6>[   59.776657] ..TIMER: vector=0x31 apic1=0 pin1=2 apic2=-1 pin2=-1
<6>[   59.923347] checking TSC synchronization [CPU#0 -> CPU#1]: passed.
<6>[   59.943479] Brought up 2 CPUs
<4>[   60.198497] migration_cost=496
<6>[   60.303586] Time: tsc clocksource has been installed.
<6>[   60.303678] Switched to high resolution mode on CPU 0
<6>[   60.303974] Switched to high resolution mode on CPU 1

HTH

-- 
Tilman Schmidt                          E-Mail: tilman@imap.cc
Bonn, Germany
Diese Nachricht besteht zu 100% aus wiederverwerteten Bits.
Ungeöffnet mindestens haltbar bis: (siehe Rückseite)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 253 bytes --]

  parent reply	other threads:[~2007-07-09 21:22 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-09 14:57 clocksource tsc unstable Renato S. Yamane
2007-07-09 15:51 ` Arnaldo Carvalho de Melo
2007-07-09 16:08   ` Arkadiusz Miskiewicz
2007-07-09 20:18   ` Renato S. Yamane
2007-07-09 20:54     ` Pawel Dziepak
2007-07-10  9:22       ` Jan Engelhardt
2007-07-09 21:26   ` Tilman Schmidt [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-28  6:35 Clocksource " Dave Young
2009-03-28  9:14 ` Andi Kleen
2009-03-30  6:39   ` Dave Young

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=4692A801.6050203@imap.cc \
    --to=tilman@imap.cc \
    --cc=acme@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=renatoyamane@mandic.com.br \
    /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