public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Shawn Willden <shawn@willden.org>
To: linux-kernel@vger.kernel.org
Subject: 2.6.8 Thinkpad T40, clock running too fast
Date: Tue, 2 Nov 2004 15:18:12 -0700	[thread overview]
Message-ID: <200411021518.17391.shawn@willden.org> (raw)

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm having a problem with the clock on my Thinkpad running too fast.  My clock 
is gaining about 4 seconds every five minutes of operation.  I'm actually not 
sure when this started because NTP has been fairly successful at keeping my 
clock under control, so I didn't really notice it until I spent some time 
operating disconnected... and then it became very obvious very quickly.

On October 15th, I "fixed" the problem by booting with "noapic" on the command 
line.  Or I thought I fixed it anyway.  I had to reboot yesterday for an 
unrelated issue (a "stuck" smb share that I couldn't figure out how to 
unmount) and the racing clock is back.  I've booted with "noapic", "nolapic", 
"noapic nolapic" and no options at all, and the clock doesn't keep the time 
with any of them.  I'm not sure if it's always too fast.  I seem to remember 
that last month it was running too slow.  I'll check with the various apic 
settings and see if it's consistent.

I'm not sure what information I need to provide, but you can find my kernel 
config at http://willden.org/~shawn/config-2.6.8.  It's built from the Debian 
2.6.8 tree, with a custom config.  The CPU is a 1.6GHz Pentium M in a 
"Centrino" chipset.

What should I be looking at to track this down?  I'm building a 2.6.9 kernel 
but I haven't found any reports of similar problems corrected by it, so I 
don't expect that to make a difference.

Thanks,

 Shawn.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBiAep6d8WxFy/CWcRAoXVAKCeEwysrrF/+lcFuRttAx5JDs8RYQCgjf1q
cdK/581EqaX+2oGXlkOLpoE=
=sNMu
-----END PGP SIGNATURE-----

             reply	other threads:[~2004-11-03  0:40 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-02 22:18 Shawn Willden [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-11-02 22:51 2.6.8 Thinkpad T40, clock running too fast Shawn Willden
2004-11-02 23:06 ` john stultz
2004-11-03  0:03   ` Shawn Willden
2004-11-03  0:27     ` john stultz
2004-11-03  0:58       ` Shawn Willden
2004-11-03  0:38   ` Shawn Willden
2004-11-03 12:29     ` Stefan Seyfried

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=200411021518.17391.shawn@willden.org \
    --to=shawn@willden.org \
    --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