From: Ian Chard <ian@chard.org>
To: linux-kernel@vger.kernel.org
Subject: TSC and real-time clock slippage with 2.6.2
Date: 04 Feb 2004 13:34:39 +0000 [thread overview]
Message-ID: <1075901679.5608.13.camel@tanagra> (raw)
Hi,
Ever since I upgraded from 2.4.20 to the 2.6 tree, I've had a problem
with real-time clock slippage and hard hangs on my Athlon XP 2500+
(1830MHz according to /proc/cpuinfo). I've kept an eye on the list and
have applied new patches as the problem seems to be known about, but as
the problem's still there with 2.6.2 I thought it was about time I
reared my ugly head.
At or shortly after boot time, I get the "Losing too many ticks!"
message (this seems to be related to how hard the system is working --
if it runs an fsck, the message appears immediately). Then, while the
system is running, the real-time clock will lose time: the more jobs use
the CPU, the more time I lose. Occasionally, the system will oops or
hard-hang altogether (which could be an unrelated driver issue; it is
pretty unusual).
I'm willing to test any patches you clever folk want to throw at me, or
alternatively if there's an easy solution I'll try anything.
Please cc: me on any replies, as my phone line is made of wet string and
would never cope with being subscribed!
Thanks for any help
- Ian
--
Ian Chard <ian@chard.org>
"Resting" Unix sysadmin and RHCE
near Linlithgow, central Scotland | sedimentation fault - beach dumped
next reply other threads:[~2004-02-04 13:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-04 13:34 Ian Chard [this message]
2004-02-04 18:23 ` TSC and real-time clock slippage with 2.6.2 john stultz
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=1075901679.5608.13.camel@tanagra \
--to=ian@chard.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.