From: Marcin Kasperski <Marcin.Kasperski@softax.com.pl>
To: linux-kernel@vger.kernel.org
Cc: Marcin.Kasperski@softax.com.pl
Subject: heavy kupdated still observed in 2.4.18
Date: 18 Dec 2002 15:37:22 +0100 [thread overview]
Message-ID: <1040222242.7694.17.camel@cauchy> (raw)
{ I am not subscribed to linux-kernel, so be so kind to cc the replies
to me - although I will review the archives. I send this mail to report
that some problem still exists although it is considered to be solved }
I repeatably observe the effect of 'heavy kupdated' (kupdated taking
almost 100% CPU, computer not reacting - for a few seconds, happening
from time to time). In the archives I found that this problem is
considered to be removed in 2.4.15per7
(http://hypermail.idiosynkrasia.net/linux-kernel/archived/2001/week48/0147.html). I use 2.4.18 and I still observe it.
Some (probably important) details:
- the effect happens in the particular case: when I perform large
copying over the local network (in fact it was sth like
scp -r remote:/some/directory/tree ./
)
- I have a lot of RAM and there is a lot of free memory when the problem
is being observed
- I do not use any swap
- I use LVM (applied from lvm_1.0.5 as distributed by Sistina) and the
drive to which the copying occurs belongs to LVM volume group.
reply other threads:[~2002-12-18 14:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1040222242.7694.17.camel@cauchy \
--to=marcin.kasperski@softax.com.pl \
--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