Subject: 2.6.14-rt22
From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: linux-kernel@vger.kernel.org, Thomas Gleixner <tglx@linutronix.de>,
       Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
       john stultz <johnstul@us.ibm.com>
Cc: nando@ccrma.Stanford.EDU
Content-Type: text/plain
Date: Fri, 09 Dec 2005 15:48:25 -0800
Message-Id: <1134172105.12624.27.camel@cmn3.stanford.edu>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1409
Lines: 40

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.

and after that the tsc is selected as the timing source.
  Time: tsc clocksource has been installed.

The strange thing is that this is the same hardware as on other
machines. I have to install this kernel on more machines, will report
then...

This is what's available after the boot:
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
jiffies tsc pit

So I selected by hand:
# cat /sys/devices/system/clocksource/clocksource0/current_clocksource
pit

On the machine that's not selecting tsc the options are:
# cat /sys/devices/system/clocksource/clocksource0/available_clocksource
acpi_pm jiffies tsc pi
(and acpi_pm is selected, of course).

I think TSC's should never be selected on this hardware and it is known
not to work. 

-- Fernando


-
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/