linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: Praedor Atrebates <praedor@yahoo.com>
Cc: lkml <linux-kernel@vger.kernel.org>
Subject: Re: System clock speed too high - 2.6.3 kernel
Date: Fri, 26 Mar 2004 15:09:17 -0800	[thread overview]
Message-ID: <1080342556.5408.322.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <200403261654.57525.praedor@yahoo.com>

On Fri, 2004-03-26 at 13:54, Praedor Atrebates wrote:
> On Friday 26 March 2004 04:22 pm, john stultz held forth thus:
> > On Fri, 2004-03-26 at 11:30, Praedor Atrebates wrote:
> > > In doing a web search on system clock speeds being too high, I found
> > > entries describing exactly what I am experiencing in the linux-kernel
> > > list archives, but have not yet found a resolution.
> [...]
> > > Does anyone have any enlightenment, or a fix, to offer?  The exact same
> > > software setup on a desktop system, Athlon XP2700+, has no such problems.
> >
> > Could you please send me dmesg output for this system?
> >
> > Does booting w/ "clock=pit" help?
> 
> Thank you, this did fix the problem.  Now I have to set the type-matic setting 
> up because it is so sluggish.  
> 
> What is clock=pit doing?  What is behind this accelerated clock?

This is just manually overriding the automatic time source selection.
You're using the PIT (programmable interval timer) over what was being
automatically selected (according the to the dmesg you sent me, the
pmtmr or ACPI PM timer) by your kernel config. 

As clock=pit seemed to solve the problem, it looks like its a ACPI PM
issue. 

thanks
-john


  reply	other threads:[~2004-03-26 23:09 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-26 19:30 System clock speed too high - 2.6.3 kernel Praedor Atrebates
2004-03-26 21:22 ` john stultz
2004-03-26 21:54   ` Praedor Atrebates
2004-03-26 23:09     ` john stultz [this message]
     [not found]   ` <200403261800.32717.praedor@yahoo.com>
2004-03-26 21:57     ` john stultz
2004-03-26 22:05       ` Praedor Atrebates
2004-03-26 22:18       ` Praedor Atrebates
2004-03-30 15:25     ` john stultz
2004-04-06 21:46       ` Dominik Brodowski
2004-03-26 21:46 ` George Anzinger
2004-03-26 21:57   ` Praedor Atrebates
2004-03-27 16:09     ` George Anzinger
     [not found] <1E4zj-77w-69@gated-at.bofh.it>
2004-05-25  9:22 ` Joris van Rantwijk
2004-05-25 20:53   ` john stultz
2004-05-25 20:58   ` john stultz
2004-05-26 22:43     ` Joris van Rantwijk
2004-05-26 23:08       ` john stultz
2004-05-27 13:32       ` Bill Davidsen

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=1080342556.5408.322.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=praedor@yahoo.com \
    /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;
as well as URLs for NNTP newsgroup(s).