From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: Arthur Marsh <arthur.marsh@internode.on.net>
Cc: linux-mm@kvack.org
Subject: Re: 8 Gigabytes and constantly swapping
Date: Fri, 12 May 2017 19:56:31 +0900 [thread overview]
Message-ID: <64c96dd6-651c-eee8-2a30-65e60988d7d8@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <171e8fa1-3f14-dc18-09b5-48399b250a30@internode.on.net>
On 2017/05/12 17:51, 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.
Did the /bin/top process continue showing up-to-dated statistics rather than
refrain from showing up-to-dated statistics? (I wonder why you had to hit
the power switch before trying SysRq-m/SysRq-f etc.)
If yes, assuming that reading statistics involves memory allocation requests,
there was no load at at all despite firefox and chromium were running?
If no, all allocation requests got stuck waiting for memory reclaim?
>
> 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.
I don't know but http://lkml.kernel.org/r/20170316100409.GR802@shells.gnugeneration.com
or http://lkml.kernel.org/r/20170502041235.zqmywvj5tiiom3jk@merlins.org ?
More description of what happened and how you confirmed that
the /bin/top process continued working would be helpful.
--
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-12 10:56 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 [this message]
2017-05-12 13:39 ` Arthur Marsh
2017-05-13 4:15 ` Arthur Marsh
2017-05-15 8:09 ` Michal Hocko
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=64c96dd6-651c-eee8-2a30-65e60988d7d8@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--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