As was previously reported, a defect with Sapphire Rapids Xeon CPUs caused a pause in shipments, and Intel has now released a statement clarifying the situation for consumers.
Intel Sapphire Rapids MCC Bug Caused Interruptions In Performance, Firmware Update to Resolve the Issue
In a statement issued to Tom's Hardware, Intel has acknowledged the halt in shipments, and here is what it has to say:
Last week, we informed you of an issue on a subset of 4th Generation Intel Xeon Medium Core Count Processors (SPR-MCC) that could interrupt system operation under certain conditions. Out of an abundance of caution, we temporarily paused some SPR-MCC shipments while we thoroughly evaluated firmware mitigation.
We are now confident the firmware mitigation addresses the issue. We have resumed shipping all versions of SPR-MCC and are working with customers to deploy the firmware as needed.
The statement clarifies that the issue has been identified by the company and, as expected, will be fixed through a firmware update. Intel hasn't confirmed the timeline for when the fix will be released, but we expect it soon since the shipments for Sapphire Rapids MCC have been resumed. Detailing into the actual issue, it was revealed that issues were encountered while running the processor, and it depicted that the root cause has got to do something with the disruptions in the timings of the processor.
Such issues are widely common amongst server CPUs, with a prime example being AMD's EPYC Rome CPUs stopping after 1,044 days of uptime. A firmware update will fix the issue and won't cause any performance difference. Intel currently offers three different variants of the processor. The XCC model features a high core count, whereas the MCC variant affected by the bug is designed for the mainstream market. Finally, the HBM lineup consists of high HBM2e memory stack allowing the processors to be utilized for high memory-usage applications.
The bug has made Intel halt the shipments since mid-June, and only after media outlets discovered the problem the company came forward to address the issue. Intel didn't specify this bug's reason or provide a specific firmware release date.
About the author: Muhammad Zuhair is a hardware and technology reporter for Wccftech, specializing in the semiconductor industry and the complex interplay between technology, manufacturing, and geopolitics. His coverage focuses on the corporate strategies and technological roadmaps of industry giants like TSMC, NVIDIA, Samsung, and Intel. Zuhair's expertise lies in deconstructing complex topics such as fabrication nodes (e.g., 2nm process), the economic impact of policies like the CHIPS Act, and the strategic development of AI infrastructure from NVIDIA, AMD and Intel.
Follow Wccftech on Google to get more of our news coverage in your feeds.
