From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754207AbdA0Hgl (ORCPT ); Fri, 27 Jan 2017 02:36:41 -0500 Received: from mx2.suse.de ([195.135.220.15]:36757 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754018AbdA0Hgj (ORCPT ); Fri, 27 Jan 2017 02:36:39 -0500 Date: Fri, 27 Jan 2017 08:36:31 +0100 From: Michal Hocko To: Trevor Cordes Cc: Mel Gorman , linux-kernel@vger.kernel.org, Joonsoo Kim , Minchan Kim , Rik van Riel , Srikar Dronamraju Subject: Re: mm, vmscan: commit makes PAE kernel crash nightly (bisected) Message-ID: <20170127073631.GA4143@dhcp22.suse.cz> References: <20170117142114.r7abr3x2bbik47sd@techsingularity.net> <20170117145450.GQ19699@dhcp22.suse.cz> <20170119034850.0b7d504c@pog.tecnopolis.ca> <20170119113757.GP30786@dhcp22.suse.cz> <20170120003544.7e6e34d1@pog.tecnopolis.ca> <20170120110232.y7xd4b7wtwqslgnw@techsingularity.net> <20170120155553.gjv2x5eycvdudnil@techsingularity.net> <20170122184559.0b5c0fd8@pog.tecnopolis.ca> <20170124125458.GH6867@dhcp22.suse.cz> <20170126171858.5e1b484a@pog.tecnopolis.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170126171858.5e1b484a@pog.tecnopolis.ca> User-Agent: Mutt/1.6.0 (2016-04-01) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu 26-01-17 17:18:58, Trevor Cordes wrote: > On 2017-01-24 Michal Hocko wrote: > > On Sun 22-01-17 18:45:59, Trevor Cordes wrote: > > [...] > > > Also, completely separate from your patch I ran mhocko's 4.9 tree > > > with mem=2G to see if lower ram amount would help, but it didn't. > > > Even with 2G the system oom and hung same as usual. So far the > > > only thing that helps at all was the cgroup_disable=memory option, > > > which makes the problem disappear completely for me. > > > > OK, can we reduce the problem space slightly more and could you boot > > with kmem accounting enabled? cgroup.memory=nokmem,nosocket > > I ran for 30 hours with cgroup.memory=nokmem,nosocket using vanilla > 4.9.0+ and it oom'd during a big rdiff-backup at 9am. My script was > able to reboot it before it hung. Only one oom occurred before the > reboot, which is a bit odd, usually there is 5-50. See attached > messages log (oom6). > > So, still, only cgroup_disable=memory mitigates this bug (so far). If > you need me to test cgroup.memory=nokmem,nosocket with your since-4.9 > branch specifically, let me know and I'll add it to the to-test list. OK, that matches the theory that these OOMs are caused by the incorrect active list aging fixed by b4536f0c829c ("mm, memcg: fix the active list aging for lowmem requests when memcg is enabled") -- Michal Hocko SUSE Labs