From: john stultz <johnstul@us.ibm.com>
To: Linda Walsh <lkml@tlinx.org>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: PM-Timer clock source is slow. Try something else: How slow? What other source(s)?
Date: Wed, 29 Nov 2006 17:32:09 -0800 [thread overview]
Message-ID: <1164850329.5426.33.camel@localhost.localdomain> (raw)
In-Reply-To: <456E2C2C.40303@tlinx.org>
On Wed, 2006-11-29 at 16:56 -0800, Linda Walsh wrote:
> I recently noticed this message in my bootup that I don't remember
> from before:
>
> PCI: Probing PCI hardware (bus 00)
> * Found PM-Timer Bug on the chipset. Due to workarounds for a bug,
> * this clock source is slow. Consider trying other clock sources
This basically means that your chipset has a bug which requires the ACPI
PM timer to be read three times in order to get a valid reading.
This will cause gettimeofday/clock_gettime to take longer to execute,
which is what is meant by "slow" (rather then the counter's frequency
being incorrect).
> How would this affect my clock? It says to try another
> clock source, what type of clock source would it be suggesting I
> use? Another chip already in the computer? It is an Intel 440BX
> chipset; on an Dell motherboard. Would that be likely to have
> another chip source that is compensating?
>
> I don't notice a significant clock slowdown, but I'm running NTP,
> so that could be masking the problem.
Unless you're running performance critical programs that utilize
gettimeofday/clock_gettime, you probably won't notice anything. Time
should still function properly. If you are having performance issues,
you can try using a different clocksource (the TSC is probably safe, but
not necessarily).
thanks
-john
next prev parent reply other threads:[~2006-11-30 1:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 0:56 Linda Walsh
2006-11-30 1:32 ` john stultz [this message]
2006-11-30 7:00 ` Srinivasa Ds
2006-11-30 19:39 ` Linda Walsh
2006-12-01 10:40 ` Dominik Brodowski
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=1164850329.5426.33.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@tlinx.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
Powered by JetHome