Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932481AbdCGO14 (ORCPT ); Tue, 7 Mar 2017 09:27:56 -0500 Received: from mx2.suse.de ([195.135.220.15]:60520 "EHLO mx2.suse.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754946AbdCGO1J (ORCPT ); Tue, 7 Mar 2017 09:27:09 -0500 Date: Tue, 7 Mar 2017 15:14:17 +0100 From: Michal Hocko To: MegaBrutal Cc: Stable tree , LKML , linux-mm@kvack.org, Andrew Morton , Linus Torvalds , Hillf Danton , Johannes Weiner , Mel Gorman , Minchan Kim , Trevor Cordes Subject: Re: [PATCH stable-4.9 2/2] mm, vmscan: consider eligible zones in get_scan_count Message-ID: <20170307141417.GK28642@dhcp22.suse.cz> References: <20170228151108.20853-1-mhocko@kernel.org> <20170228151108.20853-3-mhocko@kernel.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1103 Lines: 29 On Mon 06-03-17 19:00:00, MegaBrutal wrote: > Hi Michal, > > I'm over a very long kernel bisection, and if I made no mistake in > testing commits, this patch fixes a kernel bug which affects my HP > Compaq dc5800 machine with 32 bit Ubuntu OS. > > The bug manifests itself with "NMI watchdog: BUG: soft lockup - CPU#0 > stuck for 23s! [kswapd0:38]" messages in 4.8 kernels, and "page > allocation stalls for 47608ms, order:1, > mode:0x17000c0(GFP_KERNEL_ACCOUNT|__GFP_NOTRACK)" in 4.10 kernels up > to this commit. This is really hard to say without seeing the traces. > Michal, can you confirm that this patch may fix issues like the ones I > encountered? If so, I'll try to get the Ubuntu kernel staff to > backport this commit to Yakkety's 4.8 kernel. On the other hand, I > can't seem to be able to backport this commit to 4.8 with "git > cherry-pick", so maybe I need to wait for your tweaks you mentioned. The backport from 4.9 to 4.8 shouldn't be very complicated I believe. > Anyway, thank you very much for the fix! Good to hear the patch helped you though. -- Michal Hocko SUSE Labs