Author: ken
Date: Wed Jan 10 10:41:27 2018
New Revision: 19662
Log:
Update intel microcode, and the example, to 20180108.
Modified:
trunk/BOOK/general.ent
trunk/BOOK/introduction/welcome/changelog.xml
trunk/BOOK/postlfs/config/firmware.xml
Modified: trunk/BOOK/general.ent
==============================================================================
--- trunk/BOOK/general.ent Wed Jan 10 07:43:22 2018 (r19661)
+++ trunk/BOOK/general.ent Wed Jan 10 10:41:27 2018 (r19662)
@@ -1,12 +1,12 @@
<!-- $LastChangedBy$ $Date$ -->
-<!ENTITY day "08"> <!-- Always 2 digits -->
+<!ENTITY day "10"> <!-- Always 2 digits -->
<!ENTITY month "01"> <!-- Always 2 digits -->
<!ENTITY year "2018">
<!ENTITY copyrightdate "2001-&year;">
<!ENTITY copyholder "The BLFS Development Team">
<!ENTITY version "&year;-&month;-&day;">
-<!ENTITY releasedate "January 8th, &year;">
+<!ENTITY releasedate "January 10th, &year;">
<!ENTITY pubdate "&year;-&month;-&day;"> <!-- metadata req. by TLDP -->
<!ENTITY blfs-version "svn"> <!-- svn|[release #] -->
<!ENTITY lfs-version "development"> <!-- x.y|development -->
Modified: trunk/BOOK/introduction/welcome/changelog.xml
==============================================================================
--- trunk/BOOK/introduction/welcome/changelog.xml Wed Jan 10 07:43:22
2018 (r19661)
+++ trunk/BOOK/introduction/welcome/changelog.xml Wed Jan 10 10:41:27
2018 (r19662)
@@ -42,6 +42,18 @@
</listitem>
-->
<listitem>
+ <para>January 10th, 2018</para>
+ <itemizedlist>
+ <listitem>
+ <para>[ken] - Update intel microcode to 20180108, this includes
+ Spectre mitigation for some CPUs (and might slow them as a result).
+ More details of updated models are in the ticket. Fixes
+ <ulink url="&blfs-ticket-root;10249">#10249</ulink>.</para>
+ </listitem>
+ </itemizedlist>
+ </listitem>
+
+ <listitem>
<para>January 9th, 2018</para>
<itemizedlist>
<listitem>
Modified: trunk/BOOK/postlfs/config/firmware.xml
==============================================================================
--- trunk/BOOK/postlfs/config/firmware.xml Wed Jan 10 07:43:22 2018
(r19661)
+++ trunk/BOOK/postlfs/config/firmware.xml Wed Jan 10 10:41:27 2018
(r19662)
@@ -130,9 +130,9 @@
<para>The first step is to get the most recent version of the Intel
microcode. This must be done by navigating to
- <ulink
url='https://downloadcenter.intel.com/download/27377/Linux-Processor-Microcode-Data-File'/>
+ <ulink
url='https://downloadcenter.intel.com/download/27431/Linux-Processor-Microcode-Data-File'/>
and following the instructions there. As of this writing the most recent
- version of the microcode is <filename>microcode-20171117.tgz</filename>.
+ version of the microcode is <filename>microcode-20180108.tgz</filename>.
Extract this file in the normal way to create an
<filename>intel-ucode</filename>
directory, containing various blobs with names in the form
XX-YY-ZZ.</para>
@@ -180,15 +180,15 @@
<para>This example from the Haswell i7 which was released in Q2 2014 and
is
not affected by the TSX errata shows it has been updated from revision
0x19
- in the BIOS/UEFI to revision 0x22. Unlike in older kernels, the
individual
+ in the BIOS/UEFI to revision 0x23. Unlike in older kernels, the
individual
CPUs are not separately reported:</para>
-<screen><literal>[ 0.000000] Linux version 4.11.0 (lfs@plexi) (gcc version
7.1.0 (GCC) )
- #1 SMP PREEMPT Sun May 14 16:00:00 BST 2017
-[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-sda6 root=/dev/sda6 ro
-[ 0.913685] microcode: sig=0x306c3, pf=0x2, revision=0x22
+<screen><literal>[ 0.000000] Linux version 4.14.12 (lfs@plexi) (gcc version
7.2.0 (GCC) )
+ #1 SMP PREEMPT Tue Jan 9 16:00:00 GMT 2018
+[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.14.12-sda7 root=/dev/sda7 ro
+[ 0.913685] microcode: sig=0x306c3, pf=0x2, revision=0x23
[ 0.913905] microcode: Microcode Update Driver: v2.2.
-[ 148.723932] microcode: updated to revision 0x22, date =
2017-01-27</literal></screen>
+[ 148.723932] microcode: updated to revision 0x23, date =
2017-11-28</literal></screen>
<para>That may be followed by individual reports for each core.</para>
<para>If the microcode was not updated, there is no new microcode for
@@ -303,11 +303,11 @@
kernel, showing that the first notification comes before the kernel
version
is mentioned:</para>
-<screen><literal>[ 0.000000] microcode: microcode updated early to revision
0x22, date = 2017-01-27
-[ 0.000000] Linux version 4.11.0 (lfs@plexi) (gcc version 7.1.0 (GCC) )
- #2 SMP PREEMPT Sun May 14 17:58:53 BST 2017
-[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.11.0-sda6 root=/dev/sda6 ro
-[ 0.928947] microcode: sig=0x306c3, pf=0x2, revision=0x22
+<screen><literal>[ 0.000000] microcode: microcode updated early to revision
0x23, date = 2017-11-20
+[ 0.000000] Linux version 4.14.12 (lfs@plexi) (gcc version 7.2.0 (GCC) )
+ #2 SMP PREEMPT Tue Jan 9 17:58:53 GMT 2018
+[ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.14.12-sda7 root=/dev/sda7 ro
+[ 0.928947] microcode: sig=0x306c3, pf=0x2, revision=0x23
[ 0.929160] microcode: Microcode Update Driver: v2.2.</literal></screen>
<para>An AMD example for an earlier stable kernel version:</para>
--
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
