From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752503AbcGTGp6 (ORCPT ); Wed, 20 Jul 2016 02:45:58 -0400 Received: from mail-wm0-f49.google.com ([74.125.82.49]:38810 "EHLO mail-wm0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752128AbcGTGp4 convert rfc822-to-8bit (ORCPT ); Wed, 20 Jul 2016 02:45:56 -0400 From: Arkadiusz Miskiewicz Reply-To: arekm@maven.pl Organization: Do not reply to gmail address. Write to arekm@maven.pl instead. To: linux-kernel@vger.kernel.org Subject: Re: Linux 4.1.28 Date: Wed, 20 Jul 2016 08:45:52 +0200 User-Agent: KMail/1.13.7 (Linux/4.7.0-rc7-00092-g47ef4ad; KDE/4.14.21; x86_64; ; ) Cc: Thomas Voegtle , Sasha Levin , stable , lwn@lwn.net References: <5786F7BC.9090406@oracle.com> <5788CEF1.8010900@oracle.com> In-Reply-To: MIME-Version: 1.0 Content-Type: Text/Plain; charset="utf-8" Content-Transfer-Encoding: 8BIT Message-Id: <201607200845.52577.a.miskiewicz@gmail.com> Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Friday 15 of July 2016, Thomas Voegtle wrote: > On Fri, 15 Jul 2016, Sasha Levin wrote: > > On 07/15/2016 07:38 AM, Thomas Voegtle wrote: > >> On Wed, 13 Jul 2016, Sasha Levin wrote: > >>> I'm announcing the release of the 4.1.28 kernel. > >> > >> I have a serious memleak with 4.1.28 (like 20mb/s) > >> I stripped down my kernel config and started a bisect, which came to: > >> > >> # first bad commit: [c5ad33184354260be6d05de57e46a5498692f6d6] > >> mm/swap.c: flush lru pvecs on compound page arrival > >> => > >> commit c5ad33184354260be6d05de57e46a5498692f6d6 > >> Author: Lukasz Odzioba > >> Date: Fri Jun 24 14:50:01 2016 -0700 > >> > >> mm/swap.c: flush lru pvecs on compound page arrival > >> > >> Reverting this on top 4.1.28 helps. Config attached. > > > > Yup, this was reported and a fix is already queued for 4.1.29. > > And that one? > Happens while trying to start a firewall script with iptables-restore. > > > [ 180.071999] NMI watchdog: BUG: soft lockup - CPU#1 stuck for 22s! > [iptables-restor:2338] Same here but I don't have actuall trace Applying iptables firewall rules...................................[ 42.297704] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 22s! [iptables- restor:900] [ 70.287999] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 22s! [iptables-restor:900] [ 102.276912] NMI watchdog: BUG: soft lockup - CPU#7 stuck for 23s! [iptables-restor:900] -- Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )