linux-kernel - Re: Panic on OOM

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2011 19:51:51 -0700 (PDT)
From:	David Rientjes <rientjes@...gle.com>
To:	cfowler@...dc.com
cc:	linux-kernel@...r.kernel.org
Subject: Re: Panic on OOM

On Tue, 14 Jun 2011, Chris Fowler wrote:

> > More supporting evidence is that in the initial report that you said
> > you had seen the panic and "Rebooting in 10 seconds..." 
> 
> There was a long period between when the box became unresponsive and the
> panic happened.

Yes, that may indicate a VM issue that changed between v2.6.33 and v2.6.38 
that caused the oom killer not to get triggered right away.

> I did not time it but I left it alone in the afternoon
> and later that night I saw the panic.  I know the panic was not
> immediate.
> 

I was attempting to diagnose an issue where the machine failed to actually 
reboot after the "Rebooting in 10 seconds..." message.  So the issue is 
that the machine becomes unresponsive for an indefinite period of time 
between invoking your perl script and seeing the panic, or that the 
machine fails to reboot after "Rebooting in 10 seconds..."?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/