linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Thunder from the hill <thunder@lightweight.ods.org>
Cc: erik@debill.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: kernel losing time
Date: Mon, 26 Aug 2002 09:30:50 +0200	[thread overview]
Message-ID: <20020826093050.A2524@ucw.cz> (raw)
In-Reply-To: <Pine.LNX.4.44.0208251601060.3234-100000@hawkeye.luckynet.adm>; from thunder@lightweight.ods.org on Sun, Aug 25, 2002 at 04:02:07PM -0600

On Sun, Aug 25, 2002 at 04:02:07PM -0600, Thunder from the hill wrote:
> Hi,
> 
> On Sun, 25 Aug 2002 erik@debill.org wrote:
> > Would this explain my computer losing 2-3 minutes of time while
> > ripping a cd?  Normally it's dead on (w/ ntpd running to guarantee
> > that) but while ripping or burning it loses so badly ntpd can't keep
> > up.
> 
> We call it 'heavy interrupt load'. The more errors can happen, the more 
> errors do happen. (And by the way, I've already seen VIA chipsets jump off 
> by hours.)

It's always the same amount - about four hours - there is an underflow to
negative values with unsigned ints.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-08-26  7:26 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-25 10:55 kernel losing time Volker Kuhlmann
2002-08-25 11:01 ` Thunder from the hill
2002-08-25 11:47   ` Volker Kuhlmann
2002-08-25 21:55   ` erik
2002-08-25 22:02     ` Thunder from the hill
2002-08-26  7:30       ` Vojtech Pavlik [this message]
2002-08-26  0:05     ` Alan Cox
2002-08-26  1:13       ` Volker Kuhlmann
2002-08-26 10:15         ` Alan Cox
2002-08-26 10:27           ` Richard Zidlicky
2002-08-28  1:32             ` Volker Kuhlmann
2002-08-28 16:24               ` george anzinger
2002-08-26  3:05       ` erik

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=20020826093050.A2524@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=erik@debill.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thunder@lightweight.ods.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;
as well as URLs for NNTP newsgroup(s).