linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Wei Yang <richard.weiyang@gmail.com>
To: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
Cc: Wei Yang <richard.weiyang@gmail.com>, Bo Xu <xubo@kylinos.cn>,
	linux-mm@kvack.org
Subject: Re: [Q] page allocation failure when there are many free pages
Date: Tue, 19 Apr 2022 00:06:39 +0000	[thread overview]
Message-ID: <20220419000639.khdot3kigk6s2jne@master> (raw)
In-Reply-To: <4d1daf7a-d660-8661-220d-969bf81a2fbb@I-love.SAKURA.ne.jp>

On Mon, Apr 18, 2022 at 05:22:40PM +0900, Tetsuo Handa wrote:
>On 2022/04/18 15:29, Bo Xu wrote:
>> Hi, Yang
>> 
>> ?????? From the messages you provided, there are not much free pages.
>> ?????? I guess the page alloc is happing in Node 0 with zone
>> ?????? Normal.But in zone Normal free mem is lower than low mem,so
>> ?????? there are some memory pressure is your machine.But now i have
>> ?????? no idea why page recliam or others did not make effect.
>> 
>
>The kernel says that it was a GFP_NOWAIT allocation request, which does not
>wait for page reclaim or others.
>
>  java: page allocation failure: order:0, mode:0x400000(GFP_NOWAIT), nodemask=(null),cpuset=/,mems_allowed=0
>  CPU: 6 PID: 7121 Comm: java Kdump: loaded Not tainted 4.19.95-29 #1
>
>Question is why it was a GFP_NOWAIT allocation request. Try installing debuginfo kernel
>package and decoding exact call traces (filenames and lines) using scripts/faddr2line .

Thanks, let me have a try.

-- 
Wei Yang
Help you, Help me


  reply	other threads:[~2022-04-19  0:06 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-17  3:35 Wei Yang
2022-04-18  6:29 ` Bo Xu
2022-04-18  8:22   ` Tetsuo Handa
2022-04-19  0:06     ` Wei Yang [this message]
2022-04-19  0:03   ` Wei Yang

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=20220419000639.khdot3kigk6s2jne@master \
    --to=richard.weiyang@gmail.com \
    --cc=linux-mm@kvack.org \
    --cc=penguin-kernel@I-love.SAKURA.ne.jp \
    --cc=xubo@kylinos.cn \
    /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