From: Robert Hancock <hancockr@shaw.ca>
To: Pedram M <pmessri@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Fwd: kswapd issues + kernel 2.4.21-32.0.1.ELsmp
Date: Sun, 01 Apr 2007 14:27:51 -0600 [thread overview]
Message-ID: <461015C7.60804@shaw.ca> (raw)
In-Reply-To: <fa.Fyq10Ks5ejO6P+77Y8svOle1kro@ifi.uio.no>
Pedram M wrote:
> Hi,
>
> I've seen this around, and have heard about it in forums and else-where,
> could somebody enlighten me with more information or with experiences
> they have had. Looks like kswapd begins to eat CPU dramatically till the
> box eventually locks up.
>
> Thanks,
> Pedram
Looks like an old RHEL3 kernel - first off try the latest updated kernel
which is 2.4.21-47.0.1.EL.
--
Robert Hancock Saskatoon, SK, Canada
To email, remove "nospam" from hancockr@nospamshaw.ca
Home Page: http://www.roberthancock.com/
next parent reply other threads:[~2007-04-01 20:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.vikcLJfO/FKczN77bSVCqEtBhL0@ifi.uio.no>
[not found] ` <fa.Fyq10Ks5ejO6P+77Y8svOle1kro@ifi.uio.no>
2007-04-01 20:27 ` Robert Hancock [this message]
[not found] <9c9aa5d00703310110s2a21f19l37544c3d46be53c9@mail.gmail.com>
2007-03-31 8:11 ` Fwd: kswapd issues + kernel 2.4.21-32.0.1.ELsmp Pedram M
2007-03-31 15:50 ` Rik van Riel
2007-04-01 10:21 ` Dan Aloni
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=461015C7.60804@shaw.ca \
--to=hancockr@shaw.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=pmessri@gmail.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