All of lore.kernel.org
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
Cc: linux-kernel@vger.kernel.org,
	Thomas Gleixner <tglx@linutronix.de>,
	Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>
Subject: Re: 2.6.14-rt22
Date: Fri, 09 Dec 2005 18:29:30 -0800	[thread overview]
Message-ID: <1134181771.4002.4.camel@leatherman> (raw)
In-Reply-To: <1134172105.12624.27.camel@cmn3.stanford.edu>

On Fri, 2005-12-09 at 15:48 -0800, Fernando Lopez-Lezcano wrote:
> Hi all, I'm running 2.6.14-rt22 and just noticed something strange. I
> have not installed it in all machines yet, but in some of them (same
> hardware as others that seems to work fine) the TSC was selected as the
> main clock for the kernel. Remember this is one of the Athlon X2
> machines in which the TCS's drift...
> 
> dmesg shows this:
>   PM-Timer running at invalid rate: 2172% of normal - aborting.

Hm. That's odd. Either your PM-Timer isn't running at the right
frequency, or something is going wrong in the calibration. I'm
suspecting its the second. If you add a "return 0;" to the top of
verify_pmtmr_rate() in drivers/clocksource/acpi_pm.c does the acpi_pm
timer keep proper time?

thanks
-john



  parent reply	other threads:[~2005-12-10  2:29 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 23:48 2.6.14-rt22 Fernando Lopez-Lezcano
2005-12-10  1:21 ` 2.6.14-rt22 (acpi_pm vs tsc vs BIOS) Fernando Lopez-Lezcano
2005-12-10  2:31   ` john stultz
2005-12-10  3:10     ` Fernando Pablo Lopez-Lezcano
2005-12-10  2:29 ` john stultz [this message]
2005-12-13 20:15   ` 2.6.14-rt22 john stultz
2005-12-14  3:02     ` 2.6.14-rt22 Fernando Lopez-Lezcano

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=1134181771.4002.4.camel@leatherman \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=nando@ccrma.Stanford.EDU \
    --cc=rostedt@goodmis.org \
    --cc=tglx@linutronix.de \
    /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.