From: Dave Jones <davej@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: linux-mm@kvack.org, Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: 3.4-rc4 oom killer out of control.
Date: Thu, 26 Apr 2012 17:52:57 -0400 [thread overview]
Message-ID: <20120426215257.GA12908@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1204261437470.28376@chino.kir.corp.google.com>
On Thu, Apr 26, 2012 at 02:40:48PM -0700, David Rientjes wrote:
> On Thu, 26 Apr 2012, Dave Jones wrote:
>
> > On a test machine that was running my system call fuzzer, I just saw
> > the oom killer take out everything but the process that was doing all
> > the memory exhausting.
> >
>
> Would it be possible to try the below patch? It should kill the thread
> using the most memory (which happens to only be a couple more megabytes on
> your system), but it might just delay the inevitable since the system is
> still in a pretty bad state.
>
> KOSAKI-san suggested doing this before and I think it's the best direction
> to go in anyway.
Sure, I'll give it a shot when I reboot.
However, see my follow-up message. I think there are two bugs here.
1) The over-aggressive oom-killer, and 2) ksmd going mental.
/sys/kernel/mm/ksm/full_scans is increasing constantly
full_scans: 146370
pages_shared: 1
pages_sharing: 4
pages_to_scan: 1250
pages_unshared: 867
pages_volatile: 1
run: 1
sleep_millisecs: 20
everything in /sys/kernel/mm/hugepages/hugepages-2048kB, is 0.
/sys/kernel/mm/transparent_hugepage/khugepaged:
alloc_sleep_millisecs 60000
defrag 1
full_scans 15
max_ptes_none 511
pages_collapsed 6
pages_to_scan 4096
scan_sleep_millisecs 10000
Dave
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-04-26 21:53 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-26 19:35 3.4-rc4 oom killer out of control Dave Jones
2012-04-26 20:53 ` Dave Jones
2012-04-26 22:30 ` David Rientjes
2012-04-26 21:40 ` David Rientjes
2012-04-26 21:52 ` Dave Jones [this message]
2012-04-26 22:20 ` David Rientjes
2012-04-26 22:44 ` Dave Jones
2012-04-26 22:49 ` David Rientjes
2012-04-26 22:54 ` Dave Jones
2012-04-27 0:54 ` Steven Rostedt
2012-04-27 2:02 ` Dave Jones
2012-05-03 22:14 ` David Rientjes
2012-05-03 22:29 ` Dave Jones
2012-05-17 21:33 ` [patch] mm, oom: normalize oom scores to oom_score_adj scale only for userspace David Rientjes
2012-05-17 21:50 ` Andrew Morton
2012-05-23 7:15 ` [patch v2] " David Rientjes
2012-05-23 22:37 ` Andrew Morton
2012-05-24 6:02 ` David Rientjes
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=20120426215257.GA12908@redhat.com \
--to=davej@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
/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;
as well as URLs for NNTP newsgroup(s).