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 12:57:00 +0200 [thread overview]
Message-ID: <20160331105700.GD27831@dhcp22.suse.cz> (raw)
In-Reply-To: <56FCEFFE.6040604@huawei.com>
On Thu 31-03-16 17:38:06, Xishi Qiu wrote:
[...]
> Hi Michal,
>
> It's arm64, so DMA is [0-4G], and Normal is [4G-]
I wasn't aware of that. Thanks for the clarification.
> Is that something wrong with the RAM hardware, then trigger the problem?
This is hard to tell but I would try to check which of the page fault
path has returned with VM_FAULT_OOM. This might be a wrong .fault
callback.
--
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>
prev parent reply other threads:[~2016-03-31 10:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-31 9:16 [RFC] oom, but there is enough memory Xishi Qiu
2016-03-31 9:30 ` Michal Hocko
2016-03-31 9:38 ` Xishi Qiu
2016-03-31 10:57 ` Michal Hocko [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=20160331105700.GD27831@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;
as well as URLs for NNTP newsgroup(s).