Messages in this thread |  | | From | Filipe Manana <> | | Date | Sun, 11 Aug 2024 16:33:54 +0100 | | Subject | Re: 6.10/regression/bisected - after f1d97e769152 I spotted increased execution time of the kswapd0 process and symptoms as if there is not enough memory |
| |
On Sun, Aug 11, 2024 at 9:08 AM Jannik Glückert <jannik.glueckert@gmail.com> wrote: > > Hello, > > I am still encountering this issue on 6.10.3. As far as I can see this > is the last post in the thread, if the discussion continued elsewhere > please let me know. > > My workload is a backup via restic, the system is idle otherwise. > This is on a Zen4 CPU with a very fast PCIe Gen4 nvme, so perhaps it was > fixed for others because they had comparatively slow IO or a smaller > workload? > > I have attached the bpftrace run and a graph of the memory PSI. kswapd0 > is at 100% during the critical sections. dmesg is empty. > Important events were e.g. 09:31-09:32 and 09:33-09:34 where the system > was completely unresponsive multiple times, for about 5 seconds at a time. > > I did also mention this on the #btrfs IRC channel and there are other > users still encountering this on 6.10
This came to my attention a couple days ago in a bugzilla report here:
https://bugzilla.kernel.org/show_bug.cgi?id=219121
There's also 2 other recent threads in the mailing about it.
There's a fix there in the bugzilla, and I've just sent it to the mailing list. In case you want to try it:
https://lore.kernel.org/linux-btrfs/d85d72b968a1f7b8538c581eeb8f5baa973dfc95.1723377230.git.fdmanana@suse.com/
Thanks.
> > Best > Jannik
|  |