Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751753AbbLUVOV (ORCPT ); Mon, 21 Dec 2015 16:14:21 -0500 Received: from resqmta-po-09v.sys.comcast.net ([96.114.154.168]:37880 "EHLO resqmta-po-09v.sys.comcast.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751013AbbLUVOU (ORCPT ); Mon, 21 Dec 2015 16:14:20 -0500 Date: Mon, 21 Dec 2015 15:14:18 -0600 (CST) From: Christoph Lameter X-X-Sender: cl@east.gentwo.org To: Sasha Levin cc: Michal Hocko , LKML , "linux-mm@kvack.org" Subject: Re: mm, vmstat: kernel BUG at mm/vmstat.c:1408! In-Reply-To: <56786A22.9030103@oracle.com> Message-ID: References: <5674A5C3.1050504@oracle.com> <567860EB.4000103@oracle.com> <56786A22.9030103@oracle.com> Content-Type: text/plain; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 756 Lines: 19 On Mon, 21 Dec 2015, Sasha Levin wrote: > I've also noticed a new warning from the workqueue code which my scripts > didn't pick up before: > > [ 3462.380681] BUG: workqueue lockup - pool cpus=2 node=2 flags=0x4 nice=0 stuck for 54s! > [ 3462.522041] workqueue vmstat: flags=0xc > [ 3462.527795] pwq 4: cpus=2 node=2 flags=0x0 nice=0 active=1/256 > [ 3462.554836] pending: vmstat_update Does that mean that vmstat_update locks up or something that schedules it? Also what workload triggers the BUG()? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/