From: =?utf-8?B?UGF3ZcWC?= Sikora <pawel.sikora@agmk.net>
To: Greg KH <gregkh@linuxfoundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [3.2.2] oom + no-killable-processes.
Date: Wed, 29 Feb 2012 21:53:35 +0100
Message-ID: <1888499.Wt33pfNhUs@vmx>
User-Agent: KMail/4.8.0 (Linux/3.2.7-1; KDE/4.8.0; x86_64; ; )
In-Reply-To: <20120229200910.GB31348@kroah.com>
References: <3905756.9FRF7uBtcE@vmx> <20120229200910.GB31348@kroah.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8BIT
Content-Type: text/plain; charset="utf-8"
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 943
Lines: 19

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@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/