From owner-freebsd-current@freebsd.org  Wed Jun 27 10:46:39 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 4A8C2101AA5A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 27 Jun 2018 10:46:39 +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 F37AE773F9;
 Wed, 27 Jun 2018 10:46:38 +0000 (UTC)
 (envelope-from danfe@freebsd.org)
Received: by freefall.freebsd.org (Postfix, from userid 1033)
 id E9C4B178F7; Wed, 27 Jun 2018 10:46:38 +0000 (UTC)
Date: Wed, 27 Jun 2018 10:46:38 +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: <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>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180615084022.GA32922@pesky.lan>
User-Agent: Mutt/1.9.5 (2018-04-13)
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.26
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: Wed, 27 Jun 2018 10:46:39 -0000

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,

./danfe