Date: Fri, 23 Jul 2021 20:20:02 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 257314] FBSD 13 crash after some KDE parts crash supposing out of swap space Message-ID: <bug-257314-227-0H7IfbSANN@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257314-227@https.bugs.freebsd.org/bugzilla/> References: <bug-257314-227@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D257314 --- Comment #22 from Mark Millard <marklmi26-fbsd@yahoo.com> --- (In reply to Michael from comment #20) > certainly it is not really kernel related because the underlying OS is wo= rking still fine No. The kills are initiated by the kernel --and only by the kernel. The OS is doing the kills for failing the conditions for allowing continued operation of all the processes. The kernel is also what reports: "swap_pager: indefinite wait buffer:" messages. I would like the patched kernel to be used in order to find out exactly --and for sure-- which condition in the kernel is failing to allow continued operation of all processes. I've no objection to combining such with an increased vm.pageout_oom_seq value assigned at boot: A) If it still does a kill, we learn from the messages what the condition was. B) If it no longer does a kill, we then know that the condition that had been failing was the test involving vm.pageout_oom_seq . --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257314-227-0H7IfbSANN>