From owner-freebsd-current@freebsd.org Sun Feb 18 18:28:46 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 82EE7F1F744 for ; Sun, 18 Feb 2018 18:28:46 +0000 (UTC) (envelope-from ml@netfence.it) Received: from smtp209.alice.it (smtp209.alice.it [82.57.200.105]) by mx1.freebsd.org (Postfix) with ESMTP id 0FF1283C68 for ; Sun, 18 Feb 2018 18:28:45 +0000 (UTC) (envelope-from ml@netfence.it) Received: from soth.ventu (87.18.51.42) by smtp209.alice.it (8.6.060.28) id 5A88C32E002D94AB for freebsd-current@freebsd.org; Sun, 18 Feb 2018 19:28:39 +0100 Received: from alamar.ventu (alamar.local.netfence.it [10.1.2.18]) by soth.ventu (8.15.2/8.15.2) with ESMTP id w1IISc7o036997 for ; Sun, 18 Feb 2018 19:28:38 +0100 (CET) (envelope-from ml@netfence.it) X-Authentication-Warning: soth.ventu: Host alamar.local.netfence.it [10.1.2.18] claimed to be alamar.ventu Subject: Re: How to find CPU microcode version ? To: freebsd-current@freebsd.org References: <20180218104137.GA32429@home.opsec.eu> From: Andrea Venturoli Message-ID: <90550601-e86b-a72d-83b6-405a371bb457@netfence.it> Date: Sun, 18 Feb 2018 19:28:33 +0100 User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0 MIME-Version: 1.0 In-Reply-To: <20180218104137.GA32429@home.opsec.eu> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US 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: Sun, 18 Feb 2018 18:28:46 -0000 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? Unless of course you set up rc.conf to repeat it at every start... bye av.