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 <lukasz.odzi...@intel.com> > >> 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 )
