From: Fernando Lopez-Lezcano <nando@ccrma.Stanford.EDU>
To: linux-kernel@vger.kernel.org
Cc: cc@ccrma.Stanford.EDU, nando@ccrma.Stanford.EDU,
Thomas Gleixner <tglx@linutronix.de>,
Steven Rostedt <rostedt@goodmis.org>, Ingo Molnar <mingo@elte.hu>,
john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.14-rt22 (acpi_pm vs tsc vs BIOS)
Date: Fri, 09 Dec 2005 17:21:11 -0800 [thread overview]
Message-ID: <1134177671.4811.4.camel@cmn3.stanford.edu> (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.
>
> 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.
Aha! Yes but no. The BIOS makes a difference. The first BIOS that has
support for the X2 processors on this particular motherboard works fine
with regards to the acpi_pm clock source, subsequent ones make linux say
things like:
PM-Timer running at invalid rate: 2159% of normal - aborting.
and then tsc is selected as the clock source...
> 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
next prev parent reply other threads:[~2005-12-10 1:21 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 ` Fernando Lopez-Lezcano [this message]
2005-12-10 2:31 ` 2.6.14-rt22 (acpi_pm vs tsc vs BIOS) john stultz
2005-12-10 3:10 ` Fernando Pablo Lopez-Lezcano
2005-12-10 2:29 ` 2.6.14-rt22 john stultz
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=1134177671.4811.4.camel@cmn3.stanford.edu \
--to=nando@ccrma.stanford.edu \
--cc=cc@ccrma.Stanford.EDU \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--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.