From: Michal Hocko <mhocko@kernel.org>
To: Arthur Marsh <arthur.marsh@internode.on.net>
Cc: linux-mm@kvack.org
Subject: Re: 8 Gigabytes and constantly swapping
Date: Mon, 15 May 2017 10:09:46 +0200 [thread overview]
Message-ID: <20170515080945.GA6062@dhcp22.suse.cz> (raw)
In-Reply-To: <171e8fa1-3f14-dc18-09b5-48399b250a30@internode.on.net>
On Fri 12-05-17 18:21:27, Arthur Marsh wrote:
> I've been building the Linus git head kernels as the source gets updated and
> the one built about 3 hours ago managed to get stuck with kswapd0 as the
> highest consumer of CPU cycles (but still under 1 percent) of processes
> listed by top for over 15 minutes, after which I hit the power switch and
> rebooted with a Debian 4.11.0 kernel.
>
> The previous kernel built less than 24 hours earlier did not have this
> problem.
>
> CPU is an Athlon64 (Athlon II X4, 4 cores), RAM is 8GiB, swap is 4GiB, load
> was mainly firefox and chromium. Opening a new window in chromium seemed to
> help trigger the problem.
>
> It's not much information to go on, just wondered if anyone else had
> experienced similar issues?
>
> I'm happy to supply more configuration information and run tests including
> with kernels built with test patches applied.
Is this 32b or 64b kernel? Could you take /proc/vmstat snapshots ever
second while the kswapd is active?
--
Michal Hocko
SUSE Labs
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-05-15 8:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-12 8:51 Arthur Marsh
2017-05-12 10:56 ` Tetsuo Handa
2017-05-12 13:39 ` Arthur Marsh
2017-05-13 4:15 ` Arthur Marsh
2017-05-15 8:09 ` Michal Hocko [this message]
2017-05-17 1:27 ` Arthur Marsh
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=20170515080945.GA6062@dhcp22.suse.cz \
--to=mhocko@kernel.org \
--cc=arthur.marsh@internode.on.net \
--cc=linux-mm@kvack.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