linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Anzinger <george@mvista.com>
To: Praedor Atrebates <praedor@yahoo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: System clock speed too high - 2.6.3 kernel
Date: Fri, 26 Mar 2004 13:46:31 -0800	[thread overview]
Message-ID: <4064A4B7.5030103@mvista.com> (raw)
In-Reply-To: <200403261430.18629.praedor@yahoo.com>

Praedor Atrebates wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 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.
> 
> I have Mandrake 10.0, kernel-2.6.3-7mdk installed, on an IBM Thinkpad 1412 
> laptop, celeron 366, 512MB RAM.  I am finding that my system clock is ticking 
> away at a rate of about 3:1 vs reality, ie, I count ~3 seconds on the system 
> clock for every 1 real second.  I am running ntpd but this is unable to keep 
> up with the rate of system clock passage.  
> 
> I had to slow my keyboard repeat rate _way_ down in order to be able to type 
> at all as well.   The system is limited, in that I have no way to alter the 
> actual system clock (in bios at any rate).  The CPU is properly identified as 
> a celeron 366.  
> 
> 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.

Try this in the boot command line "clock=pmtmr".  If that fails, then try 
"clock=pit".

-g
> 
> praedor
> - -- 
> "George W. Bush is a deserter, an election thief, a drunk driver, a WMD 
> liar and a functional illiterate. And he poops his pants." 
> - --Barbara Bush, his mother
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.4 (GNU/Linux)
> 
> iD8DBQFAZITKSTapoRk9vv8RAkxyAJ45KBKN7ngdNX6qTOwSBIxEs7rfcACgl8e0
> 0lKo+bfaSHPcNpA+36WGCrE=
> =ZdjK
> -----END PGP SIGNATURE-----
> -
> 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/
> 

-- 
George Anzinger   george@mvista.com
High-res-timers:  http://sourceforge.net/projects/high-res-timers/
Preemption patch: http://www.kernel.org/pub/linux/kernel/people/rml


  parent reply	other threads:[~2004-03-26 21:46 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
     [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 [this message]
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=4064A4B7.5030103@mvista.com \
    --to=george@mvista.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).