From: Dave Jones <davej@redhat.com>
To: David Rientjes <rientjes@google.com>
Cc: M <sah_8@yahoo.com>, linux-mm@kvack.org
Subject: Re: kernel crash
Date: Thu, 22 Sep 2011 17:53:01 -0400 [thread overview]
Message-ID: <20110922215301.GA752@redhat.com> (raw)
In-Reply-To: <alpine.DEB.2.00.1109221430450.2635@chino.kir.corp.google.com>
On Thu, Sep 22, 2011 at 02:38:47PM -0700, David Rientjes wrote:
> The problem is this:
>
> Sep 20 19:39:19 host2 kernel: [1933000.196980] [ pid ] uid tgid total_vm rss cpu oom_adj oom_score_adj name
> ...
> Sep 20 19:39:19 host2 kernel: [1933000.197559] [13918] 507 13918 17992270 7758558 4 -17 -1000 root.exe
>
> root.exe is has about 29.5GB of the 32GB available memory in RAM, and it's
> set to have a /proc/13918/oom_score_adj of -1000 meaning it's not eligible
> for oom killing. So the kernel panics rather than kill the task.
>
> There's not much the kernel can be expected to do in such a configuration,
> you've simply exhausted all RAM and swap. You can set
> /proc/pid/oom_score_adj to not be -1000 so that it is at least eligible to
> be killed in these circumstances rather than panic the machine, but the VM
> will continue to oom under this configuration.
It's surprising that the same workload in 32-bit works.
Manoj, is root.exe recompiled for 64-bit ? I'm wondering if it's just that
the expansion of a lot of unsigned longs are causing increased memory use vs
the original 32bit use-case.
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>
prev parent reply other threads:[~2011-09-22 21:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-22 18:45 kernel crash M
2011-09-22 21:24 ` Dave Jones
2011-09-22 21:38 ` David Rientjes
2011-09-22 21:53 ` Dave Jones [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=20110922215301.GA752@redhat.com \
--to=davej@redhat.com \
--cc=linux-mm@kvack.org \
--cc=rientjes@google.com \
--cc=sah_8@yahoo.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).