Date: Wed, 27 Jun 2018 07:55:26 -0400 From: Mark Johnston <markj@freebsd.org> To: Alexey Dokuchaev <danfe@freebsd.org> Cc: Kevin Lo <kevlo@freebsd.org>, Lev Serebryakov <lev@freebsd.org>, gljennjohn@gmail.com, FreeBSD current <freebsd-current@freebsd.org> Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180627115526.GA52468@pesky> In-Reply-To: <20180627104638.GA15311@FreeBSD.org> References: <d3ee2b8f-bdbe-ce25-f496-6267f9bb0212@FreeBSD.org> <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> <20180605214808.GA94301@pesky> <20180615051025.GA79327@ns.kevlo.org> <20180615084022.GA32922@pesky.lan> <20180627104638.GA15311@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
On Wed, Jun 27, 2018 at 10:46:38AM +0000, Alexey Dokuchaev wrote: > On Fri, Jun 15, 2018 at 04:40:22AM -0400, Mark Johnston wrote: > > ... > > The change was committed as r334752. Are you seeing unexpected OOM > > kills on or after that revision? > > I've just discovered this thread. I've updated my -CURRENT desktop ca. > June 4th and my X.org session crashes within several minutes. This is > on i386 system with 4G RAM. > > I cannot get SVN revision of that kernel because something got broken > and it was not embedded in the image. :-( > > Rebooting with kernel="kernel.old" from May 12th made this problem go > away. Is the root cause is known at this time? Which revision shall > I try to see whether it does not exhibit this bug any longer? Thanks, As noted earlier in the thread, r329882 introduced a problem where out-of-memory kills were taking place despite an abundance of free pages and swap space. That bug was fixed in r334752. If you are seeing a problem that is fixed in a kernel from May 12th, then it is possibly unrelated to this bug, but it is worth testing r334752 or later to confirm.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20180627115526.GA52468>