From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751322AbdALJgU (ORCPT ); Thu, 12 Jan 2017 04:36:20 -0500 Received: from mx2.suse.de ([195.135.220.15]:42225 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750927AbdALJgT (ORCPT ); Thu, 12 Jan 2017 04:36:19 -0500 Date: Thu, 12 Jan 2017 10:36:14 +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: <20170112093613.GF2264@dhcp22.suse.cz> References: <20170111103243.GA27795@pog.tecnopolis.ca> <20170111121146.i53jyerxont7b74i@techsingularity.net> <20170111121428.4sswbkzyqz7vf6so@techsingularity.net> <20170111165232.0b7abe18@pog.tecnopolis.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20170111165232.0b7abe18@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 Wed 11-01-17 16:52:32, Trevor Cordes wrote: [...] > I'm not sure how I can tell if my bug is because of memcgs so here is > a full first oom example (attached). 4.7 kernel doesn't contain 71c799f4982d ("mm: add per-zone lru list stat") so the OOM report will not tell us whether the Normal zone doesn't age active lists, unfortunatelly. You can easily check whether this is memcg related by trying to run the same workload with cgroup_disable=memory kernel command line parameter. This will put all the memcg specifics out of the way. -- Michal Hocko SUSE Labs