From: Michal Hocko <mhocko@kernel.org>
To: Yisheng Xie <xieyisheng1@huawei.com>
Cc: Vlastimil Babka <vbabka@suse.cz>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>,
Hanjun Guo <guohanjun@huawei.com>
Subject: Re: [RFC] 3.10 kernel- oom with about 24G free memory
Date: Thu, 9 Feb 2017 14:26:28 +0100 [thread overview]
Message-ID: <20170209132628.GI10257@dhcp22.suse.cz> (raw)
In-Reply-To: <9a22aefd-dfb8-2e4c-d280-fc172893bcb4@huawei.com>
On Thu 09-02-17 20:54:49, Yisheng Xie wrote:
> Hi all,
> I get an oom on a linux 3.10 kvm guest OS. when it triggers the oom
> it have about 24G free memory(and host OS have about 10G free memory)
> and watermark is sure ok.
>
> I also check about about memcg limit value, also cannot find the
> root cause.
>
> Is there anybody ever meet similar problem and have any idea about it?
>
> Any comment is more than welcome!
>
> Thanks
> Yisheng Xie
>
> -------------
> [ 81.234289] DefSch0200 invoked oom-killer: gfp_mask=0xd0, order=0, oom_score_adj=0
> [ 81.234295] DefSch0200 cpuset=/ mems_allowed=0
> [ 81.234299] CPU: 3 PID: 8284 Comm: DefSch0200 Tainted: G O E ----V------- 3.10.0-229.42.1.105.x86_64 #1
> [ 81.234301] Hardware name: OpenStack Foundation OpenStack Nova, BIOS rel-1.8.1-0-g4adadbd-20161111_105425-HGH1000008200 04/01/2014
> [ 81.234303] ffff880ae2900000 000000002b3489d7 ffff880b6cec7c58 ffffffff81608d3d
> [ 81.234307] ffff880b6cec7ce8 ffffffff81603d1c 0000000000000000 ffff880b6cd09000
> [ 81.234311] ffff880b6cec7cd8 000000002b3489d7 ffff880b6cec7ce0 ffffffff811bdd77
> [ 81.234314] Call Trace:
> [ 81.234323] [<ffffffff81608d3d>] dump_stack+0x19/0x1b
> [ 81.234327] [<ffffffff81603d1c>] dump_header+0x8e/0x214
> [ 81.234333] [<ffffffff811bdd77>] ? mem_cgroup_iter+0x177/0x2b0
> [ 81.234339] [<ffffffff8115d83e>] check_panic_on_oom+0x2e/0x60
> [ 81.234342] [<ffffffff811c17bf>] mem_cgroup_oom_synchronize+0x34f/0x580
OK, so this is a memcg OOM killer which panics because the configuration
says so. The OOM report doesn't say so and that is the bug. dump_header
is memcg aware and mem_cgroup_out_of_memory initializes oom_control
properly. Is this Vanilla kernel?
--
Michal Hocko
SUSE Labs
--
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/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-02-09 13:26 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-09 12:54 Yisheng Xie
2017-02-09 13:26 ` Michal Hocko [this message]
2017-02-09 13:41 ` Tetsuo Handa
2017-02-09 13:41 ` Michal Hocko
2017-02-10 1:13 ` Yisheng Xie
2017-02-10 7:09 ` Michal Hocko
2017-02-10 8:48 ` Yisheng Xie
2017-02-10 8:52 ` Michal Hocko
2017-02-10 9:15 ` Yisheng Xie
2017-02-10 9:24 ` Michal Hocko
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=20170209132628.GI10257@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=guohanjun@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penguin-kernel@I-love.SAKURA.ne.jp \
--cc=vbabka@suse.cz \
--cc=xieyisheng1@huawei.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