public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jakob Oestergaard <jakob@unthought.net>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Jeff Dike <jdike@karaya.com>, Andrew Morton <akpm@digeo.com>,
	linux-kernel@vger.kernel.org
Subject: Re: 2.4.20-rc1 - hang with processes stuck in D
Date: Sat, 9 Nov 2002 23:39:21 +0100	[thread overview]
Message-ID: <20021109223921.GE10902@unthought.net> (raw)
In-Reply-To: <shslm437vi9.fsf@charged.uio.no>

On Fri, Nov 08, 2002 at 07:43:10PM +0100, Trond Myklebust wrote:
> >>>>> " " == Jakob Oestergaard <jakob@unthought.net> writes:
...
>      > Everything using disk, both on NFS clients and locally running
>      > processes, just pause. Five seconds after everything is like it
>      > never happened.
> 
> If you are using HIGHMEM, then the stock 2.4.20-rc1 has a known issue
> with an unbalanced kmap. Marcelo has already applied the following
> patch in the latest bitkeeper update.

No highmem.  The box has 512 MB RAM.

I get some
eth1: TX underrun, threshold adjusted.
eth0: TX underrun, threshold adjusted.
messages in the syslog - probably around 100 messages or so, but they
stop appearing after a day of uptime or so.  This is two bonded Intel
eepro100 cards, using the "Becker" driver (not the Intel one which I saw
was included).  Those messages do not seem to be correlated with the
pauses at all though.

That's the *only* anomaly except for the pauses, that I see on the box.

The machine has run 2.4.20-rc1 for 5 days now, with an average load
probably around 3 or 4  (load 2 caused by two long-running CPU hogs, the
rest comes from disk I/O, mostly because it's NFS exporting a 147G fs).

Stable so far, but the "hickups" are weird.

-- 
................................................................
:   jakob@unthought.net   : And I see the elder races,         :
:.........................: putrid forms of man                :
:   Jakob Østergaard      : See him rise and claim the earth,  :
:        OZ9ABN           : his downfall is at hand.           :
:.........................:............{Konkhra}...............:

  reply	other threads:[~2002-11-09 22:32 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06  0:25 2.4.20-rc1 - hang with processes stuck in D Jeff Dike
2002-11-06  0:37 ` Andrew Morton
2002-11-06  3:08   ` Jeff Dike
2002-11-08  4:17     ` Jakob Oestergaard
2002-11-08 18:43       ` Trond Myklebust
2002-11-09 22:39         ` Jakob Oestergaard [this message]
2002-11-08  9:01   ` Marcelo Tosatti
2002-11-10 21:22     ` Jeff Dike

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=20021109223921.GE10902@unthought.net \
    --to=jakob@unthought.net \
    --cc=akpm@digeo.com \
    --cc=jdike@karaya.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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