From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f70.google.com (mail-lf0-f70.google.com [209.85.215.70]) by kanga.kvack.org (Postfix) with ESMTP id 633B06B0069 for ; Mon, 19 Sep 2016 04:42:42 -0400 (EDT) Received: by mail-lf0-f70.google.com with SMTP id y6so32999697lff.0 for ; Mon, 19 Sep 2016 01:42:42 -0700 (PDT) Received: from mail-wm0-x22b.google.com (mail-wm0-x22b.google.com. [2a00:1450:400c:c09::22b]) by mx.google.com with ESMTPS id k9si25556209wjx.225.2016.09.19.01.42.40 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 19 Sep 2016 01:42:41 -0700 (PDT) Received: by mail-wm0-x22b.google.com with SMTP id 1so145026986wmz.1 for ; Mon, 19 Sep 2016 01:42:40 -0700 (PDT) Date: Mon, 19 Sep 2016 09:42:37 +0100 From: Lorenzo Stoakes Subject: Re: More OOM problems Message-ID: <20160919084237.GA30625@lucifer> References: <20160918202614.GB31286@lucifer> <20160919083215.GF10785@dhcp22.suse.cz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160919083215.GF10785@dhcp22.suse.cz> Sender: owner-linux-mm@kvack.org List-ID: To: Michal Hocko Cc: Linus Torvalds , Tetsuo Handa , Oleg Nesterov , Vladimir Davydov , Vlastimil Babka , Andrew Morton , Markus Trippelsdorf , Arkadiusz Miskiewicz , Ralf-Peter Rohbeck , Jiri Slaby , Olaf Hering , Joonsoo Kim , linux-mm On Mon, Sep 19, 2016 at 10:32:15AM +0200, Michal Hocko wrote: > > so this is the same thing as in Linus case. All the zones are hitting > min wmark so the should_compact_retry() gave up. As mentioned in other > email [1] this is inherent limitation of the workaround. Your system is > swapless but there is a lot of the reclaimable page cache so Vlastimil's > patches should help. I will experiment with a linux-next kernel and see if the problem recurs. I've attempted to see if there is a way to manually reproduce on the mainline kernel by performing workloads that triggered the OOM (loading google sheets tabs, compiling a kernel, playing a video on youtube), but to no avail - it seems the system needs to be sufficiently fragmented first before it'll trigger. Given that's the case, I'll just have to try using the linux-next kernel and if you don't hear from me you can assume it did not repro again :) I actually have a whole bunch of other OOM kill logs that I saved from previous occurrences of this issue, would it be useful for me to pastebin them, or would they not add anything of use beyond what's been shown in this thread? -- 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: email@kvack.org