From: timothy parkinson <t@timothyparkinson.com>
To: john stultz <johnstul@us.ibm.com>
Cc: hauan@cmu.edu, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 "clock preempt"?
Date: Thu, 22 Jan 2004 14:50:26 -0500 [thread overview]
Message-ID: <20040122195026.GA579@h00a0cca1a6cf.ne.client2.attbi.com> (raw)
In-Reply-To: <1074800554.21658.68.camel@cog.beaverton.ibm.com>
well, it does *say* the following:
..... host bus clock speed is 133.0266 MHz.
checking TSC synchronization across 2 CPUs: passed.
Starting migration thread for cpu 0
is there a good way to check IDE PIO?
timothy
On Thu, Jan 22, 2004 at 11:42:35AM -0800, john stultz wrote:
> On Thu, 2004-01-22 at 11:37, timothy parkinson wrote:
> > hi john,
> >
> > i think this sounds like the same issue that i've been seeing with 2.5/2.6
> > kernels for a while now. smp kernel on a dual PIII machine without preempt.
> >
> > after running for a while the "losing ticks" shows up in dmesg, and the system
> > loses a lot of time. load seems to make it worse, so that just might be the
> > trigger.
> >
> > i'll try that one-liner as well when i get a chance - you said that if the
> > system still loses time, that narrows it down to hardware, yes?
>
> Well, not necessarily hardware, but it narrows it down to something
> blocking interrupts for way too long. IDE PIO for example seems to be a
> likely culprit. Another possibility on SMP systems is your cpu TSCs not
> being in sync.
>
> thanks
> -john
>
>
>
next prev parent reply other threads:[~2004-01-22 19:51 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-20 20:36 Steinar Hauan
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 [this message]
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=20040122195026.GA579@h00a0cca1a6cf.ne.client2.attbi.com \
--to=t@timothyparkinson.com \
--cc=hauan@cmu.edu \
--cc=johnstul@us.ibm.com \
--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
Powered by JetHome