![]() Whether Microsoft will choose to do this in the near future is anyone’s guess, but they certainly are capable of offering the microcode updates in that manner. I’ve seen several microcode updates in Windows Updates, but someone pointed out the other day that it has been quite a while since one of these has been issued, even though Intel (and perhaps AMD I haven’t been following them) have been chugging right along with the updates themselves. If that’s true, why can’t Windows /Microsoft do firmware updates the same way so that if something heads south it’s easier to fix or undo? So it isn’t clear if the “Belay that order” order applies just to Haswell and Broadwell, or to Haswell, Broadwell, Ivy Bridge, Sandy Bridge, Skylake and Kaby Lake as well.Īs I understand it the Linux way of updating the firmware is much more undoable than a BIOS update. We have determined that similar behavior occurs on other products in some configurations, including Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms. The problem extends beyond Haswell and Broadwell. Then there’s a link to this list of Intel products, which includes Coffee Lake, Kaby Lake, Skylake, Broadwell, Haswell, Ivy Bridge and Sandy Bridge processors. The progress we have made in identifying a root cause for Haswell and Broadwell will help us address issues on other platforms. Please be assured we are working quickly to address these issues. We believe it is important for OEMs and our customers to follow this guidance for all of the specified platforms listed below, as they may demonstrate higher than expected reboots and unpredictable system behavior. This would be delivered via a BIOS update, and would not impact mitigations for Variant 1 (Spectre) and Variant 3 (Meltdown). For those concerned about system stability while we finalize the updated solutions, we are also working with our OEM partners on the option to utilize a previous version of microcode that does not display these issues, but removes the Variant 2 (Spectre) mitigations.We expect to share more details on timing later this week. We also ask that our industry partners focus efforts on testing early versions of the updated solution for Broadwell and Haswell we started rolling out this weekend, so we can accelerate its release.We recommend that OEMs, Cloud service providers, system manufacturers, software vendors and end users stop deployment of current versions on the below platforms, as they may introduce higher than expected reboots and other unpredictable system behavior.Based on this, we are updating our guidance for customers and partners: We have now identified the root cause of the reboot issue impacting Broadwell and Haswell platforms, and made good progress in developing a solution to address it. Here’s what the official announcement says: Re-reading the supporting info, it isn’t clear (to me) if the halt has been called just for Broadwell and Haswell chips, or for all of Intel’s product line. It’s the old boot problem, but the advice is to avoid ANY firmware upgrades, on any platform.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |