Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 18 Nov 2015 09:27:32 +0100
From:      Andrea Venturoli <ml@netfence.it>
To:        freebsd-questions@freebsd.org
Subject:   Re: Is processor microcode advised?
Message-ID:  <564C3674.8040803@netfence.it>
In-Reply-To: <CA%2BtpaK3EMAU5iN4NC6jXQtugJbxyN%2Bm2OtN5-4cyXqnpy4fLcQ@mail.gmail.com>
References:  <564B3E4D.7070808@gmail.com> <CA%2BtpaK3EMAU5iN4NC6jXQtugJbxyN%2Bm2OtN5-4cyXqnpy4fLcQ@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 11/17/15 16:10, Adam Vande More wrote:
> On Tue, Nov 17, 2015 at 8:48 AM, Will Senn <will.senn@gmail.com> wrote:
>
>> Is it important/necessary/advisable  to install microcode for Intel CPU's?
>> If so, how do you know which CPU's have updates? Also, after doing make
>> install in /usr/ports/sysutils/devcpu-data and adding
>> microcode_update_enable="YES" to rc.conf, how can you tell if anything was
>> applied - what do you look for in dmesg output
>>
>
> man cpuctl
>
> But normally this is just handled with a bios update.

Supposing BIOS has not been updated (due to no availability, lazyness, 
impossibility over a remote link, fear of bricking the box, etc...), the 
original question would still stand: is it important/necessary/advisable 
to use devcpu-data?

Also, I see microcode_update has to load the cpuctl module. What are the 
implications of this WRT security?
Would it be advisable to unload it afterwards?

  bye & Thanks
	av.



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?564C3674.8040803>