Intel confirms that Sandy Bridge (2000-series) through to Kaby Lake (7000-series) CPUs also affected by reboot bug reported to Haswell and Broadwell platforms.
Intel confirms that Sandy Bridge (2000-series) through to Kaby Lake (7000-series) CPUs also affected by reboot bug reported to Haswell and Broadwell platforms.
Last week, in the wake of firmware updates pushed to address the Meltdown security flaw, EVP and GM of the Data Center Group at Intel Navin Shenoy confirmed emerging reports of ‘higher system reboots’ on systems running Haswell and Broadwell CPUs. Clearly an undesirable state of affairs, Intel pledged that they would work quickly to diagnose the issue and disseminate an update through normal channels.
Sadly it turns out that this specific problem was more widespread than previously understood. Shenoy return to this official blog this week to state that systems running on both more recent and older Intel Core CPU generations were affected in addition to Haswell and Broadwell – namely Sandy Bridge, Ivybridge, Skylake and Kaby Lake. Potentially that’s a whole lot of systems currently in day-to-day use.
Thankfully Intel have been able to replicate the issue in their labs, a key step in getting to the bottom of the problem. They anticipate that beta microcode will be released to motherboard vendors for validation by next week for quick distribution.
Navin Shenoy’s blog post goes on to discuss the performance impact of patches which alleviate vulnerability to Meltdown. Using industry standard testing procedures on Xeon Scalable Processor platforms (i.e. Skylake-class Xeon systems) Intel discovered that many benchmarks tended to be impacted only minimally, typically on the order of 0-2%, but workloads with high I/O that are also saturating the CPU cores can be impacted as much as 25%. (Summarized Results)
Wisely, Shenoy is up front in stating that the real-world effect of the patch will vary according to each use case and system configuration. However, in their words “workloads that incorporate a larger number of user/kernel privilege changes and spend a significant amount of time in privileged mode will be more adversely impacted”. Coupled to a similar discussion last week this paints a picture of a patch which has negligible impact on consumer hardware, but is potentially highly detrimental to enterprise customers.
