search for: soeoen

...tion against Intel (didn't hear about AMD though) is > quite likely, so, indeed, RedHat does not want to be even mentioned in > it, which will be unfair, especially after RedHat putting effort into > fixing somebody's else crap. > It isn't about washing hands, lawsuits, or soeoen else's stuff. It is about broken microcode updates. The code from intel was broken .. causing several CPUs not to boot after update. That (and only that) is why they were pulled. Users MUST individually QA the microcode for their individual CPUs, OEM Frimware, chipset etc. The issue here i...

...#39;t hear about AMD though) is >> quite likely, so, indeed, RedHat does not want to be even mentioned in >> it, which will be unfair, especially after RedHat putting effort into >> fixing somebody's else crap. >> > > It isn't about washing hands, lawsuits, or soeoen else's stuff. It is > about broken microcode updates. > > The code from intel was broken .. causing several CPUs not to boot after > update. That (and only that) is why they were pulled. > > Users MUST individually QA the microcode for their individual CPUs, OEM > Frimw...

...ough) is >>> quite likely, so, indeed, RedHat does not want to be even mentioned in >>> it, which will be unfair, especially after RedHat putting effort into >>> fixing somebody's else crap. >>> >> >> It isn't about washing hands, lawsuits, or soeoen else's stuff.? It is >> about broken microcode updates. >> >> The code from intel was broken .. causing several CPUs not to boot after >> update.? That (and only that) is why they were pulled. >> >> Users MUST individually QA the microcode for their individua...

> Look at: > > https://t.co/6fT61xgtGH > > Get the latest microcode.dat file from here: > > https://t.co/zPwagbeJFY > > See how to update the microcode from the links at the bottom of this page: > > https://t.co/EOgclWdHCw > > An before anyone asks .. I have no idea why Red Hat chose this path, > they did. It doesn't matter if I (or anyone else)