mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: john stultz <johnstul@us.ibm.com>
To: timothy parkinson <t@timothyparkinson.com>
Cc: hauan@cmu.edu, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.1 "clock preempt"?
Date: Thu, 22 Jan 2004 11:42:35 -0800	[thread overview]
Message-ID: <1074800554.21658.68.camel@cog.beaverton.ibm.com> (raw)
In-Reply-To: <20040122193704.GA552@h00a0cca1a6cf.ne.client2.attbi.com>

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


  reply	other threads:[~2004-01-22 19:43 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 [this message]
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=1074800554.21658.68.camel@cog.beaverton.ibm.com \
    --to=johnstul@us.ibm.com \
    --cc=hauan@cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=t@timothyparkinson.com \
    /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®