![[H]ard|Forum](/styles/hardforum/xenforo/logo_dark.png){kind=logo}
- Joined
- May 18, 1997
- Messages
- 54,911
Back on January 11, Intel started seeing reports of random system reboots after applying Meltdown and Spectre patches on Intel Broadwell and Haswell CPUs. Seems as if this was not an isolated occurrence and this has now been verified with other Intel partners. And this looks to be hammering a larger base of CPUs than first reported. Ivy Bridge, Sandy Bridge, Skylake, and Kaby Lake processors are also affected. Microcode is in the works to address this and being worked on now.
We have now issued firmware updates for 90 percent of Intel CPUs introduced in the past five years, but we have more work to do. As I noted in my blog post last week, while the firmware updates are effective at mitigating exposure to the security issues, customers have reported more frequent reboots on firmware updated systems.
As part of this, we have determined that similar behavior occurs on other products in some configurations, including Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms. We have reproduced these issues internally and are making progress toward identifying the root cause. In parallel, we will be providing beta microcode to vendors for validation by next week.
Intel has also followed up its initial desktop performance metrics with benchmarks for data center. All looks well except for data IO, which of course is no concern to data centers. /s
As usual, take these with a grain of salt, and hopefully you admins have some pre-patch metrics to use for comparison on your own systems.
The benchmark results reported above may need to be revised as additional testing is conducted. The results depend on the
specific platform configurations and workloads utilized in the testing, and may not be applicable to any particular user’s
components, computer system or workloads. The results are not necessarily representative of other benchmarks and other
benchmark results may show greater or lesser impact from mitigations.
We have now issued firmware updates for 90 percent of Intel CPUs introduced in the past five years, but we have more work to do. As I noted in my blog post last week, while the firmware updates are effective at mitigating exposure to the security issues, customers have reported more frequent reboots on firmware updated systems.
As part of this, we have determined that similar behavior occurs on other products in some configurations, including Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms. We have reproduced these issues internally and are making progress toward identifying the root cause. In parallel, we will be providing beta microcode to vendors for validation by next week.
Intel has also followed up its initial desktop performance metrics with benchmarks for data center. All looks well except for data IO, which of course is no concern to data centers. /s
As usual, take these with a grain of salt, and hopefully you admins have some pre-patch metrics to use for comparison on your own systems.
The benchmark results reported above may need to be revised as additional testing is conducted. The results depend on the
specific platform configurations and workloads utilized in the testing, and may not be applicable to any particular user’s
components, computer system or workloads. The results are not necessarily representative of other benchmarks and other
benchmark results may show greater or lesser impact from mitigations.
