From owner-freebsd-current@freebsd.org Fri Jun 15 09:07:34 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 A8BBA100D178 for ; Fri, 15 Jun 2018 09:07:34 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from home.opsec.eu (home.opsec.eu [IPv6:2001:14f8:200::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 39FDE82394; Fri, 15 Jun 2018 09:07:34 +0000 (UTC) (envelope-from lists@opsec.eu) Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD)) (envelope-from ) id 1fTkhi-000EK5-Cu; Fri, 15 Jun 2018 11:07:34 +0200 Date: Fri, 15 Jun 2018 11:07:34 +0200 From: Kurt Jaeger To: Mark Johnston Cc: FreeBSD current Subject: Re: swapping is completely broken in -CURRENT r334649? Message-ID: <20180615090734.GG4028@home.opsec.eu> References: <20180605181716.73b8ea91@ernst.home> <2925b27f-43cf-8813-eaa7-4f3d12bef8f0@FreeBSD.org> <20180605214808.GA94301@pesky> <20180615051025.GA79327@ns.kevlo.org> <20180615084022.GA32922@pesky.lan> <20180615084808.GF4028@home.opsec.eu> <20180615090358.GB32922@pesky.lan> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20180615090358.GB32922@pesky.lan> 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 09:07:34 -0000 Hi! > > > The change was committed as r334752. Are you seeing unexpected OOM > > > kills on or after that revision? > > > > When I tried to run a qemu-based poudriere run yesterday on a r334918 > > box, it killed a few processes outside of that run and did not > > work out. > > > > I'm unsure it was because of that problem or a problem with qemu. > > How much memory and swap does the guest have? It's started by poudriere, I do not really know. > Were you consistently able to complete a run before? Two years ago, on a much lower version of FreeBSD, yes. I just started it again, and after a while the qemu-ppc64-static was at approx. 23 GB memory and increasing, without much progress. > If it's happening during a poudriere run, it may well have been a true > OOM situation. The patch below prints a few stats to the dmesg before > the kill. The output of that together with "sysctl vm" output should be > enough to determine what's happening. > > diff --git a/sys/vm/vm_pageout.c b/sys/vm/vm_pageout.c > index 264c98203c51..9c7ebcf451ec 100644 > --- a/sys/vm/vm_pageout.c > +++ b/sys/vm/vm_pageout.c > @@ -1670,6 +1670,8 @@ vm_pageout_mightbe_oom(struct vm_domain *vmd, int page_shortage, > * start OOM. Initiate the selection and signaling of the > * victim. > */ > + printf("v_free_count: %u, v_inactive_count: %u\n", > + vmd->vmd_free_count, vmd->vmd_pagequeues[PQ_INACTIVE].pq_cnt); > vm_pageout_oom(VM_OOM_MEM); > > /* I'll have a look at this. -- pi@opsec.eu +49 171 3101372 2 years to go !