mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Steven Haigh <netwiz@crc.id.au>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Fedora 26 / Kernel 4.11.10 - System becomes unresponsive when swapping
Date: Tue, 22 Aug 2017 21:34:12 +1000	[thread overview]
Message-ID: <1813378.B2JPgOS4PZ@wopr.lan.crc.id.au> (raw)
In-Reply-To: <1540730.ipWl7zM1Wl@wopr.lan.crc.id.au>

[-- Attachment #1: Type: text/plain, Size: 2622 bytes --]

Hi all,

Just as a follow up - I believe I may have found a regression between kernel 
4.10.x and the newer 4.11 / 4.12 versions.

After some assistance, I have lodged this report:
	https://bugzilla.kernel.org/show_bug.cgi?id=196729

If anyone can assist with this, I'll be happy to reply / comment / test via 
the bugzilla report to hopefully bring the issue to the surface.


On Tuesday, 18 July 2017 9:10:31 AM AEST Steven Haigh wrote:
> Hi all,
> 
> Firstly, please CC me directly in replies due to not being subscribed.
> 
> After a fix to glibc that fixed Unity 3D based games (Fedora ref: https://
> bugzilla.redhat.com/show_bug.cgi?id=1440287), I have noticed that when I
> play Cities: Skylines that the system becomes unresponsive when digging
> into swap.
> 
> 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.
> 
> This seems to be a relatively new problem that I did not encounter during
> the Fedora 26 beta - but do now.
> 
> Does anyone have any suggestions on where to start tracking this type of
> issue down?


-- 
Steven Haigh

📧 netwiz@crc.id.au       💻 http://www.crc.id.au
📞 +61 (3) 9001 6090    📱 0412 935 897

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

      reply	other threads:[~2017-08-22 11:40 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 23:10 Steven Haigh
2017-08-22 11:34 ` Steven Haigh [this message]

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=1813378.B2JPgOS4PZ@wopr.lan.crc.id.au \
    --to=netwiz@crc.id.au \
    --cc=linux-kernel@vger.kernel.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

all inboxes | Powered by JetHome®