public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Chris Fowler <cfowler@outpostsentinel.com>
To: linux-kernel@vger.kernel.org
Subject: Panic on OOM
Date: Tue, 14 Jun 2011 09:31:16 -0400	[thread overview]
Message-ID: <1308058276.2074.295.camel@compaq-desktop> (raw)

I'm running into a problem in 2.6.38 where the kernel is not doing what
I'm expecting it to do.  I'm guessing that some things have changed and
that is what it going on.

First,  The tune at boot:

        f.open("/proc/sys/vm/panic_on_oom", std::ios::out);
        f << "1";
        f.close();

        f.open("/proc/sys/kernel/panic", std::ios::out);
        f << "10";
        f.close();

I want the kernel to panic on out of memory.  I then want it to wait 10s
before doing a reboot.

This program will consume all memory and make the box unresponsive

#!/usr/bin/perl

my @mem = ()
while(1) {
  push @mem, "########################";
}

It does not take long to fill up 1G of space.  There is NO swap on this
device and never will be.  I did notice that after a long period of time
(I've not timed it) I finally do see a panic and I do see "rebooting in
10 seconds..." .  It does not reboot.


I'm guessing that there are some tweaks or new behavior I just need to
be aware of.

Thanks,
Chris



             reply	other threads:[~2011-06-14 13:57 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-14 13:31 Chris Fowler [this message]
2011-06-15  0:13 ` Panic on OOM David Rientjes
2011-06-15  2:04   ` Chris Fowler
2011-06-15  2:32     ` David Rientjes
2011-06-15  2:41       ` Chris Fowler
2011-06-15  2:51         ` David Rientjes
2011-06-15  2:53           ` Chris Fowler
2011-06-15 13:50           ` Chris Fowler
2011-06-15 20:07             ` David Rientjes
2011-06-15 20:11               ` Chris Fowler
2011-06-15  2:48       ` Chris Fowler
2011-06-15  0:41 ` KAMEZAWA Hiroyuki
2011-06-15  1:44   ` Chris Fowler
2011-06-15  2:05     ` David Rientjes
2011-06-15  0:54 ` KOSAKI Motohiro

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=1308058276.2074.295.camel@compaq-desktop \
    --to=cfowler@outpostsentinel.com \
    --cc=cfowler@opsdc.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