linux-kernel - Re: [3.2.2] oom + no-killable-processes.

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]

Message-ID: <1888499.Wt33pfNhUs@vmx>
Date:	Wed, 29 Feb 2012 21:53:35 +0100
From:	Paweł Sikora <pawel.sikora@...k.net>
To:	Greg KH <gregkh@...uxfoundation.org>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [3.2.2] oom + no-killable-processes.

On Wednesday 29 of February 2012 12:09:10 Greg KH wrote:
> On Wed, Feb 29, 2012 at 08:28:23PM +0100, Paweł Sikora wrote:
> > Hi all,
> > 
> > i've found on my 8-core opterons following oops (oom+nokillable): http://imgbin.org/index.php?page=image&id=6945
> > usualy the kernel just kills processes from userspace but this time something has gone wrong...
> > sysrq was dead, so no more stacktraces :/
> 
> Is this something new with 3.2.2?

i see such nokillable oom first time. the 3.1.x stable has been working for few months.
as you can see on the oops timestamp the 3.2.2 failed after ~27.5d so it isn't an immediate
crash which can be easily bisected :/ currently i'm stressing the 3.2.7...

--
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/