From: john stultz <johnstul@us.ibm.com>
To: Praedor Atrebates <praedor@yahoo.com>
Cc: lkml <linux-kernel@vger.kernel.org>,
Dominik Brodowski <linux@brodo.de>,
Len Brown <len.brown@intel.com>
Subject: Re: System clock speed too high - 2.6.3 kernel
Date: Fri, 26 Mar 2004 13:57:46 -0800 [thread overview]
Message-ID: <1080338266.5408.316.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <200403261800.32717.praedor@yahoo.com>
On Fri, 2004-03-26 at 15:00, Praedor Atrebates wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> 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.
> > >
> > > 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
> [...]
> > Could you please send me dmesg output for this system?
> >
> > Does booting w/ "clock=pit" help?
>
> Attached is the output of dmesg. As I scanned it I see that I still have APIC
> disabled in Bios. I'll try enabling it and, if that doesn't help, then I
> will try the "clock=pit" switch.
I noticed in the dmesg you sent me that you're using the ACPI PM time
source. There has just recently been a bug opened for a very similar
issue (see http://bugme.osdl.org/show_bug.cgi?id=2375 ).
First of all, scratch trying "clock=pit" and test booting w/
"clock=tsc". If that resolves the issue, disable ACPI PM timesource
support (under the ACPI menu) in your kerel and that should fix you for
the short term.
As for the long term, I'm curious if this is a BIOS/Hardware quirk on
some systems or if there is just something we missed.
Dominik/Len: Any clue on this?
thanks
-john
next prev parent reply other threads:[~2004-03-26 21:59 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-26 19:30 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 [this message]
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=1080338266.5408.316.camel@cog.beaverton.ibm.com \
--to=johnstul@us.ibm.com \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@brodo.de \
--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
all inboxes | Powered by JetHome®