Changeset b174fb1


Ignore:
Timestamp:
11/13/2019 03:43:33 AM (2 years ago)
Author:
Ken Moffat <ken@…>
Branches:
10.0, 10.1, 11.0, 9.1, ken/refactor-virt, lazarus, qt5new, trunk, xry111/git-date, xry111/git-date-for-trunk, xry111/git-date-test
Children:
6572358
Parents:
3ded25e
Message:

Update Intel microcode to 20191112.

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@22375 af4574ff-66df-0310-9fd7-8a98e5e911e0

Files:
2 edited

Legend:

Unmodified
Added
Removed
  • introduction/welcome/changelog.xml

    r3ded25e rb174fb1  
    4646      <itemizedlist>
    4747        <listitem>
     48          <para>[ken] - Update to Intel-Linux-Processor-Microcode-Data-Files-microcode-20191112.
     49          Fixes the Jump Conditional Code erratum on skylake and derived CPUs,
     50          and the TSX Async Abort vulnerability on some later CPUs. Fixes
     51          <ulink url="&blfs-ticket-root;12760">#12760</ulink>.</para>
     52        </listitem>
     53        <listitem>
    4854          <para>[timtas] - Remove an invalid build option in talloc-2.3.0.</para>
    4955        </listitem>
  • postlfs/config/firmware.xml

    r3ded25e rb174fb1  
    137137     url='https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/releases/'/>
    138138     and downloading the latest file there.  As of this writing the most recent
    139      version of the microcode is microcode-20190514a.
     139     version of the microcode is microcode-20191112.
    140140     Extract this file in the normal way, the microcode is in the <filename>intel-ucode</filename>
    141141     directory, containing various blobs with names in the form XX-YY-ZZ.
     
    154154     </para>
    155155
    156      <para>To be able to use the microcode which addresses MDS, the kernel must
    157      be one of the following stable versions: 5.1.2, 5.0.16, 4.19.43, 4.14.119,
    158      4.9.176 or a later version of those series, or a later kernel series such
    159      as 5.2.</para>
     156     <para>To be able to use this latest microcode on all the affected processors
     157     the kernel version needs to be versions 5.3.11, 4.19.84 or later.</para>
    160158
    161159     <para>Now you need to determine your processor's identity to see if there
     
    167165
    168166      <para>Convert the cpu family, model and stepping to pairs of hexadecimal
    169       digits. For a Haswell i7-4790 (described as Intel(R) Core(TM) i7-4790
    170       CPU) the relevant values are cpu family 6, model 60, stepping 3 so in
    171       this case the required identification is 06-3c-03. A look at the blobs
    172       will show that there is one for this CPU (although it might
    173       have already been applied by the BIOS). If there is a blob for your
     167      digits. For a Skylake i3 6100 (described as Intel(R) Core(TM) i3-6100
     168      CPU) the relevant values are cpu family 6, model 94, stepping 3 so in
     169      this case the required identification is 06-5e-03. A look at the blobs
     170      will show that there is one for this CPU (although for older issues it
     171      might have already been applied by the BIOS). If there is a blob for your
    174172      system then test if it will be applied by copying it (replace &lt;XX-YY-ZZ&gt;
    175173      by the identifier for your machine) to where the kernel can find it:</para>
     
    197195<screen><userinput>dmesg | grep -e 'microcode' -e 'Linux version' -e 'Command line'</userinput></screen>
    198196
    199       <para>This old example (from before Intel provided details of the latest
    200       versions) from the Haswell i7 which was released in Q2 2014 and is
    201       not affected by the TSX errata shows it has been updated from revision 0x19
    202       in the BIOS/UEFI (which this version of the kernel now complains about) to
    203       revision 0x24. Unlike in older kernels, the individual CPUs are not separately
    204       reported:</para>
    205 
    206 <screen><literal>[    0.000000] Linux version 4.18.0-rc8 (root@plexi) (gcc version 8.2.0 (GCC))
    207                #2 SMP PREEMPT Sat Aug 11 22:26:26 BST 2018
    208 [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.18.0-rc8-sda5 root=/dev/sda5 ro resume=/dev/sdb1
    209 [    0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata;
    210                please update microcode to version: 0x22 (or later)
    211 [    0.482712] microcode: sig=0x306c3, pf=0x2, revision=0x19
    212 [    0.274963] microcode: Microcode Update Driver: v2.2.
    213 [ 1475.941353] microcode: updated to revision 0x25, date = 2018-04-02
    214 [ 1475.944753] x86/CPU: CPU features have changed after loading microcode, but might not take effect</literal></screen>
     197      <para>This example (the machine had just been updated to a new kernel and was
     198      already using early loading for firmware from a few months before) shows it
     199      has now been updated from revision 0xcc to 0xd4.</para>
     200
     201<screen><literal>[    0.000000] microcode: microcode updated early to revision 0xcc, date = 2019-04-01
     202[    0.000000] Linux version 5.3.11 (ken@milliways) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Wed Nov 13 01:43:09 GMT 2019
     203[    0.569085] microcode: sig=0x506e3, pf=0x2, revision=0xcc
     204[    0.569136] microcode: Microcode Update Driver: v2.2.
     205[  257.975226] microcode: updated to revision 0xd4, date = 2019-08-14
     206[  257.976347] microcode: Reload completed, microcode revision: 0xd4</literal></screen>
    215207
    216208    <para>If the microcode was not updated, there is no new microcode for
     
    327319
    328320      <para>The places and times where early loading happens are very different
    329       in AMD and Intel machines. First, an Intel example from an updated
    330       kernel, showing that the first notification comes before the kernel version
    331       is mentioned:</para>
    332 
    333 <screen><literal>[    0.000000] microcode: microcode updated early to revision 0x27, date = 2019-02-26
    334 [    0.000000] Linux version 5.0.16 (lfs@plexi) (gcc version 9.1.0 (GCC))
    335                #2 SMP PREEMPT Sat May 18 23:10:29 BST 2019
    336 [    0.000000] Command line: BOOT_IMAGE=/vmlinuz-5.0.16-sda5 root=/dev/sda5 ro resume=/dev/sdb1
    337 [    0.275864] microcode: sig=0x306c3, pf=0x2, revision=0x27
    338 [    0.275911] microcode: Microcode Update Driver: v2.2.</literal></screen>
     321      in AMD and Intel machines. First, an Intel example with early loading:</para>
     322
     323<screen><literal>[    0.000000] microcode: microcode updated early to revision 0xd4, date = 2019-08-14
     324[    0.000000] Linux version 5.3.11 (ken@milliways) (gcc version 9.2.0 (GCC)) #1 SMP PREEMPT Wed Nov 13 01:43:09 GMT 2019
     325[    0.552160] microcode: sig=0x506e3, pf=0x2, revision=0xd4
     326[    0.552184] microcode: Microcode Update Driver: v2.2.</literal></screen>
    339327
    340328      <para>A historic AMD example:</para>
Note: See TracChangeset for help on using the changeset viewer.