linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rik van Riel <riel@conectiva.com.br>
To: <tcm@nac.net>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: Possible freezing bug located after ac13
Date: Sat, 23 Jun 2001 23:54:06 -0300 (BRST)	[thread overview]
Message-ID: <Pine.LNX.4.33L.0106232353100.3161-100000@duckman.distro.conectiva> (raw)
In-Reply-To: <20010623222954.A9031@debian>

On Sat, 23 Jun 2001 tcm@nac.net wrote:

> I've recently been going slightly nuts with the fact ac15, 16, and 17
> all like deadlocking/slowing to a crawl for seconds/minutes on my K6-III
> with 64MB of ram and a swap space of 128MB...
>
> Recently I noticed something VERY odd, I'd been keeping an eye on
> gkrellm while I was doing stupid things to produce the problem (a du
> as root in X of / generally would always make it pop up) ... And swap
> was doing I/O at the time *JUST* before when I'd either deadlock or slow
> down to a crawl, and if it recovered, swap would do more I/O...
>
> So. I tried unmounting all swap, and suddenly everything worked fine,
> although I couldn't exactly do everythign I wanted of course.
>
> I regression tested this, ac 16,15 and even 14 do this. ac 13 does *not*
> - IMHO I think the dead swap patches introduced into 14 may be related
> to the problem.

1) the dead swap cache patch should alleviate the problem,
   if anything

2) does this happen with 2.4.6-pre5 too ?

regards,

Rik
--
Executive summary of a recent Microsoft press release:
   "we are concerned about the GNU General Public License (GPL)"


		http://www.surriel.com/
http://www.conectiva.com/	http://distro.conectiva.com/


  reply	other threads:[~2001-06-24  2:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-24  2:29 Possible freezing bug located after ac13 tcm
2001-06-24  2:54 ` Rik van Riel [this message]
2001-06-26 22:38 ` Swap error message I've seen in 2.4.5-ac17 tcm
2001-06-28  0:33 ` Freezing bug in all kernels greater than 2.4.5-ac13 *AND* 2.4.6-pre2 tcm
2001-06-27 23:11   ` Marcelo Tosatti
2001-06-27 23:25     ` Marcelo Tosatti
2001-07-01  5:08   ` tcm

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=Pine.LNX.4.33L.0106232353100.3161-100000@duckman.distro.conectiva \
    --to=riel@conectiva.com.br \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tcm@nac.net \
    /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;
as well as URLs for NNTP newsgroup(s).