Intel says that it expects to share more details on its testing later this week. The company said it has started rolling out an early version of the updated solution to partners for testing and will make a final release that will become available after the testing has been completed.
"We have determined that similar behavior occurs on other products in some configurations, including Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms".
Intel has a patching problem.
Shenoy's announcement on Monday offered no mention, as he had explained in his earlier January 17 post, that other processors also are affected by the reboot problems, namely "Ivy Bridge-, Sandy Bridge-, Skylake-, and Kaby Lake-based platforms".
Each time news trickles out about just how insane this unprecedented industry event really is, cloud vendors and data center managers consider buying servers from AMD or ARM vendors the next time their systems need to be replaced.More news: Zion Williamson drops 34, impresses former National Basketball Association star night before announcement
More news: Adolescent age now starts from 10 and lasts up to 24
More news: 'Cold War Mentality': US Defense Strategy Includes False Judgments on China
But unfortunately, after sending the software patch to computer manufacturers and enterprise customers, chipmaker Intel discovered that its security fix caused reboot problems.
After the tests, which will presumably end next week, the company will issue a "beta microcode" of another security patch to various vendors and computer makers so this can be validated as good for applying on specific computer models. At least for Windows users, patches such as the one Intel issued typically come through the Windows Update feature, not from Intel itself.
At the issue's outbreak, Intel advised hardware partners to stop issuing updates for unpatched devices, but not to recall the updates they had already issued.
Intel now says users should avoid installing and partners should stop distributing the patch it issued to protect against the Meltdown and Spectre attacks. If your processor is not on the reboot issue list however, Intel still suggests to "vigilantly maintain security best practice" and keep systems up-to-date. However, it appears to be problematic for those on Broadwell or Haswell.