@gordon-lack >> FWIW: I just ran that on my system with the *old* microcode, and it
Define *old* microcode Microcode can also come from the latest BIOS if you had updated. So if you really wanted to be sure you have the original CPU microcode which should be vulnerable, you will need to: 1. remove the intel-microcode package 2. rebuild the initrd for the kernel you want to run because the microcode is passed to the kernel 3. Make sure you are on an older BIOS release that did not include Intel microcode updates. The *older* Ubuntu intel-microcode from January, may contain the first Intel patches, so that is why you want to fully remove the package and rebuilt initrd so that you get the microcode directly from CPU or BIOS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1759920 Title: intel-microcode 3.20180312.0 causes lockup at login screen(w/ linux- image-4.13.0-37-generic) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/intel-microcode/+bug/1759920/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
