Author: ken
Date: Fri Feb 23 15:51:03 2018
New Revision: 19853

Log:
firmware: Update the intel microcode examples to the current, i.e. old, release 
and the 4.15.3 kernel. Nobody commented on the bogosity in my previous 
late-load example, but it is gone now.

Modified:
   trunk/BOOK/postlfs/config/firmware.xml

Modified: trunk/BOOK/postlfs/config/firmware.xml
==============================================================================
--- trunk/BOOK/postlfs/config/firmware.xml      Fri Feb 23 13:27:30 2018        
(r19852)
+++ trunk/BOOK/postlfs/config/firmware.xml      Fri Feb 23 15:51:03 2018        
(r19853)
@@ -180,16 +180,18 @@
 
       <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 0x23. Unlike in older kernels, the 
individual
-      CPUs are not separately reported:</para>
-
-<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 0x23, date = 
2017-11-28</literal></screen>
-    <para>That may be followed by individual reports for each core.</para>
+      in the BIOS/UEFI (which this version of hte kernel now complains about) 
to
+      revision 0x22. Unlike in older kernels, the individual CPUs are not 
separately
+      reported:</para>
+
+<screen><literal>[    0.000000] Linux version 4.15.3 (ken@plexi) (gcc version 
7.3.0 (GCC))
+               #2 SMP PREEMPT Fri Feb 23 03:13:53 GMT 2018
+[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda6 root=/dev/sda6 ro
+[    0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata;
+               please update microcode to version: 0x22 (or later)
+[    0.482712] microcode: sig=0x306c3, pf=0x2, revision=0x19
+[    0.482937] microcode: Microcode Update Driver: v2.2.
+[  402.668612] microcode: updated to revision 0x22, date = 
2017-01-27</literal></screen>
 
     <para>If the microcode was not updated, there is no new microcode for
     this system's processor. If it did get updated, you can now proceed to 
<xref
@@ -303,12 +305,12 @@
       kernel, showing that the first notification comes before the kernel 
version
       is mentioned:</para>
 
-<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>
+<screen><literal>[    0.000000] microcode: microcode updated early to revision 
0x22, date = 2017-01-27
+[    0.000000] Linux version 4.15.3 (ken@plexi) (gcc version 7.3.0 (GCC))
+               #3 SMP PREEMPT Fri Feb 23 05:06:50 GMT 2018
+[    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda6 root=/dev/sda6 ro
+[    0.489478] microcode: sig=0x306c3, pf=0x2, revision=0x22
+[    0.489747] microcode: Microcode Update Driver: v2.2.</literal></screen>
 
       <para>An AMD example:</para>
 
-- 
http://lists.linuxfromscratch.org/listinfo/blfs-book
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page

Reply via email to