From owner-freebsd-arm@freebsd.org Mon Jun 4 07:54:06 2018 Return-Path: Delivered-To: freebsd-arm@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 5A772FE19E3 for ; Mon, 4 Jun 2018 07:54:06 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (www.zefox.net [50.1.20.27]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "www.zefox.org", Issuer "www.zefox.org" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id CB49978B63 for ; Mon, 4 Jun 2018 07:54:05 +0000 (UTC) (envelope-from fbsd@www.zefox.net) Received: from www.zefox.net (localhost [127.0.0.1]) by www.zefox.net (8.15.2/8.15.2) with ESMTPS id w547sAtN077072 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Mon, 4 Jun 2018 00:54:11 -0700 (PDT) (envelope-from fbsd@www.zefox.net) Received: (from fbsd@localhost) by www.zefox.net (8.15.2/8.15.2/Submit) id w547s9ZH077071; Mon, 4 Jun 2018 00:54:09 -0700 (PDT) (envelope-from fbsd) Date: Mon, 4 Jun 2018 00:54:09 -0700 From: bob prohaska To: Warner Losh Cc: Erich Dollansky , freebsd-arm@freebsd.org, bob prohaska Subject: OOM errors, was Re: panic: Assertion td->td_lock == TDQ_LOCKPTR(tdq) failed at /usr/src/sys/kern/sched_ule.c:2137 Message-ID: <20180604075409.GA76017@www.zefox.net> References: <20180601154153.GA62632@www.zefox.net> <20180602091606.63a1ab37.freebsd.ed.lists@sumeritec.com> <20180602150549.GA68197@www.zefox.net> <20180602193255.GA68908@www.zefox.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.24 (2015-08-30) X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 Jun 2018 07:54:06 -0000 > > > On Sat, Jun 02, 2018 at 09:14:18AM -0600, Warner Losh wrote: > > > > > > Do you have r334508? It fixes the OOM falsely triggering. > > > > The kernel is now up to 334538, but I'm still seeing OOM kills, like this: Jun 4 00:01:57 www kernel: pid 27824 (llvm-tblgen), uid 0, was killed: out of swap space Jun 4 00:01:57 www kernel: pid 27828 (llvm-tblgen), uid 0, was killed: out of swap space Jun 4 00:01:57 www kernel: pid 27832 (llvm-tblgen), uid 0, was killed: out of swap space Jun 4 00:01:57 www kernel: pid 27830 (llvm-tblgen), uid 0, was killed: out of swap space Jun 4 00:01:57 www kernel: pid 27610 (make), uid 0, was killed: out of swap space After restarting the -j4 buildworld with -DNO_CLEAN it appeared that swap use peaked around 129 MB. Four instances of llvm-tblgen entered state pfault at roughly the same time swap use peaked and then two were killed. Apparently the remaining pair died in sympathy. Have you any idea what I might be doing wrong? Thanks for reading, bob prohaska `