From owner-freebsd-current@freebsd.org  Wed Feb 21 06:16:42 2018
Return-Path: <owner-freebsd-current@freebsd.org>
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 7B94EF087FE
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 21 Feb 2018 06:16:42 +0000 (UTC) (envelope-from lists@opsec.eu)
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 1DC81687B2
 for <freebsd-current@freebsd.org>; Wed, 21 Feb 2018 06:16:42 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: by mailman.ysv.freebsd.org (Postfix)
 id D1049F087FC; Wed, 21 Feb 2018 06:16:41 +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 BFD7AF087F9
 for <current@mailman.ysv.freebsd.org>; Wed, 21 Feb 2018 06:16:41 +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 5C2ED687B0
 for <current@freebsd.org>; Wed, 21 Feb 2018 06:16:41 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: from pi by home.opsec.eu with local (Exim 4.89 (FreeBSD))
 (envelope-from <lists@opsec.eu>)
 id 1eoNhm-00066D-SO; Wed, 21 Feb 2018 07:16:38 +0100
Date: Wed, 21 Feb 2018 07:16:38 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Shane Ambler <FreeBSD@ShaneWare.Biz>
Cc: current@freebsd.org
Subject: Re: How to find CPU microcode version ?
Message-ID: <20180221061638.GM32429@home.opsec.eu>
References: <20180218104137.GA32429@home.opsec.eu>
 <057ac894-7362-b235-3859-65108b2afb76@ShaneWare.Biz>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <057ac894-7362-b235-3859-65108b2afb76@ShaneWare.Biz>
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
 <freebsd-current.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current/>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-current>, 
 <mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 21 Feb 2018 06:16:42 -0000

Hi!

> One situation that can cause out of swap errors is large amounts of
> wired ram.

Indeed: Very large amounts of wired RAM. What happened ? This
did not happen before the last upgrade ? I'm at r328899.

CPU:  0.0% user,  0.0% nice,  0.1% system,  0.0% interrupt, 99.9% idle
Mem: 2472K Active, 8K Inact, 31G Wired, 515M Free
ARC: 25G Total, 19G MFU, 3792M MRU, 840K Anon, 492M Header, 2040M Other
     22G Compressed, 36G Uncompressed, 1.67:1 Ratio
Swap: 34G Total, 76M Used, 34G Free, 8K In, 92K Out

-- 
pi@opsec.eu            +49 171 3101372                         2 years to go !