From: Steinar Hauan <steinhau@andrew.cmu.edu>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: 2.6.1 "clock preempt"?
Date: Tue, 20 Jan 2004 15:36:08 -0500 [thread overview]
Message-ID: <1074630968.19174.49.camel@steinar.cheme.cmu.edu> (raw)
hello,
i've started to test the 2.6 series of kernels and observed a
strange thing: with moderate background load, the system clock
(i.e. time) seems to slow down to about 60% of normal speed
and the normally reliable ntp process (v4.2.0)
details: working interactively with a couple of background dummy
processes (*1), my system clock slowed down approx 90 mins over
a period of approx 4 hrs real time.
(*1) infinite loop: 1 rip, 1 encode -- both run at nice 10
the kernel logs show messages on the form:
localhost kernel: Losing too many ticks!
localhost kernel: TSC cannot be used as a timesource.
(Are you running with SpeedStep?)
localhost kernel: Falling back to a sane timesource.
localhost kernel: set_rtc_mmss: can't update from 5 to 58
without the background load, the system keeps perfect time.
==> any ideas of what could be going on would be appreciated.
hardware details
Intel P4 2.53gz on Supermicro P4SAA mobo (Intel 7205 chipset)
1gb memory; multiple drives; Promise Ultra/133 raid controller
software
kernel 2.6.1 w/APIC and PREEMPT options turned on.
Fedora Core 1 + selected development packages (verified on 2.4).
more info available on request.
regards,
--
Steinar Hauan, dept of ChemE -- hauan@cmu.edu
Carnegie Mellon University, Pittsburgh PA, USA
next reply other threads:[~2004-01-20 20:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:36 Steinar Hauan [this message]
2004-01-20 21:26 ` john stultz
2004-01-21 15:06 ` Steinar Hauan
2004-01-21 18:19 ` john stultz
2004-01-22 19:37 ` timothy parkinson
2004-01-22 19:42 ` john stultz
2004-01-22 19:50 ` timothy parkinson
2004-01-22 19:54 ` john stultz
2004-01-22 20:00 ` timothy parkinson
2004-01-22 21:21 ` john stultz
2004-01-23 19:02 ` timothy parkinson
2004-01-23 19:17 ` john stultz
2004-01-23 19:36 ` timothy parkinson
2004-01-23 20:06 ` john stultz
2004-01-23 20:38 ` timothy parkinson
2004-01-23 21:04 ` john stultz
2004-01-27 21:30 ` markus reichelt
2004-01-30 23:32 ` Bartlomiej Zolnierkiewicz
2004-01-31 0:24 ` timothy parkinson
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=1074630968.19174.49.camel@steinar.cheme.cmu.edu \
--to=steinhau@andrew.cmu.edu \
--cc=hauan@cmu.edu \
--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
all inboxes | Powered by JetHome®