From: Dave Hansen <dave@linux.vnet.ibm.com>
To: Sachin Sant <sachinp@in.ibm.com>
Cc: Stephen Rothwell <sfr@canb.auug.org.au>,
linux-next@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: OOM with hackbench against next 0708
Date: Wed, 08 Jul 2009 08:22:29 -0700 [thread overview]
Message-ID: <1247066549.14309.1029.camel@nimitz> (raw)
In-Reply-To: <4A5499B4.5050007@in.ibm.com>
On Wed, 2009-07-08 at 18:35 +0530, Sachin Sant wrote:
> While executing hackbench against today's next on a 4 way
> power6 box (9117 MMA), the machine crawled within few seconds
> with lots of OOM messages. I captured a Crash dump and was
> able to extract the dmesg log which i have attached here.
>
> This problem started with 0706 next release. 0703 worked fine.
>
> Kernel is compiled with SLQB and 64K page size.
>
> .config attached. Let me know what other information i can
> provide to find a solution for this problem.
This doesn't look like a kernel bug at all to me. You're out of memory,
out of swap, and the thing that got killed was the thing allocating
memory. You're also down to 65MB of pagecache, which is awfully low for
a 6GB machine. That tells me it's also been effective in reclaiming
disk cache.
There are a couple of possibilities:
1. hackbench is broken, allocating too much memory and ooming, or it
has been misconfigured by a user
2. hackbench broke because something the kernel is telling it is wrong
3. The kernel is leaking (or just plain using) some memory more than a
few releases ago, and that caused the oom.
I'd go back and carefully examine how hackbench is being run and that it
is consistent. You should also double-check your finding that the
several-day-old -next isn't seeing this issue.
-- Dave
next prev parent reply other threads:[~2009-07-08 15:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-08 7:31 linux-next: Tree for July 8 Stephen Rothwell
2009-07-08 13:05 ` OOM with hackbench against next 0708 Sachin Sant
2009-07-08 15:22 ` Dave Hansen [this message]
2009-07-10 7:04 ` Sachin Sant
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=1247066549.14309.1029.camel@nimitz \
--to=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=sachinp@in.ibm.com \
--cc=sfr@canb.auug.org.au \
/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