From: Mikael Pettersson <mikpelinux@gmail.com>
To: Mikael Pettersson <mikpelinux@gmail.com>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs
Date: Sat, 7 Jun 2014 15:22:55 +0200 [thread overview]
Message-ID: <21395.4655.114256.170707@gargle.gargle.HOWL> (raw)
In-Reply-To: <21393.48632.521704.579850@gargle.gargle.HOWL>
Mikael Pettersson writes:
> Geert Uytterhoeven writes:
> > Hi Mikael,
> >
> > On Fri, Jun 6, 2014 at 1:38 PM, Mikael Pettersson <mikpelinux@gmail.com> wrote:
> > > Since updating my ARAnym VMs from 3.12.16 to 3.13.11 I see kswapd0
> > > and ksoftirqd/0 consume inordinate amounts of CPU. kswapd0 often
> > > rises to about 30-50% CPU even though RAM shouldn't be anywhere near
> > > depleted (768GB, a gcc bootstrap running in a screen session).
> > > kswapd0 tends to stay this way until I drop caches, but doing that
> > > doesn't always fix it. I also sometimes see ksoftirqd/0 consume
> > > 5-30% CPU.
> > >
> > > Reverting to 3.12.16 completely eliminates these problems.
> >
> > Any chance to bisect it?
> >
> > > I haven't tested 3.14 or 3.15-rc yet.
> >
> > Would be good to know, though, as it may have been fixed.
> > However, as v3.13.11 is the most recent stable version of v3.13, this may be
> > an elsewhere unknown and thus unfixed issue.
>
> I've just started a gcc-4.8 bootstrap on 3.14.5, and then I'll try 3.15
> if it isn't fixed in 3.14.
3.14.5 is also affected by the bug. Dropping caches fixed kswapd0, but
instead ksoftirqd/0 jumped to 20-40%, and it refuses to calm down.
next prev parent reply other threads:[~2014-06-07 13:23 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 11:38 [3.13 regression] kswapd0 and ksoftirqd/0 CPU hogs Mikael Pettersson
2014-06-06 11:43 ` Geert Uytterhoeven
2014-06-06 13:11 ` Mikael Pettersson
2014-06-07 13:22 ` Mikael Pettersson [this message]
2014-06-11 8:20 ` Mikael Pettersson
2014-06-11 8:45 ` Andreas Schwab
2014-07-01 11:43 ` Mikael Pettersson
2015-03-31 1:16 ` Michael Schmitz
2015-03-31 13:19 ` Mikael Pettersson
2015-04-01 3:08 ` Michael Schmitz
2015-04-01 4:45 ` Finn Thain
2015-04-01 5:21 ` Michael Schmitz
2015-04-06 21:25 ` Michael Schmitz
2015-04-07 0:06 ` Finn Thain
2015-04-07 5:38 ` Michael Schmitz
2016-02-21 17:06 ` Mikael Pettersson
2016-02-21 19:31 ` Michael Schmitz
2016-02-22 10:01 ` Geert Uytterhoeven
2016-03-06 7:21 ` Mikael Pettersson
2016-03-06 8:54 ` Geert Uytterhoeven
2016-03-06 9:20 ` Mikael Pettersson
2016-04-13 18:57 ` Mikael Pettersson
2016-05-31 4:52 ` Finn Thain
2016-05-31 10:06 ` Mikael Pettersson
2016-05-31 10:21 ` Geert Uytterhoeven
2016-05-31 10:39 ` John Paul Adrian Glaubitz
2016-05-31 10:41 ` Geert Uytterhoeven
2016-06-01 6:36 ` Mikael Pettersson
2015-04-01 16:11 ` Andreas Schwab
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=21395.4655.114256.170707@gargle.gargle.HOWL \
--to=mikpelinux@gmail.com \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox