From: Jim Crilly <noth@noth.is.eleet.ca>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: mlock + OOM = infinite loop
Date: Sun, 24 Feb 2002 23:37:01 -0500 [thread overview]
Message-ID: <3C79BF6D.8000206@noth.is.eleet.ca> (raw)
In-Reply-To: <3C797F82.4000602@candelatech.com>
I have a dual Athlon 1.2Ghz box with 1.2G of memory, I decided to run 2
copies of memtest to test the memory with each testing 629M (the
existance of memtest86 slipped my mind). With the 2.4.17 and 2.4.18-rc2
kernels (Andre's IDE amd kdb patches applied) the kernel loops trying to
free memory so the second mlock can succeed which never happens, I let
it run for about 2 days while I was away and it never became responsive,
minus kdb.
But with Rik's rmap12a patch it successfully starts the OOM and kills
one of the memtest processes, the only strange thing is it kills the
first instance letting the second succeed, I would think it would be
nicer to just fail in the second mlock and let the first continue.
Also all the kernels were compiled with SMP support, if that makes a
difference.
Jim
prev parent reply other threads:[~2002-02-25 4:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-25 0:04 lockup on dual athlon system Ben Greear
2002-02-25 4:37 ` Jim Crilly [this message]
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=3C79BF6D.8000206@noth.is.eleet.ca \
--to=noth@noth.is.eleet.ca \
--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