From: Sachin Sant <sachinp@in.ibm.com>
To: Dave Hansen <dave@linux.vnet.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: Fri, 10 Jul 2009 12:34:25 +0530 [thread overview]
Message-ID: <4A56E7F9.9030405@in.ibm.com> (raw)
In-Reply-To: <1247066549.14309.1029.camel@nimitz>
Dave Hansen wrote:
> 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.
>
Thanks Dave for the pointers.
I am able to consistently recreate this issue with next 0708. hackbench
creates 3600 tasks in my case. After starting the tests machine becomes
unresponsive and i finally have to reboot it.
The test ran successfully on next03, but unfortunately i did
not save the config file for that run. If i use the config file from
0708 and compile a 0703, the machine becomes unresponsive because
of OOM's. I can't explain why the test ran successfully against
0703 :-( in previous attempt.
Only data point i have at this time is the same tests runs successfully
against 2.6.31-rc2. But may be that's not even an argument :-)
Thanks
-Sachin
--
---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------
prev parent reply other threads:[~2009-07-10 7:04 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
2009-07-10 7:04 ` Sachin Sant [this message]
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=4A56E7F9.9030405@in.ibm.com \
--to=sachinp@in.ibm.com \
--cc=dave@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--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