From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755459AbcLZM07 (ORCPT ); Mon, 26 Dec 2016 07:26:59 -0500 Received: from mx2.suse.de ([195.135.220.15]:47491 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752138AbcLZM06 (ORCPT ); Mon, 26 Dec 2016 07:26:58 -0500 Date: Mon, 26 Dec 2016 13:26:51 +0100 From: Michal Hocko To: kernel test robot Cc: Nils Holland , Mel Gorman , Johannes Weiner , Vladimir Davydov , Tetsuo Handa , linux-kernel@vger.kernel.org, linux-mm@kvack.org, Chris Mason , David Sterba , linux-btrfs@vger.kernel.org, lkp@01.org Subject: Re: [lkp-developer] [mm, memcg] d18e2b2aca: WARNING:at_mm/memcontrol.c:#mem_cgroup_update_lru_size Message-ID: <20161226122651.GA20715@dhcp22.suse.cz> References: <20161223144738.GB23117@dhcp22.suse.cz> <20161225222556.GH19366@yexl-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20161225222556.GH19366@yexl-desktop> 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 Mon 26-12-16 06:25:56, kernel test robot wrote: > > FYI, we noticed the following commit: > > commit: d18e2b2aca0396849f588241e134787a829c707d ("mm, memcg: fix (Re: OOM: Better, but still there on)") > url: https://github.com/0day-ci/linux/commits/Michal-Hocko/mm-memcg-fix-Re-OOM-Better-but-still-there-on/20161223-225057 > base: git://git.cmpxchg.org/linux-mmotm.git master > > in testcase: boot > > on test machine: qemu-system-i386 -enable-kvm -m 360M > > caused below changes: > > > +--------------------------------------------------------+------------+------------+ > | | c7d85b880b | d18e2b2aca | > +--------------------------------------------------------+------------+------------+ > | boot_successes | 8 | 0 | > | boot_failures | 0 | 2 | > | WARNING:at_mm/memcontrol.c:#mem_cgroup_update_lru_size | 0 | 2 | > | kernel_BUG_at_mm/memcontrol.c | 0 | 2 | > | invalid_opcode:#[##]DEBUG_PAGEALLOC | 0 | 2 | > | Kernel_panic-not_syncing:Fatal_exception | 0 | 2 | > +--------------------------------------------------------+------------+------------+ > > > > [ 95.226364] init: tty6 main process (990) killed by TERM signal > [ 95.314020] init: plymouth-upstart-bridge main process (1039) terminated with status 1 > [ 97.588568] ------------[ cut here ]------------ > [ 97.594364] WARNING: CPU: 0 PID: 1055 at mm/memcontrol.c:1032 mem_cgroup_update_lru_size+0xdd/0x12b > [ 97.606654] mem_cgroup_update_lru_size(40297f00, 0, -1): lru_size 1 but empty > [ 97.615140] Modules linked in: > [ 97.618834] CPU: 0 PID: 1055 Comm: killall5 Not tainted 4.9.0-mm1-00095-gd18e2b2 #82 > [ 97.628008] Call Trace: > [ 97.631025] dump_stack+0x16/0x18 > [ 97.635107] __warn+0xaf/0xc6 > [ 97.638729] ? mem_cgroup_update_lru_size+0xdd/0x12b Do you have the full backtrace? -- Michal Hocko SUSE Labs