From owner-freebsd-current@freebsd.org  Wed Feb 21 06:20:53 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 5666DF08B8A
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Wed, 21 Feb 2018 06:20:53 +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 EFA3968A0F
 for <freebsd-current@freebsd.org>; Wed, 21 Feb 2018 06:20:52 +0000 (UTC)
 (envelope-from lists@opsec.eu)
Received: by mailman.ysv.freebsd.org (Postfix)
 id AB98DF08B89; Wed, 21 Feb 2018 06:20:52 +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 9981FF08B87
 for <current@mailman.ysv.freebsd.org>; Wed, 21 Feb 2018 06:20:52 +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 3424D68A0B
 for <current@freebsd.org>; Wed, 21 Feb 2018 06:20:52 +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 1eoNlr-00068m-P4
 for current@freebsd.org; Wed, 21 Feb 2018 07:20:51 +0100
Date: Wed, 21 Feb 2018 07:20:51 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: current@freebsd.org
Subject: Re: How to find CPU microcode version ?
Message-ID: <20180221062051.GA23558@home.opsec.eu>
References: <20180218104137.GA32429@home.opsec.eu>
 <057ac894-7362-b235-3859-65108b2afb76@ShaneWare.Biz>
 <20180221061638.GM32429@home.opsec.eu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20180221061638.GM32429@home.opsec.eu>
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:20:53 -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.

vfs.zfs.arc_max was at 32345493504

changed that to

vfs.zfs.arc_max=16172746752

Looks better now.

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