From owner-freebsd-current@freebsd.org Fri Jun 15 08:40:30 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 4E194100A30B for ; Fri, 15 Jun 2018 08:40:30 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-wr0-x22d.google.com (mail-wr0-x22d.google.com [IPv6:2a00:1450:400c:c0c::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id B7EC280C0A; Fri, 15 Jun 2018 08:40:29 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-wr0-x22d.google.com with SMTP id x4-v6so9075346wro.11; Fri, 15 Jun 2018 01:40:29 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=90ZwDJDlaGcFBvMNbjPab0RSECHc+/Tnf9svlXpOpwk=; b=FudMw+3FzG+u7X1Ez4GTlYcKXqmHM8ebfc4rEmMfVSq7p5QMZ+qFTrzmXttWIke3Tk AG/8Gso0t3wnR+20PR8SJ7oO3zbWU+bl+2kZz+kzWvlgTnsm0pkCHEL62uJ5yL1M9R5t nCArn+PGgcdMMTr3+Ogjinhie7DT/TEVPZdORXhsbHioCP1JmalX6m5VYlRbPnLQhR5b whfKZri7NvtBXwIUsGCPWwAXs484yUvzUmoSj7V+yew6FVLugE3I6kkY4f764dBX/fh1 Y7gPTXXscNgSK4JgE9ts4P2CZTKDnpvEBJjAeosapmnWqEmhsaSQ49IEaJzmtCFqTTcx jUJA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:date:from:to:cc:subject:message-id :references:mime-version:content-disposition:in-reply-to:user-agent; bh=90ZwDJDlaGcFBvMNbjPab0RSECHc+/Tnf9svlXpOpwk=; b=FreeXVDZceAcrfLnwojfQuejaJPBo0qTN+Q1ijdp9CU4s1vOB3L4YYFHTKn51Ovjh/ +SPNt9ChNWlKeS1r8cxqWcZUXqViE7L1Qct5ElWCgHhd/T2iZEPcRPDetWg+XixgOag5 8pi74wPEgWLMKhbHx0H3Pm/FCw3NZNavsv6UCk+m668w6r+UrRtAGl6H+tBZ+zROwpKx s7HC3kYwj8ITF7DamYLO8yKUDdLgSqKS/9NZNzvSORLUjtnk8vT0cl/Ybd7qdNNyq89i DZoxi9+DaaWVkkIMLFg+kTkOrHNXuijU/kV+gVJmN40nLLlCy7fADcsoFusbkNW64WQR AOhg== X-Gm-Message-State: APt69E2BpI55i+h5qvHPr3YyiXj4caXqrLciGuEYqfCA5Jd3tlH7kfOH yUK7Ehbjn4evQ7NewuNo1Ua+3Q== X-Google-Smtp-Source: ADUXVKLmj2VI4XA51X0Aobf8owolxZ9r3MCKa8dADp4TK46yEXhBoKWI5o+kpXhUtjfAZEzIctxjKA== X-Received: by 2002:adf:a60c:: with SMTP id k12-v6mr814848wrc.200.1529052028494; Fri, 15 Jun 2018 01:40:28 -0700 (PDT) Received: from pesky.lan (84.32.136.95.rev.vodafone.pt. [95.136.32.84]) by smtp.gmail.com with ESMTPSA id p5-v6sm5840427wre.83.2018.06.15.01.40.26 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 15 Jun 2018 01:40:27 -0700 (PDT) Sender: Mark Johnston Date: Fri, 15 Jun 2018 04:40:22 -0400 From: Mark Johnston To: Kevin Lo Cc: Lev Serebryakov , gljennjohn@gmail.com, FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180615084022.GA32922@pesky.lan> References: <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> <20180605214808.GA94301@pesky> <20180615051025.GA79327@ns.kevlo.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180615051025.GA79327@ns.kevlo.org> User-Agent: Mutt/1.10.0 (2018-05-17) 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 08:40:30 -0000 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?