public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Scott Robert Ladd <lkml@coyotegulch.com>
To: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: False "lost ticks" on dual-Opteron system (=> timer twice as fast)
Date: Sat, 21 May 2005 16:54:06 -0400	[thread overview]
Message-ID: <428F9FEE.5000003@coyotegulch.com> (raw)
In-Reply-To: <d93f04c705052112426ee35154@mail.gmail.com>

Bernd Paysan <bernd.paysan@gmx.de> wrote:
>>I've recently set up a dual Opteron RAID server (AMD-8000-based Tyan
>>Thunder K8S Pro SCSI board, 2 246 Opterons, stepping 10). Kernel is a
>>modified 2.6.11.4-20a from SuSE 9.3 (SMP version, sure). The Opterons
>>are capable of changing the CPU frequency (between 1GHz and 2GHz).
>>
>>What I can't believe is that I'm the only one who has this problem.

Hendrik Visage wrote:
> I'll be delving deeper into this thread soon, but I'm seeing similar
> strangeness
> on a Athlon64 (rated:3G+ real:2009MHz clock), 2.6.11-r8 (gentoo), MSI
> K8N Neo Platinum.
> 
> ntp syncs time, then I start a couple of compiles, and I see ntp
> losing track of time, big jitter etc. (and the one time source is in
> on the local LAN syncing to the same remote servers). openntp I
> noticed it also.
> 
> What I have noticed in my dmesg output is that I see "lost timer ticks
> CPU Frequency change?" messages very early in the boot up.
> 
> I've seen this for about a week or three, and somehow I believe it
> wasn't a problem before 2.6.11.

I *don't* have any timer problems running 2.6.11-r8 (gentoo) on a dual
Opteron 250 system using a Tyan K8W 2885. Perhaps the problem is that
the two of you are running SCSI main drives, and I'm not?

..Scott


  reply	other threads:[~2005-05-21 20:55 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-05-08 12:45 False "lost ticks" on dual-Opteron system (=> timer twice as fast) Bernd Paysan
2005-05-08 13:40 ` [suse-amd64] " Andi Kleen
2005-05-08 16:22   ` Bernd Paysan
2005-05-09 10:53   ` Bernd Paysan
2005-05-09 13:17     ` Bernd Paysan
2005-05-10 10:53       ` Ed Tomlinson
2005-05-10 13:32         ` Andi Kleen
2005-05-10 11:12       ` Andi Kleen
2005-05-10 11:36         ` Bernd Paysan
2005-05-10 11:54         ` Bernd Paysan
2005-05-10 13:07           ` Andi Kleen
2005-05-10 13:15             ` Bernd Paysan
2005-05-10 13:21               ` Andi Kleen
2005-05-10 13:39                 ` Arjan van de Ven
2005-05-21 19:42 ` Hendrik Visage
2005-05-21 20:54   ` Scott Robert Ladd [this message]
     [not found]   ` <428F9FA6.1000800@coyotegulch.com>
     [not found]     ` <d93f04c70505211500216d8614@mail.gmail.com>
2005-05-23 11:50       ` Scott Robert Ladd
2005-05-23 23:04         ` Hendrik Visage
2005-05-25 17:06           ` Andi Kleen

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=428F9FEE.5000003@coyotegulch.com \
    --to=lkml@coyotegulch.com \
    --cc=linux-kernel@vger.kernel.org \
    /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