> It looks as though my CPU hasn't been fixed yet. Is that right? >> > > That's odd - i wonder why the checksum of the file changed; > > # grep 06-3f-02 intel-firmware-md5s-9jan2018.txt > intel-firmware-md5s-10jan2018.txt > intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749 > /lib/firmware/intel-ucode/06-3f-02 > intel-firmware-md5s-10jan2018.txt:b6e684762e7212054271c9441048fa93 > /lib/firmware/intel-ucode/06-3f-02 > > And with intel-microcode-20180108-r1 its back to what it was;
# grep 06-3f-02 intel-firmware-md5s-9jan2018.txt intel-firmware-md5s-10jan2018.txt intel-firmware-md5s-11jan2018.txt intel-firmware-md5s-9jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749 /lib/firmware/intel-ucode/06-3f-02 intel-firmware-md5s-10jan2018.txt:b6e684762e7212054271c9441048fa93 /lib/firmware/intel-ucode/06-3f-02 intel-firmware-md5s-11jan2018.txt:194c362f2c45d8a45e2ab58d5f2c9749 /lib/firmware/intel-ucode/06-3f-02 Looks like there was an issue with intel-microcode-20180108. 50/94 files are different from intel-microcode-20171117_p20171215-r1 to intel-microcode-20180108-r1, they are; 06-05-00 06-05-02 06-05-03 06-06-0a 06-06-0d 06-08-01 06-08-03 06-08-06 06-08-0a 06-09-05 06-0b-01 06-0b-04 06-0e-0c 06-0f-02 06-0f-06 06-0f-07 06-0f-0b 06-0f-0d 06-16-01 06-17-06 06-17-0a 06-1c-02 06-1c-0a 06-26-01 06-3e-04 06-3f-04 06-46-01 06-47-01 06-4f-01 06-55-04 06-56-02 06-56-03 06-5c-09 06-5e-03 06-7a-01 06-8e-09 06-8e-0a 06-9e-09 06-9e-0a 06-9e-0b 0f-00-07 0f-00-0a 0f-02-04 0f-02-05 0f-02-07 0f-02-09 0f-04-01 0f-04-08 0f-04-0a 0f-06-04
