From mboxrd@z Thu Jan 1 00:00:00 1970 From: Michael Schmitz Subject: Re: [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs Date: Mon, 22 Feb 2016 08:31:21 +1300 Message-ID: References: <21393.43065.207399.530921@gargle.gargle.HOWL> <21426.40682.197715.245775@gargle.gargle.HOWL> <21786.40688.53001.509365@gargle.gargle.HOWL> <22217.61083.254294.356622@gargle.gargle.HOWL> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Return-path: Received: from mail-io0-f170.google.com ([209.85.223.170]:35511 "EHLO mail-io0-f170.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751117AbcBUTbV (ORCPT ); Sun, 21 Feb 2016 14:31:21 -0500 Received: by mail-io0-f170.google.com with SMTP id g203so157391837iof.2 for ; Sun, 21 Feb 2016 11:31:21 -0800 (PST) In-Reply-To: <22217.61083.254294.356622@gargle.gargle.HOWL> Sender: linux-m68k-owner@vger.kernel.org List-Id: linux-m68k@vger.kernel.org To: Mikael Pettersson Cc: Andreas Schwab , Linux/m68k Hi Mikael, I've since changed too much around my system to be certain, but would suspect the bug to still be there. I'll see whether changing my config to use SLUB retriggers the bug when uncompressing a huge file (but I'm running with only 14 MB noe, which makes traversing the entire VM metadata a lot faster). Cheers, Michael On Mon, Feb 22, 2016 at 6:06 AM, Mikael Pettersson wrote: > Mikael Pettersson writes: > > Michael Schmitz writes: > > > Hi, > > > > > > has anyone found a solution to this one? > > > > > > 3.18-rc5 has kswapd0 hogging the CPU - haven't seen ksoftirqd0 yet. > > > Unpacking a large tarball tends to trigger this for me. > > > > Alas, no. I went back to the 3.10.xx kernels and they work Ok for me > > (they tend to hang during shutdown, but I can live with that). > > > > I should do a git bisect... > > I've done two git bisects on this. The first one was inconclusive > (pointed to a harmless commit), but the second one ended up with: > > # first bad commit: [ac4de9543aca59f2b763746647577302fbedd57e] Merge branch 'akpm' (patches from Andrew Morton) > > That's a big pile of VM changes, so I think it could be the culprit. > > Are people still seeing the kswapd bug with current kernels? I've > stayed with the 3.10 kernel series on my aranym VMs, except for the > one VM that did the bisection tests. > > /Mikael