From owner-freebsd-current@freebsd.org Fri Jun 15 13:48:32 2018 Return-Path: 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 3C6D21006679 for ; Fri, 15 Jun 2018 13:48:32 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (220-135-115-6.HINET-IP.hinet.net [220.135.115.6]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "ns.kevlo.org", Issuer "ns.kevlo.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 8236A6E1C7; Fri, 15 Jun 2018 13:48:30 +0000 (UTC) (envelope-from kevlo@ns.kevlo.org) Received: from ns.kevlo.org (localhost [127.0.0.1]) by ns.kevlo.org (8.15.2/8.15.2) with ESMTPS id w5FDkLHQ082605 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 15 Jun 2018 21:46:22 +0800 (CST) (envelope-from kevlo@ns.kevlo.org) Received: (from kevlo@localhost) by ns.kevlo.org (8.15.2/8.15.2/Submit) id w5FDkL5G082604; Fri, 15 Jun 2018 21:46:21 +0800 (CST) (envelope-from kevlo) Date: Fri, 15 Jun 2018 21:46:21 +0800 From: Kevin Lo To: Mark Johnston Cc: Lev Serebryakov , gljennjohn@gmail.com, FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180615134621.GA82592@ns.kevlo.org> References: <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.8.0 (2017-02-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 15 Jun 2018 13:48:32 -0000 On Fri, Jun 15, 2018 at 04:40:22AM -0400, Mark Johnston wrote: > > On Fri, Jun 15, 2018 at 01:10:25PM +0800, Kevin Lo wrote: > > On Tue, Jun 05, 2018 at 05:48:08PM -0400, Mark Johnston wrote: > > > > > > On Wed, Jun 06, 2018 at 12:22:08AM +0300, Lev Serebryakov wrote: > > > > On 05.06.2018 19:17, Gary Jennejohn wrote: > > > > > > > > > > > > > I complained about this also and alc@ gave me this hint: > > > > > sysctl vm.pageout_update_period=0 > > > > > > > > Really, situation is worse than stated in subject, because processes > > > > are being killed AFTER memory pressure, when here are a lot of free > > > > memory already! > > > > > > > > It looks like very serious bug. > > > > > > The issue was identified earlier this week and is being worked on. It's > > > a regression from r329882 which appears only on certain hardware. You > > > can probably work around it by setting vm.pageout_oom_seq to a large > > > value (try 1000 for instance), though this will make the "true" OOM > > > killer take longer to kick in. The problem is unrelated to the > > > pageout_update_period. > > > > I have a large swap space and I've encountered this issue as well > > > > pid 90707 (getty), uid 0, was killed: out of swap space > > pid 90709 (getty), uid 0, was killed: out of swap space > > pid 90709 (getty), uid 0, was killed: out of swap space > > ... > > > > Setting vm.pageout_oom_seq to 1000 doesn't help. If you have a patch I'll be > > happy to test it, thanks. > > The change was committed as r334752. Are you seeing unexpected OOM > kills on or after that revision? The box is running -CURRENT r334983. I'll investigate further, thanks.