From owner-freebsd-current@freebsd.org  Thu Aug 16 09:59:12 2018
Return-Path: <owner-freebsd-current@freebsd.org>
Delivered-To: freebsd-current@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id DB7931084825
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Thu, 16 Aug 2018 09:59:12 +0000 (UTC)
 (envelope-from danfe@freebsd.org)
Received: from freefall.freebsd.org (freefall.freebsd.org
 [IPv6:2610:1c1:1:6074::16:84])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client CN "freefall.freebsd.org",
 Issuer "Let's Encrypt Authority X3" (verified OK))
 by mx1.freebsd.org (Postfix) with ESMTPS id 940AD79697;
 Thu, 16 Aug 2018 09:59:12 +0000 (UTC)
 (envelope-from danfe@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1033)
 id 86BB41B863; Thu, 16 Aug 2018 09:59:12 +0000 (UTC)
Date: Thu, 16 Aug 2018 09:59:12 +0000
From: Alexey Dokuchaev <danfe@FreeBSD.org>
To: Mark Johnston <markj@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: <20180816095912.GA80650@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> <20180627115526.GA52468@pesky>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180627115526.GA52468@pesky>
User-Agent: Mutt/1.9.5 (2018-04-13)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 16 Aug 2018 09:59:13 -0000

On Wed, Jun 27, 2018 at 07:55:26AM -0400, Mark Johnston wrote:
> 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.

Thanks, I can confirm that r334752 fixed the out-of-memory kills for me
now that I've been running it for two weeks without a single problem.

./danfe