Changeset 1c1bdba
- Timestamp:
- 02/23/2018 11:51:03 PM (6 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/inkscape-core-mods, lazarus, lxqt, perl-modules, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 39e9acce
- Parents:
- 8c2155e
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
postlfs/config/firmware.xml
r8c2155e r1c1bdba 181 181 <para>This example from the Haswell i7 which was released in Q2 2014 and is 182 182 not affected by the TSX errata shows it has been updated from revision 0x19 183 in the BIOS/UEFI to revision 0x23. Unlike in older kernels, the individual 184 CPUs are not separately reported:</para> 185 186 <screen><literal>[ 0.000000] Linux version 4.14.12 (lfs@plexi) (gcc version 7.2.0 (GCC) ) 187 #1 SMP PREEMPT Tue Jan 9 16:00:00 GMT 2018 188 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.14.12-sda7 root=/dev/sda7 ro 189 [ 0.913685] microcode: sig=0x306c3, pf=0x2, revision=0x23 190 [ 0.913905] microcode: Microcode Update Driver: v2.2. 191 [ 148.723932] microcode: updated to revision 0x23, date = 2017-11-28</literal></screen> 192 <para>That may be followed by individual reports for each core.</para> 183 in the BIOS/UEFI (which this version of hte kernel now complains about) to 184 revision 0x22. Unlike in older kernels, the individual CPUs are not separately 185 reported:</para> 186 187 <screen><literal>[ 0.000000] Linux version 4.15.3 (ken@plexi) (gcc version 7.3.0 (GCC)) 188 #2 SMP PREEMPT Fri Feb 23 03:13:53 GMT 2018 189 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda6 root=/dev/sda6 ro 190 [ 0.000000] [Firmware Bug]: TSC_DEADLINE disabled due to Errata; 191 please update microcode to version: 0x22 (or later) 192 [ 0.482712] microcode: sig=0x306c3, pf=0x2, revision=0x19 193 [ 0.482937] microcode: Microcode Update Driver: v2.2. 194 [ 402.668612] microcode: updated to revision 0x22, date = 2017-01-27</literal></screen> 193 195 194 196 <para>If the microcode was not updated, there is no new microcode for … … 304 306 is mentioned:</para> 305 307 306 <screen><literal>[ 0.000000] microcode: microcode updated early to revision 0x2 3, date = 2017-11-20307 [ 0.000000] Linux version 4.1 4.12 (lfs@plexi) (gcc version 7.2.0 (GCC))308 # 2 SMP PREEMPT Tue Jan 9 17:58:53GMT 2018309 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.1 4.12-sda7 root=/dev/sda7ro310 [ 0. 928947] microcode: sig=0x306c3, pf=0x2, revision=0x23311 [ 0. 929160] microcode: Microcode Update Driver: v2.2.</literal></screen>308 <screen><literal>[ 0.000000] microcode: microcode updated early to revision 0x22, date = 2017-01-27 309 [ 0.000000] Linux version 4.15.3 (ken@plexi) (gcc version 7.3.0 (GCC)) 310 #3 SMP PREEMPT Fri Feb 23 05:06:50 GMT 2018 311 [ 0.000000] Command line: BOOT_IMAGE=/vmlinuz-4.15.3-sda6 root=/dev/sda6 ro 312 [ 0.489478] microcode: sig=0x306c3, pf=0x2, revision=0x22 313 [ 0.489747] microcode: Microcode Update Driver: v2.2.</literal></screen> 312 314 313 315 <para>An AMD example:</para>
Note:
See TracChangeset
for help on using the changeset viewer.