Launchpad has imported 4 comments from the remote bug at https://bugzilla.redhat.com/show_bug.cgi?id=1472336.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2017-07-18T13:24:02+00:00 Steven wrote: 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. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/61 ------------------------------------------------------------------------ On 2017-07-18T13:25:32+00:00 Steven wrote: Forgot to add kernel version! Currently testing with: kernel-4.11.10-300.fc26.x86_64 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/62 ------------------------------------------------------------------------ On 2017-10-20T17:07:52+00:00 Jan wrote: Related bug reports: https://bugzilla.redhat.com/show_bug.cgi?id=1357032 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356 Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/65 ------------------------------------------------------------------------ On 2018-02-28T03:52:10+00:00 Laura wrote: We apologize for the inconvenience. There is a large number of bugs to go through and several of them have gone stale. The kernel moves very fast so bugs may get fixed as part of a kernel update. Due to this, we are doing a mass bug update across all of the Fedora 26 kernel bugs. Fedora 26 has now been rebased to 4.15.4-200.fc26. Please test this kernel update (or newer) and let us know if you issue has been resolved or if it is still present with the newer kernel. If you have moved on to Fedora 27, and are still experiencing this issue, please change the version to Fedora 27. If you experience different issues, please open a new bug report for those. Reply at: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/comments/71 ** Changed in: fedora Status: Unknown => Confirmed ** Changed in: fedora Importance: Unknown => Medium ** Bug watch added: Red Hat Bugzilla #1357032 https://bugzilla.redhat.com/show_bug.cgi?id=1357032 -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to linux in Ubuntu. https://bugs.launchpad.net/bugs/159356 Title: System freeze on high memory usage Status in linux package in Ubuntu: Confirmed Status in linux package in Arch Linux: New Status in Fedora: Confirmed Bug description: I run a batch matlab job server here at my lab, running Dapper 6.06 (for the LTS). One of the users has submitted a very memory-consuming job, which successfully crashes the server. Upon closer inspection, the crash happens like this: 1. I run matlab with the given file (as an ordinary, unpriveleged user) 2. RAM usage quickly fills up 3. Once the RAM meter hits 100%, the system freezes: All SSH connections freeze up, and while switching VTs directly on the machine works, no new processes run - so one can't log in, or do anything if he is logged in. (Sometimes typing doesn't work at all) Note that the swap - while 7 gigs of it are available - is never used. (The machine has 7 gigs of RAM as well) I've tried the same on my Gutsy 32-bit box, and there was no system freezeup - matlab simply notified that the system was out of memory. However, it did this once memory was 100% in use - and still, swap didn't get used at all! (Though it is mounted correctly and shows up in "top" and "free"). So first thing's first - I'd like to eliminate the crash issue. I suppose I could switch the server to 32-bit, but I think that would be a performance loss, considering that it does a lot of heavy computation. There is no reason, however, that this should happen on a 64-bit machine anyway. Why does it? WORKAROUND: Enabling DMA in the BIOS To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/159356/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp
