<html><head></head><body>I don't know what's being fixed, but there are already microcode updates available for some Haswell Xeon E5 chips, according to OVH's (probably the 4th or 5th largest consumer of them) CEO on Twitter.<br>
In same tweet, said older chips (no idea how old) would get updates within weeks.<br>
YMMV.<br>
-Adam<br><br><div class="gmail_quote">On January 4, 2018 6:02:50 PM CST, Trevor Cordes <trevor@tecnopolis.ca> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">On 2018-01-04 Gilles Detillieux wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I just updated our Scientific Linux systems, which means the RHEL <br> updates are out too, and presumably CentOS updates are too or will be <br> shortly. These updates included firmware/microcode packages, which<br></blockquote><br>Interesting on the fw/microcode as what I read indicated this can't be<br>fixed in fw/mc. Though perhaps fw/mc changes could help in some way,<br>in tandem with the OS.<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"> I'm assuming are loaded on reboot as well. Some of the reports I read <br> suggested that you'd need to reflash your BIOS/UEFI firmware once the<br> PC manufacturers release these updates. Are those reports in error, <br> confusing the two types of firmware, or are we going to have to hunt <br> down PC or mobo-specific firmware updates for this whole debacle too?<br></blockquote><br>Again, from what I read, this won't be a fw thing, so I don't think<br>we'll see the above scenario. If we do -- if fix=fw+os -- then we're<br>in for a world of hurt because most mfr's stop updating fw after their<br>cycle, usually max of 3 years, some much less. That would leave a<br>whole slew of mobos unfixable. Good way for the industry to force a<br>rapid upgrade cycle!!! That might really get Intel in trouble,<br>though... $$$ lawsuits.<br><br>Of course, it's early days, so I could be way offbase, and even if I'm<br>correct now, my info may be wrong in a few days/weeks.<br><hr><br>Roundtable mailing list<br>Roundtable@muug.ca<br><a href="https://muug.ca/mailman/listinfo/roundtable">https://muug.ca/mailman/listinfo/roundtable</a><br></pre></blockquote></div><br>
-- <br>
Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html>