From: "Paweł 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 [thread overview]
Message-ID: <1888499.Wt33pfNhUs@vmx> (raw)
In-Reply-To: <20120229200910.GB31348@kroah.com>
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...
next prev parent reply other threads:[~2012-02-29 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3905756.9FRF7uBtcE@vmx>
2012-02-29 20:09 ` [3.2.2] oom + no-killable-processes Greg KH
2012-02-29 20:53 ` Paweł Sikora [this message]
2012-03-01 1:22 ` David Rientjes
2012-02-29 19:38 Paweł Sikora
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=1888499.Wt33pfNhUs@vmx \
--to=pawel.sikora@agmk.net \
--cc=gregkh@linuxfoundation.org \
--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