A little while ago, the Linux-headed sleuths over at Phoronix came across an obscure bug in Ryzen CPUs that triggered segmentation faults ("segfaults," which cause application crashes) in a compiler-specific workload. The bug was confirmed by AMD's engineers, who described it as a "performance marginality problem" and indicated that owners of affected CPUs could reach out to AMD Customer Care. The engineers also noted that Ryzen Threadripper and Epyc processors are unaffected. Phoronix's Michael Larabel took AMD up on its replacement offer and recently received a revised CPU that's apparently clear of the bug.
Larabel performed his due diligence and got to torturing the revised Ryzen 7 1800X under the same conditions that triggered the compilation segfaults. He's happy to report that he came across no issues whatsoever, whether related to compilation or not. The system used for testing was the same for old and revised processors alike. That also seems to clear any suspicion that the bug could somehow also be related to the motherboard or another component.
In his article, Larabel goes on to note that judging from his observations, Ryzen CPUs manufactured before week 25 (mid-June) of 2017 appear to be the ones affected by the problem. The bug is reasonably difficult to trigger, but users that want to rest easy can reach out to AMD Customer Care and get a replacement part.
|Geil lights up its Evo X ROG-certified RAM||4|
|Google Compute Engine is now powered in part by Pascal||10|
|EVGA slaps 12 GT/s memory on the GTX 1080 Ti FTW3 Elite||14|
|G.Skill unleashes AMD-ready Trident Z RGB kits up to 3200 MT/s||14|
|Asus' ZenFone 4 Pro offers high-end photography and networking||21|
|Radeon 17.9.2 drivers put the pedal to the metal for Project Cars 2||4|
|ROG Strix X299-XE Gaming motherboard is rather groovy||4|
|Miniature Golf Day Shortbread||18|
|GeForce 385.69 drivers are Game Ready for a ton of titles||2|
|That horse is dead Jim. Very dead.||+12|