(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@xxxxxxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxxxxxxx > Reporter: dh@xxxxxxxxxxxxxxxxx > 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@xxxxxxxxx. For more info on Linux MM, see: http://www.linux-mm.org/ . Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>