From: Michal Hocko <mhocko@kernel.org> To: Gerhard Wiesinger <lists@wiesinger.com> Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: Still OOM problems with 4.9er kernels Date: Fri, 9 Dec 2016 17:09:46 +0100 [thread overview] Message-ID: <20161209160946.GE4334@dhcp22.suse.cz> (raw) In-Reply-To: <a0bf765f-d5dd-7a51-1a6b-39cbda56bd58@wiesinger.com> On Fri 09-12-16 16:52:07, Gerhard Wiesinger wrote: > On 09.12.2016 14:40, Michal Hocko wrote: > > On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote: > > > Hello, > > > > > > same with latest kernel rc, dnf still killed with OOM (but sometimes > > > better). > > > > > > ./update.sh: line 40: 1591 Killed ${EXE} update ${PARAMS} > > > (does dnf clean all;dnf update) > > > Linux database.intern 4.9.0-0.rc8.git2.1.fc26.x86_64 #1 SMP Wed Dec 7 > > > 17:53:29 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > > > > > > Updated bug report: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1314697 > > Could you post your oom report please? > > E.g. a new one with more than one included, first one after boot ... > > Just setup a low mem VM under KVM and it is easily triggerable. What is the workload? > Still enough virtual memory available ... Well, you will always have a lot of virtual memory... > 4.9.0-0.rc8.git2.1.fc26.x86_64 > > [ 624.862777] ksoftirqd/0: page allocation failure: order:0, mode:0x2080020(GFP_ATOMIC) [...] > [95895.765570] kworker/1:1H: page allocation failure: order:0, mode:0x2280020(GFP_ATOMIC|__GFP_NOTRACK) These are atomic allocation failures and should be recoverable. [...] > [97883.838418] httpd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=0, order=0, oom_score_adj=0 But this is a real OOM killer invocation because a single page allocation cannot proceed. [...] > [97883.882611] Mem-Info: > [97883.883747] active_anon:2915 inactive_anon:3376 isolated_anon:0 > active_file:3902 inactive_file:3639 isolated_file:0 > unevictable:0 dirty:205 writeback:0 unstable:0 > slab_reclaimable:9856 slab_unreclaimable:9682 > mapped:3722 shmem:59 pagetables:2080 bounce:0 > free:748 free_pcp:15 free_cma:0 there is still some page cache which doesn't seem to be neither dirty nor under writeback. So it should be theoretically reclaimable but for some reason we cannot seem to reclaim that memory. There is still some anonymous memory and free swap so we could reclaim it as well but it all seems pretty down and the memory pressure is really large > [97883.890766] Node 0 active_anon:11660kB inactive_anon:13504kB > active_file:15608kB inactive_file:14556kB unevictable:0kB isolated(anon):0kB > isolated(file):0kB mapped:14888kB dirty:820kB writeback:0kB shmem:0kB > shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 236kB writeback_tmp:0kB > unstable:0kB pages_scanned:168352 all_unreclaimable? yes all_unreclaimable also agrees that basically nothing is reclaimable. That was one of the criterion to hit the OOM killer prior to the rewrite in 4.6 kernel. So I suspect that older kernels would OOM under your memory pressure as well. -- Michal Hocko SUSE Labs
WARNING: multiple messages have this Message-ID (diff)
From: Michal Hocko <mhocko@kernel.org> To: Gerhard Wiesinger <lists@wiesinger.com> Cc: linux-kernel@vger.kernel.org, linux-mm@kvack.org, Linus Torvalds <torvalds@linux-foundation.org> Subject: Re: Still OOM problems with 4.9er kernels Date: Fri, 9 Dec 2016 17:09:46 +0100 [thread overview] Message-ID: <20161209160946.GE4334@dhcp22.suse.cz> (raw) In-Reply-To: <a0bf765f-d5dd-7a51-1a6b-39cbda56bd58@wiesinger.com> On Fri 09-12-16 16:52:07, Gerhard Wiesinger wrote: > On 09.12.2016 14:40, Michal Hocko wrote: > > On Fri 09-12-16 08:06:25, Gerhard Wiesinger wrote: > > > Hello, > > > > > > same with latest kernel rc, dnf still killed with OOM (but sometimes > > > better). > > > > > > ./update.sh: line 40: 1591 Killed ${EXE} update ${PARAMS} > > > (does dnf clean all;dnf update) > > > Linux database.intern 4.9.0-0.rc8.git2.1.fc26.x86_64 #1 SMP Wed Dec 7 > > > 17:53:29 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux > > > > > > Updated bug report: > > > https://bugzilla.redhat.com/show_bug.cgi?id=1314697 > > Could you post your oom report please? > > E.g. a new one with more than one included, first one after boot ... > > Just setup a low mem VM under KVM and it is easily triggerable. What is the workload? > Still enough virtual memory available ... Well, you will always have a lot of virtual memory... > 4.9.0-0.rc8.git2.1.fc26.x86_64 > > [ 624.862777] ksoftirqd/0: page allocation failure: order:0, mode:0x2080020(GFP_ATOMIC) [...] > [95895.765570] kworker/1:1H: page allocation failure: order:0, mode:0x2280020(GFP_ATOMIC|__GFP_NOTRACK) These are atomic allocation failures and should be recoverable. [...] > [97883.838418] httpd invoked oom-killer: gfp_mask=0x24201ca(GFP_HIGHUSER_MOVABLE|__GFP_COLD), nodemask=0, order=0, oom_score_adj=0 But this is a real OOM killer invocation because a single page allocation cannot proceed. [...] > [97883.882611] Mem-Info: > [97883.883747] active_anon:2915 inactive_anon:3376 isolated_anon:0 > active_file:3902 inactive_file:3639 isolated_file:0 > unevictable:0 dirty:205 writeback:0 unstable:0 > slab_reclaimable:9856 slab_unreclaimable:9682 > mapped:3722 shmem:59 pagetables:2080 bounce:0 > free:748 free_pcp:15 free_cma:0 there is still some page cache which doesn't seem to be neither dirty nor under writeback. So it should be theoretically reclaimable but for some reason we cannot seem to reclaim that memory. There is still some anonymous memory and free swap so we could reclaim it as well but it all seems pretty down and the memory pressure is really large > [97883.890766] Node 0 active_anon:11660kB inactive_anon:13504kB > active_file:15608kB inactive_file:14556kB unevictable:0kB isolated(anon):0kB > isolated(file):0kB mapped:14888kB dirty:820kB writeback:0kB shmem:0kB > shmem_thp: 0kB shmem_pmdmapped: 0kB anon_thp: 236kB writeback_tmp:0kB > unstable:0kB pages_scanned:168352 all_unreclaimable? yes all_unreclaimable also agrees that basically nothing is reclaimable. That was one of the criterion to hit the OOM killer prior to the rewrite in 4.6 kernel. So I suspect that older kernels would OOM under your memory pressure as well. -- 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-12-09 16:09 UTC|newest] Thread overview: 88+ messages / expand[flat|nested] mbox.gz Atom feed top 2016-11-30 7:10 Still OOM problems with 4.9er kernels Gerhard Wiesinger 2016-11-30 7:20 ` Gerhard Wiesinger 2016-12-09 7:06 ` Gerhard Wiesinger 2016-12-09 13:40 ` Michal Hocko 2016-12-09 13:40 ` Michal Hocko 2016-12-09 15:52 ` Gerhard Wiesinger 2016-12-09 15:52 ` Gerhard Wiesinger 2016-12-09 15:58 ` Gerhard Wiesinger 2016-12-09 15:58 ` Gerhard Wiesinger 2016-12-09 16:09 ` Michal Hocko [this message] 2016-12-09 16:09 ` Michal Hocko 2016-12-09 16:58 ` Gerhard Wiesinger 2016-12-09 17:30 ` Michal Hocko 2016-12-09 17:30 ` Michal Hocko 2016-12-09 18:01 ` Gerhard Wiesinger 2016-12-09 18:01 ` Gerhard Wiesinger 2016-12-09 21:42 ` Vlastimil Babka 2016-12-09 21:42 ` Vlastimil Babka 2016-12-10 13:50 ` Gerhard Wiesinger 2016-12-10 13:50 ` Gerhard Wiesinger 2016-12-12 8:24 ` Michal Hocko 2016-12-12 8:24 ` Michal Hocko 2016-12-23 2:55 ` Minchan Kim 2016-12-23 2:55 ` Minchan Kim 2017-01-01 17:20 ` Gerhard Wiesinger 2017-01-01 17:20 ` Gerhard Wiesinger 2017-01-04 8:40 ` Gerhard Wiesinger 2017-01-04 9:11 ` Michal Hocko 2017-01-04 9:11 ` Michal Hocko 2017-02-26 8:40 ` Still OOM problems with 4.9er/4.10er kernels Gerhard Wiesinger 2017-02-27 8:27 ` Michal Hocko 2017-02-27 8:27 ` Michal Hocko 2017-02-28 6:06 ` Gerhard Wiesinger 2017-02-28 6:06 ` Gerhard Wiesinger 2017-02-28 8:14 ` Michal Hocko 2017-02-28 8:14 ` Michal Hocko 2017-02-27 9:02 ` Minchan Kim 2017-02-27 9:02 ` Minchan Kim 2017-02-27 9:44 ` Michal Hocko 2017-02-27 9:44 ` Michal Hocko 2017-02-28 5:17 ` Minchan Kim 2017-02-28 5:17 ` Minchan Kim 2017-02-28 8:12 ` Michal Hocko 2017-02-28 8:12 ` Michal Hocko 2017-03-02 7:17 ` Minchan Kim 2017-03-02 7:17 ` Minchan Kim 2017-03-16 6:38 ` Gerhard Wiesinger 2017-03-16 6:38 ` Gerhard Wiesinger 2017-03-16 8:27 ` Michal Hocko 2017-03-16 8:27 ` Michal Hocko 2017-03-16 8:47 ` lkml 2017-03-16 8:47 ` lkml 2017-03-16 9:08 ` Michal Hocko 2017-03-16 9:08 ` Michal Hocko 2017-03-16 9:23 ` lkml 2017-03-16 9:23 ` lkml 2017-03-16 9:39 ` Michal Hocko 2017-03-16 9:39 ` Michal Hocko 2017-03-17 16:37 ` Gerhard Wiesinger 2017-03-17 16:37 ` Gerhard Wiesinger 2017-03-17 17:13 ` Michal Hocko 2017-03-17 17:13 ` Michal Hocko 2017-03-17 20:08 ` Gerhard Wiesinger 2017-03-17 20:08 ` Gerhard Wiesinger 2017-03-19 8:17 ` Gerhard Wiesinger 2017-03-19 8:17 ` Gerhard Wiesinger 2017-03-20 1:54 ` Tetsuo Handa 2017-03-20 1:54 ` Tetsuo Handa 2017-03-19 15:18 ` Michal Hocko 2017-03-19 15:18 ` Michal Hocko 2017-03-19 16:02 ` Gerhard Wiesinger 2017-03-19 16:02 ` Gerhard Wiesinger 2017-03-20 3:05 ` Mike Galbraith 2017-03-20 3:05 ` Mike Galbraith 2017-03-21 5:59 ` Gerhard Wiesinger 2017-03-21 5:59 ` Gerhard Wiesinger 2017-03-21 7:13 ` Mike Galbraith 2017-03-21 7:13 ` Mike Galbraith 2017-03-23 7:16 ` Gerhard Wiesinger 2017-03-23 7:16 ` Gerhard Wiesinger 2017-03-23 8:38 ` Mike Galbraith 2017-03-23 8:38 ` Mike Galbraith 2017-03-23 14:46 ` Tetsuo Handa 2017-03-23 14:46 ` Tetsuo Handa 2017-03-26 8:36 ` Gerhard Wiesinger 2017-03-26 8:36 ` Gerhard Wiesinger 2016-12-09 16:03 ` Still OOM problems with 4.9er kernels Gerhard Wiesinger 2016-12-09 16:03 ` Gerhard Wiesinger
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=20161209160946.GE4334@dhcp22.suse.cz \ --to=mhocko@kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=linux-mm@kvack.org \ --cc=lists@wiesinger.com \ --cc=torvalds@linux-foundation.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.