Date: Tue, 20 Feb 2018 03:22:41 +1030 From: Shane Ambler <FreeBSD@ShaneWare.Biz> To: Kurt Jaeger <lists@opsec.eu>, current@freebsd.org Subject: Re: How to find CPU microcode version ? Message-ID: <057ac894-7362-b235-3859-65108b2afb76@ShaneWare.Biz> In-Reply-To: <20180218104137.GA32429@home.opsec.eu> References: <20180218104137.GA32429@home.opsec.eu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?057ac894-7362-b235-3859-65108b2afb76>