public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fast Clock <fastclock@earthlink.net>
To: linux-kernel@vger.kernel.org
Subject: PROBLEM: Linux system clock is running 3x too fast
Date: Sun, 22 Aug 2004 23:05:57 -0500	[thread overview]
Message-ID: <1093233957.3094.49.camel@apc> (raw)

My Athlon 64 laptop (HP Pavilion zv5000z) dual-boots Linux and Windows
XP. The Windows system clock is running accurately but the Linux system
clock is running 3 times too fast.

The problem occurs in all of the Linux distributions and releases that
I've tried, including Suse 9.1, Fedora Core 1 & 2, kernel versions
2.4.x, 2.6.x (up to 2.6.8-1.521), 32-bit & 64-bit releases.

The Linux system clock problem is also intermittent. Approximately 1 of
10 (cold) boots could yield an accurately running Linux system clock...
I've tried kernel boot options "clock=tsc", "clock=pit", "clock=pmtmr"
and have seen about the same 1/10 (failed/passed) ratio for each of
them. I've also tried kernel boot options "acpi=on" & "acpi=off" but
they don't seem to have any affect on the problem.

The differences in dmesg outputs between "good" and "bad" boots are as
followed.

good:	time.c: Detected 797.952 MHz processor.
bad:	time.c: Detected 265.995 MHz processor.

good:	Calibrating delay loop... 1576.96 BogoMIPS
bad:	Calibrating delay loop... 516.09 BogoMIPS

good:	Detected 12.468 MHz APIC timer.
bad:	Detected 4.156 MHz APIC timer.

good:	intel8x0_measure_ac97_clock: measured 49383 usecs
	intel8x0: clocking to 47408
bad:	intel8x0_measure_ac97_clock: measured 48347 usecs
	intel8x0: measured clock 16547 rejected
	intel8x0: clocking to 48000

Full dmesg logs (goods and bads) are available upon request.


             reply	other threads:[~2004-08-23  4:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-23  4:05 Fast Clock [this message]
2004-08-23  7:06 ` PROBLEM: Linux system clock is running 3x too fast Nick Piggin
     [not found] ` <1093234996.5055.5.camel@titania.zlynx.org>
2004-08-23 13:52   ` Fast Clock

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=1093233957.3094.49.camel@apc \
    --to=fastclock@earthlink.net \
    --cc=linux-kernel@vger.kernel.org \
    /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