On Tue, 30 Jun 2020 11:57:16 -0700
stan <upaitag(a)zoho.com> wrote:
On Tue, 30 Jun 2020 21:25:01 +0530
Sreyan Chakravarty <sreyan32(a)gmail.com> wrote:
> So is it confirmed this is a bug in the microcode ?
I don't think the original problem is a bug in the microcode, it is a
flaw in the design of the CPU architecture. The microcode is supposed
to fix that by mandating certain actions. Jonathon gave you some
useful advice to see if the CPU you are using is included in the fix.
I think I read that Intel is targeting later CPUs before earlier CPUs,
so it might not have been released for your CPU model yet, but *you*
should search and confirm if that is true. And Roger's suggestion
that updating the firmware before applying the fix worked also
deserves consideration, because it might be looking for specific
markers before it will apply, and they might only be there in the
latest update.
In Intel's defense, they have to be very cautious with updating the
microcode. I imagine that getting it wrong could have consequences up
to and including bricking the machine. Or it could introduce another
subtle vulnerability. This isn't something that's coded and thrown in
over night.