public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Steven Walter <srwalter@yahoo.com>
To: Thomas Pfaff <tpfaff@gmx.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.2: System clock slows down under load
Date: Tue, 27 Mar 2001 15:36:01 -0600	[thread overview]
Message-ID: <20010327153600.A6238@hapablap.dyn.dhs.org> (raw)
In-Reply-To: <Pine.WNT.4.33.0103271315310.252-101000@algeria.intern.net>
In-Reply-To: <Pine.WNT.4.33.0103271315310.252-101000@algeria.intern.net>; from tpfaff@gmx.net on Tue, Mar 27, 2001 at 01:42:39PM +0200

On Tue, Mar 27, 2001 at 01:42:39PM +0200, Thomas Pfaff wrote:
> Hi all,
> 
> i decided to make a test for the 2.4 kernel on my old hardware (Gigabyte
> EISA/VLB with an AMD 486 DX4 133). The kernel boots fine but there is one
> strange thing: The system clock slows down under load, after a make
> dep in the linux src directory it is about 2 minutes behind. This appears
> both in 2.4.1 and in 2.4.2 (I have not tried 2.4.0 yet).
> 
> I have attached a gzipped dmesg.
> 
> Any ideas ?

I notice that you're using fbcon from your dmesg.  There was a
discussion about this a while back, and it was determined that fbcon
runs with interrupts disabled for unhealthily long period of time.  This
causes it to miss timer interrupts, and the system lock get behind.  See
if this slowdown occurs with vgacon.  If it does, its probably just a
cheap crystal on the motherboard.

-- 
-Steven
Freedom is the freedom to say that two plus two equals four.

  reply	other threads:[~2001-03-27 21:58 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-27 11:42 2.4.2: System clock slows down under load Thomas Pfaff
2001-03-27 21:36 ` Steven Walter [this message]
     [not found] <F0E13277A26BD311944600500454CCD029BEBA@antarctica.intern.net>
2001-04-02  6:46 ` Thomas Pfaff

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=20010327153600.A6238@hapablap.dyn.dhs.org \
    --to=srwalter@yahoo.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tpfaff@gmx.net \
    /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