[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

** Tags added: cscc -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title: System frequently becomes completely unresponsive due to thrashing To manage notifications about this bug go to:

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

I have issue and my root partition is ext4. `mount` is full of other crap I don't understand but I don't think any of it's "real" drives. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title:

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

I am using btrfs for both / and /home. I was originally using it only for /home (and ext4 on /); but force-resetting due to this bug would occasionally render my system unbootable. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Just out of curiosity, who's is using btrfs. It doesn't matter whether you have /home or / on btrfs. I am not certain whether it plays any role, but it seems to be the common denominator in my tests. -- You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Solved on my system: On lower spec systems (4GB RAM) the default swap file in /dev/dm-1 of 1GB is insufficient. Addition of new swap file has resolved the stated issues. Filename Type Size Used Priority /swapfile file 4194300 2828 -2 /dev/dm-1 partition 999420 0 -3

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

I am having the exact same problem Bionic 18.04 x64 system kernel 4.15.0-34-generic . I have just had too hard reboot the system to regain control after waiting a hour of thrashing. All input devices are locked. As my system has too remain up all day this issue needs to be resolved to avoid HDD

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Seems to be related to https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1748408 Memory management issues since a commit on a kernel revision somewhere for 4.11 or 4.12. I'm sticking to 4.10.0-28 until resolved -- You received this bug notification because you are a member of Ubuntu Bugs,

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

I tried 4.15 rc9 from http://kernel.ubuntu.com/~kernel- ppa/mainline/v4.15-rc9/ but it still has the problem (I just waited 15 minutes before the magic sysrq sequence but I think that's enough ). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Since this bug appeared when I upgraded from zesty to artful, I reverted to 4.10.0-37 (the last kernel I had in zesty) and it had been rock-solid (it becomes unresponsive from time to time but it recovers in a few seconds). With each kernel upgrade I try the new one but the problem is still

Re: [Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

> On 3 Nov 2017, at 12:40 PM, jeremy-list wrote: > > I have tried a few different swappiness values. > 60: The problem will happen about three times per day > 10: The problem will happen about once per hour > 90: The problem will happen about once per day. 4 GBs Ram is

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

I have tried a few different swappiness values. 60: The problem will happen about three times per day 10: The problem will happen about once per hour 90: The problem will happen about once per day. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Once it has happened there is no way to check RAM usage because keyboard, mouse, and network devices all become completely unresponsive. I have 3.8 GiB of RAM installed. On the occasions when I have checked RAM usage shortly before it happened: total RAM usage was 3.8GiB. I have 19.1GiB of swap

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

What's your swappiness value? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title: System frequently becomes completely unresponsive due to thrashing To manage notifications about this bug

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

How much ram does Firefox use when this happens? -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title: System frequently becomes completely unresponsive due to thrashing To manage

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Any chance of progress being made on this bug? It's become quite rare for me to get a full day of system uptime! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1722778 Title: System frequently

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

My computer cannot boot the v4.14-rc4 kernel because the amd64 package is a failed build and my motherboard does not support 32 bit operating systems. Running the v4.14rc3 mainline kernel I was unable to connect to the internet, (so could not get firefox to use enough memory to reproduce the

[Bug 1722778] Re: System frequently becomes completely unresponsive due to thrashing

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.14 kernel[0]. If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'. If the mainline kernel does not fix