linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org
Cc: bugzilla-daemon@bugzilla.kernel.org, dh@kernel.usrbin.org
Subject: Re: [Bug 190191] New: kswapd0 spirals out of control
Date: Thu, 5 Jan 2017 11:42:33 -0800	[thread overview]
Message-ID: <20170105114233.b5c80f88f625815eaec70bc1@linux-foundation.org> (raw)
In-Reply-To: <bug-190191-27@https.bugzilla.kernel.org/>


(switched to email.  Please respond via emailed reply-to-all, not via the
bugzilla web interface).

On Mon, 12 Dec 2016 19:38:23 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:

> https://bugzilla.kernel.org/show_bug.cgi?id=190191
> 
>             Bug ID: 190191
>            Summary: kswapd0 spirals out of control
>            Product: Memory Management
>            Version: 2.5
>     Kernel Version: 4.8.0+
>           Hardware: i386
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: high
>           Priority: P1
>          Component: Other
>           Assignee: akpm@linux-foundation.org
>           Reporter: dh@kernel.usrbin.org
>         Regression: No

I'd say "Regression: yes".

Additional details at the link.  There's no indication which commit(s)
broke it.

> Created attachment 247481
>   --> https://bugzilla.kernel.org/attachment.cgi?id=247481&action=edit
> config for 4.7
> 
> I'm currently running 4.7.10 with no problems, but when i tried to upgrade to
> 4.8.0 (and just now, 4.9.0) i encountered a problem that makes my system
> unusable.
> 
> When running certain jobs, kswapd0 will consume more and more cpu cycles until
> `top' lists it at 100% and everything else slows to a crawl and makes the
> system almost completely unresponsive.
> 
> The main time i notice this is when running big rsync jobs between my
> computers, which i do regularly (masochistic homebrew packaging system, don't
> ask).
> 
> `free' never indicates any swap usage while this is going on; the systems have
> 4GB and 8GB of memory respectively and neither is getting filled up.
> 
> I've never seen this problem before and i've been running self-compiled kernels
> early in the 2.x days.
> 
> `echo 1 > /proc/sys/vm/drop_caches' works to clear the logjam, but then it just
> happens again in short order.
> 
> I'm attaching my .config for 4.7 and 4.9, in case this has something to do with
> my configuration options.
> 
> Sorry this isn't very precise, but i'm not sure how to further debug this and
> don't have a strong enough understanding of the systems involved to know what
> to provide.  If i can try anything to help pinpoint the issue, please let me
> know!
> 
> -- 
> You are receiving this mail because:
> You are the assignee for the bug.

--
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>

       reply	other threads:[~2017-01-05 19:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-190191-27@https.bugzilla.kernel.org/>
2017-01-05 19:42 ` Andrew Morton [this message]
2017-01-06 10:18   ` Michal Hocko

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=20170105114233.b5c80f88f625815eaec70bc1@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=bugzilla-daemon@bugzilla.kernel.org \
    --cc=dh@kernel.usrbin.org \
    --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