Re: Panic on OOM

[Chris Fowler <cfowler@outpostsentinel.com>]

On Tue, 2011-06-14 at 19:32 -0700, David Rientjes wrote:
> On Tue, 14 Jun 2011, Chris Fowler wrote:
> 
> > > Using /proc/sys/vm/panic_on_oom also won't panic the machine if you
> > > happen to use a cpuset or mempolicy.  You'll want to write '2' instead
> > > if you want to panic in all possible oom conditions.
> > > 
> > > 
> > 
> > 2 did it.  Thank you.
> > 
> > perl -e 'my @mem = (); while(1) { push @mem, "XXXXXXXXXXXXXXXX"; }'
> > 
> > I lost connection and it came back after about 30s.  Reboot worked.
> > 
> 
> That wasn't meant as a fix for the problem but rather just a suggestion 
> based on how you're using the device.
> 
> It's just a coincidence that it worked that time, because 
> /proc/sys/vm/panic_on_oom == 2 is the exact same as 
> /proc/sys/vm/panic_on_oom == 1 with the .config you posted (since you 
> don't have CONFIG_NUMA, constrained_alloc() always returns CONSTRAINT_NONE 
> in the oom killer).

Yea you're right.  I just did it again and it does not reboot.  It goes
in this state where it no longer responds.  The keyboard is not
responsive the screen blank no longer works, etc.  

Right now I'm just waiting for it to panic.