linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Berend De Schouwer <bds@jhb.ucs.co.za>
To: linux-mm <linux-mm@kvack.org>
Subject: oom-kill looping
Date: 28 Jul 2001 14:22:41 +0200	[thread overview]
Message-ID: <996322962.1350.43.camel@bds.ucs.co.za> (raw)

Hi,

I've got a machine that has been crashing more-or-less weekly due to
running out of memory.  I've noticed an oddity in oom-kill.  It loops
'Out of Memory: Killed process 12345 (abc).'  The same PID is listed
continuously.  This is with kernel 2.4.x.  With the 2.2 series it just
hung.

Is it a good idea to add checks oom_kill.c in badness() like:
  if is_not_runnable(p)
    return 0;
  if has_pending_term_or_kill(p)
    return 0;

and if so, would (p->state != 0) and signal_pending(p) be the way to do
it?  How would you check for just the SIGKILL or SIGTERM signal?

It takes about a week to trigger this OOM, so trials are slow.

--
Berend De Schouwer

--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org.  For more info on Linux MM,
see: http://www.linux-mm.org/

                 reply	other threads:[~2001-07-28 12:22 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=996322962.1350.43.camel@bds.ucs.co.za \
    --to=bds@jhb.ucs.co.za \
    --cc=linux-mm@kvack.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