[Kernel-packages] [Bug 1833281]

2020-01-07 Thread m.novosyolov
(In reply to ValdikSS from comment #60) > I'm not sure, but people on Rosa forum blamed BTRFS for this bug. I'm pretty > sure it's not directly tight with BTRFS, but write and read amplification > may explain why lags are more severe with this FS. People here and on ROSA forum blamed BTRFS for

[Kernel-packages] [Bug 1833281]

2019-12-27 Thread m.novosyolov
(In reply to ValdikSS from comment #58) > I have an idea why this bug is much worse with BTRFS than with EXT4: BTRFS > has much bigger read/write amplification, up to 10x higher than EXT4. You mean that when e.g. Chromium browser writes its cache, it loads IO "up to 10x higher than EXT4", and,

[Kernel-packages] [Bug 1833281]

2019-09-13 Thread m.novosyolov
(In reply to ValdikSS from comment #53) > Recently, about since kernel 5.2.7, the issue is either gone or present to > much less extent. > Right now I'm running kernel 5.2.11 and finally I can keel Firefox and > VirtualBox running at the same time, with 3G+ in swap, and the system does > not

[Kernel-packages] [Bug 1833281]

2019-09-13 Thread m.novosyolov
(In reply to howaboutsynergy from comment #55) > On an unrelated note(but since btrfs was thought to be a problem at some > point), I've discovered that btrfs with zstd:5 (or worse zstd:15) can cause > (at least) mouse cursor stuttering(like it was skipping frames), while > zstd:1 doesn't(likely

[Kernel-packages] [Bug 1833281]

2019-09-13 Thread m.novosyolov
(In reply to Mikhail Novosyolov from comment #54) > > So, something was fixed in upstream, backported to LTS kernel 4.19 and to > Ubuntu kernel. I don't know what. And that issue is 100% not in BTRFS but is > another problem or another aspect of the problem. > I can suspect commit

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
Forgot to write, that if I ran $ stress --vm 2 --vm-bytes 1000M --vm-keep swap is eventually used normally -- 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/1833281 Title: System freeze

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
(In reply to ValdikSS from comment #36) > Those who experience the issue, try to set the following sysctl settings: > > vm.swappiness=100 > vm.watermark_scale_factor=200 > > It greatly helps on my PC. It did not change anything. Still only around ~15 MB are swapped while 3.5 out of 4 GB of RAM

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
Created attachment 284677 log of read_vmstat when filling RAM with new tabs in Chromium (In reply to Michal Hocko from comment #8) > Created attachment 258067 [details] > read_vmstat.c > > On Tue 22-08-17 15:55:30, Andrew Morton wrote: > > > > (switched to email. Please respond via emailed

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
Did anybody try to reproduce it in a virtual environment? It would allow to bibisect the kernel automatically. -- 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/1833281 Title: System

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
(In reply to Jim Rees from comment #47) > This bug is being discussed on lkml: > https://lkml.org/lkml/2019/8/4/15 > > I'm not going to participate there, but someone should point them to this > bug and point out that everything worked fine until 4.10. Sometimes things > that used to work and

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
I encountered the same or a similar bug on BTRFS + HDD 5400 RPM + swap on a separate partition. Unfortunately, that notebook is not mine and is far away from me, what makes it hard to make experiments, kernels 4.15 and 4.18 both did have this problem, which can be reliably reproduced by running #

[Kernel-packages] [Bug 1833281]

2019-09-02 Thread m.novosyolov
Did anyone try to reproduce it on (open)SUSE, especially with their LTS kernel 4.12? SUSE uses BTRFS by default and develops it, there is a chance that they might have caught and fixed or worked around this problem or maybe their default sheduler/kernel options/etc prevent this. -- You