From owner-freebsd-current@freebsd.org  Sun Feb 18 18:48:22 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 5D2B9F20D0D
 for <freebsd-current@mailman.ysv.freebsd.org>;
 Sun, 18 Feb 2018 18:48:22 +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 ECA9284ACC
 for <freebsd-current@freebsd.org>; Sun, 18 Feb 2018 18:48:21 +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 1enU0f-000IS0-37; Sun, 18 Feb 2018 19:48:25 +0100
Date: Sun, 18 Feb 2018 19:48:25 +0100
From: Kurt Jaeger <lists@opsec.eu>
To: Andrea Venturoli <ml@netfence.it>
Cc: freebsd-current@freebsd.org
Subject: Re: How to find CPU microcode version ?
Message-ID: <20180218184825.GG32429@home.opsec.eu>
References: <20180218104137.GA32429@home.opsec.eu>
 <90550601-e86b-a72d-83b6-405a371bb457@netfence.it>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <90550601-e86b-a72d-83b6-405a371bb457@netfence.it>
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: Sun, 18 Feb 2018 18:48:22 -0000

Hi!

> On 02/18/18 11:41, Kurt Jaeger wrote:
> 
> > Reboot of the box and waiting a few hours and the problem re-occured.
> 
> Doesn't the work of microcode_update vanish after a reboot?

Thanks. I was not sure and tested this. Indeed, yes, the microcode update is
reverted by rebooting.

Then I have some other issue, because my problems were ongoing after
reboots.

> Unless of course you set up rc.conf to repeat it at every start...

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