From: Hendrik Visage <hvjunk@gmail.com>
To: Scott Robert Ladd <lkml@coyotegulch.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: False "lost ticks" on dual-Opteron system (=> timer twice as fast)
Date: Tue, 24 May 2005 01:04:46 +0200 [thread overview]
Message-ID: <d93f04c7050523160430f34d1d@mail.gmail.com> (raw)
In-Reply-To: <4291C38D.1040705@coyotegulch.com>
On 5/23/05, Scott Robert Ladd <lkml@coyotegulch.com> wrote:
>
> Perhaps a comparison of my .config to yours might identify the source of
> your problem.
I think I've isolated the problem child: MSI's Dynamic Overclocking features...
The MSI "Core Cell" chipset will modify the CPU frequency within
certain parameters as the CPU needs more oomph (like a kernel
recompile :^P ), but will drop it once it heats up or things become
"unstable" or the CPU is getting idle again.
What I still need to ascertain, is whether the MSI K8N Neo Platinum
(nForce2 250) *do* have a HPET implementation or not, as my timer.c
only reports a PIT timer :(
--
Hendrik Visage
next prev parent reply other threads:[~2005-05-23 23:11 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
[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 [this message]
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=d93f04c7050523160430f34d1d@mail.gmail.com \
--to=hvjunk@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@coyotegulch.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.