From: Michal Hocko <mhocko@kernel.org>
To: Vlastimil Babka <vbabka@suse.cz>
Cc: Pankaj Suryawanshi <pankajssuryawanshi@gmail.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
pankaj.suryawanshi@einfochips.com
Subject: Re: oom-killer
Date: Mon, 5 Aug 2019 14:05:25 +0200 [thread overview]
Message-ID: <20190805120525.GL7597@dhcp22.suse.cz> (raw)
In-Reply-To: <0821a17d-1703-1b82-d850-30455e19e0c1@suse.cz>
On Mon 05-08-19 13:56:20, Vlastimil Babka wrote:
> On 8/5/19 1:24 PM, Michal Hocko wrote:
> >> [ 727.954355] CPU: 0 PID: 56 Comm: kworker/u8:2 Tainted: P O 4.14.65 #606
> > [...]
> >> [ 728.029390] [<c034a094>] (oom_kill_process) from [<c034af24>] (out_of_memory+0x140/0x368)
> >> [ 728.037569] r10:00000001 r9:c12169bc r8:00000041 r7:c121e680 r6:c1216588 r5:dd347d7c > [ 728.045392] r4:d5737080
> >> [ 728.047929] [<c034ade4>] (out_of_memory) from [<c03519ac>] (__alloc_pages_nodemask+0x1178/0x124c)
> >> [ 728.056798] r7:c141e7d0 r6:c12166a4 r5:00000000 r4:00001155
> >> [ 728.062460] [<c0350834>] (__alloc_pages_nodemask) from [<c021e9d4>] (copy_process.part.5+0x114/0x1a28)
> >> [ 728.071764] r10:00000000 r9:dd358000 r8:00000000 r7:c1447e08 r6:c1216588 r5:00808111
> >> [ 728.079587] r4:d1063c00
> >> [ 728.082119] [<c021e8c0>] (copy_process.part.5) from [<c0220470>] (_do_fork+0xd0/0x464)
> >> [ 728.090034] r10:00000000 r9:00000000 r8:dd008400 r7:00000000 r6:c1216588 r5:d2d58ac0
> >> [ 728.097857] r4:00808111
> >
> > The call trace tells that this is a fork (of a usermodhlper but that is
> > not all that important.
> > [...]
> >> [ 728.260031] DMA free:17960kB min:16384kB low:25664kB high:29760kB active_anon:3556kB inactive_anon:0kB active_file:280kB inactive_file:28kB unevictable:0kB writepending:0kB present:458752kB managed:422896kB mlocked:0kB kernel_stack:6496kB pagetables:9904kB bounce:0kB free_pcp:348kB local_pcp:0kB free_cma:0kB
> >> [ 728.287402] lowmem_reserve[]: 0 0 579 579
> >
> > So this is the only usable zone and you are close to the min watermark
> > which means that your system is under a serious memory pressure but not
> > yet under OOM for order-0 request. The situation is not great though
>
> Looking at lowmem_reserve above, wonder if 579 applies here? What does
> /proc/zoneinfo say?
This is GFP_KERNEL request essentially so there shouldn't be any lowmem
reserve here, no?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2019-08-05 12:05 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-03 13:23 oom-killer Pankaj Suryawanshi
2019-08-05 11:24 ` oom-killer Michal Hocko
2019-08-05 11:56 ` oom-killer Vlastimil Babka
2019-08-05 12:05 ` Michal Hocko [this message]
2019-08-05 15:34 ` oom-killer Pankaj Suryawanshi
2019-08-05 20:16 ` oom-killer Michal Hocko
2019-08-06 14:54 ` oom-killer Pankaj Suryawanshi
2019-08-06 15:07 ` oom-killer Michal Hocko
2019-08-06 15:09 ` oom-killer Pankaj Suryawanshi
2019-08-06 15:12 ` oom-killer Michal Hocko
2019-08-06 15:23 ` oom-killer Pankaj Suryawanshi
2019-08-06 10:04 ` oom-killer Vlastimil Babka
2019-08-06 14:55 ` oom-killer Pankaj Suryawanshi
2019-08-06 15:11 ` oom-killer 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=20190805120525.GL7597@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=pankaj.suryawanshi@einfochips.com \
--cc=pankajssuryawanshi@gmail.com \
--cc=vbabka@suse.cz \
/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).