From: Andrew Morton <akpm@linux-foundation.org>
To: linux-mm@kvack.org
Cc: netwiz@crc.id.au, bugzilla-daemon@bugzilla.kernel.org
Subject: Re: [Bug 196729] New: System becomes unresponsive when swapping - Regression since 4.10.x
Date: Tue, 22 Aug 2017 15:55:30 -0700 [thread overview]
Message-ID: <20170822155530.928b377fa636bbea28e1d4df@linux-foundation.org> (raw)
In-Reply-To: <bug-196729-27@https.bugzilla.kernel.org/>
(switched to email. Please respond via emailed reply-to-all, not via the
bugzilla web interface).
On Tue, 22 Aug 2017 11:17:08 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=196729
>
> Bug ID: 196729
> Summary: System becomes unresponsive when swapping - Regression
> since 4.10.x
> Product: Memory Management
> Version: 2.5
> Kernel Version: 4.11.x / 4.12.x
> Hardware: All
> OS: Linux
> Tree: Mainline
> Status: NEW
> Severity: normal
> Priority: P1
> Component: Page Allocator
> Assignee: akpm@linux-foundation.org
> Reporter: netwiz@crc.id.au
> Regression: No
So it's "Regression: yes". More info at the bugzilla link.
> I have 10Gb of RAM in this system and run Fedora 26. If I launch Cities:
> Skylines with no swap space, things run well performance wise until I get an
> OOM - and it all dies - which is expected.
>
> When I turn on swap to /dev/sda2 which resides on an SSD, I get complete
> system freezes while swap is being accessed.
>
> The first swap was after loading a saved game, then launching kmail in the
> background. This caused ~500Mb to be swapped to /dev/sda2 on an SSD. The
> system froze for about 8 minutes - barely being able to move the mouse. The
> HDD LED was on constantly during the entire time.
>
> To hopefully rule out the above glibc issue, I started the game via jemalloc -
> but experienced even more severe freezes while swapping. I gave up waiting
> after 13 minutes of non-responsiveness - not even being able to move the mouse
> properly.
>
> During these hangs, I could typed into a Konsole window, and some of the
> typing took 3+ minutes to display on the screen (yay for buffers?).
>
> I have tested this with both the default vm.swappiness values, as well as the
> following:
> vm.swappiness = 1
> vm.min_free_kbytes = 32768
> vm.vfs_cache_pressure = 60
>
> I noticed that when I do eventually get screen updates, all 8 cpus (4 cores /
> 2 threads) show 100% CPU usage - and kswapd is right up there in the process
> list for CPU usage. Sadly I haven't been able to capture this information
> fully yet due to said unresponsiveness.
>
> (more to come in comments & attachments)
>
> --
> 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>
next parent reply other threads:[~2017-08-22 22:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-196729-27@https.bugzilla.kernel.org/>
2017-08-22 22:55 ` Andrew Morton [this message]
2017-08-23 13:38 ` Michal Hocko
2017-08-23 14:30 ` Steven Haigh
2017-08-24 12:41 ` Michal Hocko
2017-08-24 14:19 ` Steven Haigh
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=20170822155530.928b377fa636bbea28e1d4df@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=netwiz@crc.id.au \
/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