public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Triffid Hunter <triffid_hunter@funkmunch.net>
To: "Jose Ángel De Bustos Pérez" <jadebustos@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: A problem with kswapd
Date: Mon, 04 Apr 2005 18:07:39 +1000	[thread overview]
Message-ID: <4250F5CB.4070605@funkmunch.net> (raw)
In-Reply-To: <59ab6ac105040400423fefd96a@mail.gmail.com>

try 2.4.30 which has just been released (unchanged from 2.4.30-rc4)

Jose Ángel De Bustos Pérez wrote:
> Hi,
> 
> I have a problem with kswapd and I didn't find anything in the
> archives of the list (I hope not having missed someone).
> 
> kswapd is using 100% of CPU in a suse sles8 with kernel 2.4.241. This
> machine has its FS under LVM and ResiserFS, except for /boot which is
> in ext2.
> 
> Any idea? Thanks in advance.

  reply	other threads:[~2005-04-04  8:07 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-04  7:42 A problem with kswapd Jose Ángel De Bustos Pérez
2005-04-04  8:07 ` Triffid Hunter [this message]
2005-04-04  8:51   ` Jose Ángel De Bustos Pérez
2005-04-07 22:28 ` Adrian Bunk

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=4250F5CB.4070605@funkmunch.net \
    --to=triffid_hunter@funkmunch.net \
    --cc=jadebustos@gmail.com \
    --cc=linux-kernel@vger.kernel.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