From owner-freebsd-current@freebsd.org Wed Jun 27 11:56:38 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 DD534101F0BB for ; Wed, 27 Jun 2018 11:56:37 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) (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 583A779A78; Wed, 27 Jun 2018 11:56:37 +0000 (UTC) (envelope-from markjdb@gmail.com) Received: by mail-ed1-x544.google.com with SMTP id b12-v6so2915510edt.8; Wed, 27 Jun 2018 04:56:37 -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=i6CaoBhIG2TFxY/UHvJEQl5eT53cmPttmw/fPDjlqKE=; b=hB8Ctzk8t67tI+/K9ChJcN5csMjqmQ/rqsVtayjLAW9fW9r0Uf/FsSZGJWoDHQOxJO OoNKz9Op0KoRj9u+dXdJeg/ZTFhlnuAE6yvsypyRbXoxfASkiORJhVINVTeipPP6j+yq LFcR7Enc5r8WSXGrTcwnd7XuQ1J08pZqvXuyGVx0gtYsYwo/Hwm7n/IiCiEsaTruai6j LP5cDgMhvqfCfiiHMwQOXo5eDXTZLaI80hcpFXgEKHxH0EAuitGJuhV8S7d0WOfHY/Hx qK3/JzEjBcS2yL2HCVjCQK2Qg7qEOxS1G6OMQFu1TZ/hZJicCAR+jwCRkW0jQYzE9WtR NyGA== 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=i6CaoBhIG2TFxY/UHvJEQl5eT53cmPttmw/fPDjlqKE=; b=iHcgwckEp+9CQsw39HdSwEsFAF7HENpYMTyVFgssYg3Ou9rg/d6QjjKdbgWncg+pL0 vEJTW/xuYwyXjrta67w7DcVAIn1UgbPShRau1maMpgqzIj5c2QNBuijoCGV5EcAFpUE2 hXC7WEYKizpe5/zsWBY4APtDH+X9eVnzOlMdzJRJODQuZIHUpEHUg03+mdcQugdjDLh3 WHudZGidm4D3iqDH0XJBgWQ1UDI+l/9H03llJ/o3cj4H/a9cZ5P8RaR5CPhPA3XUQcYK a9E484Hz8ZLMihmQeZDoGZABqG9c57QyrlYBoKQZdgdeJX/NYGZGkc7xhnA+uEIzhdm+ ZMAA== X-Gm-Message-State: APt69E2KT3Usoxrh0Oirj9Twlgm0qVBAbFMjoJcPK1ngy4ts1nOaIeVW Vx5hXq7z07i/fu3qhjBvx7difA== X-Google-Smtp-Source: AAOMgpd3a4S3Kq722uFDmL2SEo0/ZXhULrSQUoLbLxB1D89rUDkBo9IlM+Fw1hoFkhl2MEAUKHP2xw== X-Received: by 2002:aa7:d84a:: with SMTP id f10-v6mr5459623eds.157.1530100596213; Wed, 27 Jun 2018 04:56:36 -0700 (PDT) Received: from pesky (dhcp-077-251-153-140.chello.nl. [77.251.153.140]) by smtp.gmail.com with ESMTPSA id h16-v6sm1651563ede.66.2018.06.27.04.56.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 27 Jun 2018 04:56:35 -0700 (PDT) Sender: Mark Johnston Date: Wed, 27 Jun 2018 07:55:26 -0400 From: Mark Johnston To: Alexey Dokuchaev Cc: Kevin Lo , Lev Serebryakov , gljennjohn@gmail.com, FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180627115526.GA52468@pesky> References: <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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180627104638.GA15311@FreeBSD.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: Wed, 27 Jun 2018 11:56:38 -0000 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.