From: Michal Hocko <mhocko@kernel.org>
To: Xishi Qiu <qiuxishi@huawei.com>
Cc: Linux MM <linux-mm@kvack.org>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] oom, but there is enough memory
Date: Thu, 31 Mar 2016 11:30:12 +0200 [thread overview]
Message-ID: <20160331093011.GC27831@dhcp22.suse.cz> (raw)
In-Reply-To: <56FCEAD0.9080806@huawei.com>
On Thu 31-03-16 17:16:00, Xishi Qiu wrote:
> It triggers a lot of ooms, but there is enough memory(many large blocks).
> And at last "Kernel panic - not syncing: Out of memory and no killable processes..."
>
> I find almost the every call trace include "pagefault_out_of_memory" and "gfp_mask=0x0".
> If it does oom, why not it triger in mm core path?
It seems that somebody in the page fault path has returned with
VM_FAULT_OOM without invoking the page allocator and kept returning the
same error until there is nothing killable and so the oom killer panics.
[...]
> <4>[63651.040374s][pid:2912,cpu3,sh]DMA free:550600kB min:5244kB low:27580kB high:28892kB active_anon:343060kB inactive_anon:1224kB active_file:107596kB inactive_file:465156kB unevictable:1040kB isolated(anon):0kB isolated(file):0kB present:2016252kB managed:1720040kB mlocked:1040kB dirty:40kB writeback:0kB mapped:200420kB shmem:1312kB slab_reclaimable:27048kB slab_unreclaimable:73300kB kernel_stack:15248kB pagetables:14484kB unstable:0kB bounce:0kB free_cma:30896kB writeback_tmp:0kB pages_scanned:0 all_unreclaimable? no
This is rather weird. DMA zone with 2GB? What kind of architecture is
this?
--
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:[~2016-03-31 9:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 9:16 Xishi Qiu
2016-03-31 9:30 ` Michal Hocko [this message]
2016-03-31 9:38 ` Xishi Qiu
2016-03-31 10:57 ` 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=20160331093011.GC27831@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=qiuxishi@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