Hide Forgot
+++ This bug was initially created as a clone of Bug #1846119 +++ Description of problem: Microcode revision 0xdc for CPU 06-4e-03 (Skylake) can cause the system to freeze when applying the early microcode update. Late updates seem to be ok, at least on this system. [root@intel-skylake-y-01 ~]# lscpu | egrep -i -e family -e model -e stepping CPU family: 6 Model: 78 Model name: Intel(R) Core(TM) m5-6Y54 CPU @ 1.10GHz Stepping: 3 [root@intel-skylake-y-01 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version 0x2d [root@intel-skylake-y-01 ~]# yum -y update microcode_ctl ... [root@intel-skylake-y-01 ~]# rpm -q microcode_ctl microcode_ctl-20191115-4.20200602.2.el8_2.x86_64 [root@intel-skylake-y-01 ~]# rpm -q --provides microcode_ctl | grep iucode_rev.*06-4e-03 iucode_rev(fname:intel/06-4e-03;cpuid:000406e3;pf_mask:0xc0) = 0xdc iucode_rev(fname:intel/06-4e-03;platform_id:0x40) = 0xdc iucode_rev(fname:intel/06-4e-03;platform_id:0x80) = 0xdc [root@intel-skylake-y-01 ~]# echo 1 > /sys/devices/system/cpu/microcode/reload [root@intel-skylake-y-01 ~]# cat /sys/devices/system/cpu/cpu0/microcode/version 0xdc [root@intel-skylake-y-01 ~]# dracut --force --early-microcode [root@intel-skylake-y-01 ~]# reboot ... <<<HANG AFTER GRUB SCREEN>>> Version-Release number of selected component (if applicable): microcode_ctl-20191115-4.20200602.2.el8_2.x86_64 How reproducible: always Steps to Reproduce: 1. install RHEL-8.2.0 2. apply z-stream update to microcode_ctl-20191115-4.20200602.2.el8_2.x86_64 3. dracut --force --early-ucode 4. reboot Actual results: hang after grub Expected results: normal boot Additional info: Upstream bug report: https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31
06-5e-03 is to be blacklisted as well per [1]. [1] https://github.com/intel/Intel-Linux-Processor-Microcode-Data-Files/issues/31#issuecomment-644885826
Verified with microcode_ctl-1.17-33.29.el6_10. The failed tasks are due to blacklisted CPUs which means they are not running the newest microcode revision. In other words, the failures are expected and a good thing since it means the blacklist is working. https://beaker.engineering.redhat.com/matrix/?whiteboard_filter=&job_ids=4372080%0D%0A4372125&toggle_nacks_on=on
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHEA-2020:2742