From: Henry <henry@borg.metroweb.co.za>
To: whitney@math.berkeley.edu
Cc: linux-kernel@vger.kernel.org
Subject: Re: OOPS (kswapd) in 2.4.5 and 2.4.6
Date: Thu, 5 Jul 2001 19:09:41 +0200 [thread overview]
Message-ID: <01070519204000.13482@borg> (raw)
In-Reply-To: <01070516412506.06182@borg> <200107051653.f65GrC400989@adsl-209-76-109-63.dsl.snfc21.pacbell.net>
In-Reply-To: <200107051653.f65GrC400989@adsl-209-76-109-63.dsl.snfc21.pacbell.net>
On Thu, 05 Jul 2001, Wayne Whitney wrote:
> In mailing-lists.linux-kernel, you wrote:
>
> > We've noticed the following kernel error since 2.4 (2.4.1-2.4.6).
> > It appears to be swap (kswapd thread specific?) related. The same
> > error is reported on several SMP machines after only a short period
> > (an hour or less).
>
> FYI, I see a similar problem under 2.4.5, also SMP, although only
> intermittently. Two oopses are below, from two different, although
> similarly configured, machines.
[snip]
Sounds very similar. Our servers are all identical (except for RAM).
What's unusual is that the machines we *expect* to fail sooner - don't
(not even an oops). Those are very busy cache servers (several of them
in a sibling cluster) which do a lot of swapping. The machines which
*do* fail (or oops without any further catastrophe) are typically
web/mail hosting servers (reasonably busy with about 25% swap being
used). Increasing swap did not help on 2.4.5. We're still waiting for
something to happen on 2.4.6 (ie, oops already appeared - waiting for
meltdown, which, hopefully, will not occur). We used to auto-reboot
every morning at 2am or something to keep things stable - which I
*hate* because I remember having a 2.0.35/6 workstation that had an
uptime of 6 months a couple of years ago. God, I loved that box.
cheers
Henry
next prev parent reply other threads:[~2001-07-05 17:21 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-05 14:03 OOPS (kswapd) in 2.4.5 and 2.4.6 Henry
2001-07-05 16:53 ` Wayne Whitney
2001-07-05 17:09 ` Henry [this message]
2001-07-06 5:59 ` Henry
2001-07-06 8:35 ` Andrew Morton
2001-07-06 10:31 ` Henry
2001-07-07 6:03 ` Henry
2001-07-07 8:07 ` Andrew Morton
2001-07-07 9:33 ` Henry
2001-07-07 9:54 ` Andrew Morton
2001-07-08 11:08 ` Henry
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=01070519204000.13482@borg \
--to=henry@borg.metroweb.co.za \
--cc=linux-kernel@vger.kernel.org \
--cc=whitney@math.berkeley.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.