From: Vincent Stemen <linuxkernel@AdvancedResearch.org>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: jq419@my-deja.com (Jacky Liu), linux-kernel@vger.kernel.org
Subject: Re: 2.4.4 kernel freeze for unknown reason
Date: Sun, 13 May 2001 01:17:37 -0500 [thread overview]
Message-ID: <01051301173700.02739@quark> (raw)
In-Reply-To: <E14yHw8-0001V8-00@the-village.bc.nu>
In-Reply-To: <E14yHw8-0001V8-00@the-village.bc.nu>
On Friday 11 May 2001 13:46, Alan Cox wrote:
> > I have been monitoring the memory usage constantly with the gnome
> > memory usage meter and noticed that as swap grows it is never freed
> > back up. I can kill off most of the large applications, such as
>
> The swap handling in 2.4 is somewhat hosed at the moment.
>
> > If I turn swap off all together or turn it off and back on
> > periodically to clear the swap before it gets full, I do not seem to
> > experience the lockups.
>
> That sounds right. I can give you a tiny patch that should fix the
> lockups and instead it will kill processes out of memory but thats
> obviously not the actual fix 8)
I am not sure if you got my reply to this Alan, but I would like to
have you send me the patch. Thanks.
Also, I got to thinking back and it dawned on me that there was
another significant kernel change when we started experiencing the
freezes from the vm problems. We changed the compiler from
gcc-2.7.2.3 to egcs-1.1.2 starting with kernel 2.4.0-test10 (That is
the version in which gcc-2.7.2.3 stopped being supported for the
kernel) and it seems like that was just about the same time frame that
we started experiencing the vm/swap problems. I would have to go back
and run on the test10 kernel for a while to confirm if it started with
it or 2.4.0.
I am assuming the source of the vm problem is still unknown or it
would have been fixed by now. Is it possible that it could be related
to the compiler change? If nobody has considered that, I just thought
I would bring the possibility to your attention.
- Vincent Stemen
next prev parent reply other threads:[~2001-05-13 6:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-10 3:57 2.4.4 kernel freeze for unknown reason Jacky Liu
2001-05-11 18:45 ` Vincent Stemen
2001-05-11 18:46 ` Alan Cox
2001-05-12 6:05 ` Mike Galbraith
2001-05-12 11:18 ` Alan Cox
2001-05-12 13:45 ` Mike Galbraith
2001-05-12 14:25 ` Alan Cox
2001-05-12 15:33 ` Mike Galbraith
2001-05-13 18:16 ` Christoph Rohland
2001-05-14 4:36 ` Mike Galbraith
2001-05-13 6:17 ` Vincent Stemen [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-05-11 2:26 Jacky Liu
2001-05-15 7:13 Jacky Liu
2001-05-16 5:25 ` Vincent Stemen
2001-05-29 3:59 Vasco Figueira
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=01051301173700.02739@quark \
--to=linuxkernel@advancedresearch.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jq419@my-deja.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