Minor edits to RancherOS microcode update docs

This commit is contained in:
Catherine Luse
2019-07-01 17:35:56 -07:00
committed by Denise
parent 43862f8805
commit 00ca9e09d3
@@ -3,10 +3,8 @@ title: How to update microcode
weight: 306
---
Processor manufacturers release stability and security updates to the processor microcode.
While microcode can be updated through the BIOS, the Linux kernel is also able to apply these updates.
These updates provide bug fixes that can be critical to the stability of your system.
Without these updates, you may experience spurious crashes or unexpected system halts that can be difficult to track down.
Processor manufacturers release stability and security updates to the processor microcode. While microcode can be updated through the BIOS, the Linux kernel is also able to apply these updates.
These updates provide bug fixes that can be critical to the stability of your system. Without these updates, you may experience spurious crashes or unexpected system halts that can be difficult to track down.
The microcode loader supports three loading methods:
@@ -16,27 +14,27 @@ The microcode loader supports three loading methods:
You can get more details from [here](https://www.kernel.org/doc/html/latest/x86/microcode.html).
RancherOS can support `Late loading`, here are the steps to update Intel microcode, you can refer to:
RancherOS supports `Late loading`. To update the Intel microcode, get the latest Intel microcode. An example is [here](https://downloadcenter.intel.com/download/28087/Linux-Processor-Microcode-Data-File?v=t). Then copy the data files to the firmware directory:
```
# we can get the latest intel microcode, such as https://downloadcenter.intel.com/download/28087/Linux-Processor-Microcode-Data-File?v=t
# then we need to copy data files to firmware dir
mkdir -p /lib/firmware/intel-ucode/
cp -v intel-ucode/* /lib/firmware/intel-ucode/
```
Reload the microcode. This file does not exist if you are running RancherOS on the hypervisor. Usually, the VM does not need to update the microcode.
# reload the microcode
# this file does not exist if you are running ROS on the hypervisor
# usually, the VM does not need to update the microcode.
```
echo 1 > /sys/devices/system/cpu/microcode/reload
```
Check the result:
# check the result
```
dmesg | grep microcode
[ 13.659429] microcode: sig=0x306f2, pf=0x1, revision=0x36
[ 13.665981] microcode: Microcode Update Driver: v2.01 <tigran@aivazian.fsnet.co.uk>, Peter Oruba
[ 510.899733] microcode: updated to revision 0x3b, date = 2017-11-17
```
You can use `runcmd` to reload microcode every boot:
You can use `runcmd` to reload the microcode every boot:
```
runcmd: