Subject: Re: 2.6.14-rt22
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>
In-Reply-To: <1134172105.12624.27.camel@cmn3.stanford.edu>
References: <1134172105.12624.27.camel@cmn3.stanford.edu>
Content-Type: text/plain
Date: Fri, 09 Dec 2005 18:29:30 -0800
Message-Id: <1134181771.4002.4.camel@leatherman>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1025
Lines: 25

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


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/