From owner-freebsd-current@freebsd.org Mon Feb 19 16:57:55 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 A8C3EF0FDD6 for ; Mon, 19 Feb 2018 16:57:55 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from mailman.ysv.freebsd.org (mailman.ysv.freebsd.org [IPv6:2001:1900:2254:206a::50:5]) by mx1.freebsd.org (Postfix) with ESMTP id 4DECF7EF97 for ; Mon, 19 Feb 2018 16:57:55 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: by mailman.ysv.freebsd.org (Postfix) id 0A309F0FDD5; Mon, 19 Feb 2018 16:57:55 +0000 (UTC) Delivered-To: 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 EC082F0FDD4 for ; Mon, 19 Feb 2018 16:57:54 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from ipmail06.adl6.internode.on.net (ipmail06.adl6.internode.on.net [150.101.137.145]) by mx1.freebsd.org (Postfix) with ESMTP id 3081B7EF93 for ; Mon, 19 Feb 2018 16:57:53 +0000 (UTC) (envelope-from FreeBSD@shaneware.biz) Received: from 124-169-249-32.dyn.iinet.net.au (HELO leader.local) ([124.169.249.32]) by ipmail06.adl6.internode.on.net with ESMTP; 20 Feb 2018 03:22:43 +1030 Subject: Re: How to find CPU microcode version ? To: Kurt Jaeger , current@freebsd.org References: <20180218104137.GA32429@home.opsec.eu> From: Shane Ambler Message-ID: <057ac894-7362-b235-3859-65108b2afb76@ShaneWare.Biz> Date: Tue, 20 Feb 2018 03:22:41 +1030 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20180218104137.GA32429@home.opsec.eu> Content-Type: text/plain; charset=utf-8 Content-Language: en-AU Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.25 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: Mon, 19 Feb 2018 16:57:55 -0000 On 18/02/2018 21:11, Kurt Jaeger wrote: > Hi! > Around the 14th, processes started to be killed for out of swapspace, > even if the box had almost no load at all. > > pid 1056 (mutt), uid 104, was killed: out of swap space > pid 536 (devd), uid 0, was killed: out of swap space > pid 15093 (exim), uid 26, was killed: out of swap space > pid 91868 (mutt), uid 104, was killed: out of swap space > pid 1086 (sshd), uid 104, was killed: out of swap space > > Reboot of the box and waiting a few hours and the problem re-occured. > > The box has 32 GB RAM and 34 GB swap, which never was utilized > beyond a few hundred MBs. One situation that can cause out of swap errors is large amounts of wired ram. Wired ram is memory that can't be swapped out. When you get around 80 or 90% of physical ram wired you start seeing those errors. You can see the amount of wired displayed in top or sysctl vm.stats.vm.v_wire_count then times that by hw.pagesize There is a vm.max_wired but it doesn't appear to be an enforced limit. -- FreeBSD - the place to B...Software Developing Shane Ambler