New Ryzen Is Running Solid Under Linux, No Compiler Segmentation Fault Issue

Written by Michael Larabel in Processors on 24 August 2017 at 08:19 PM EDT. Page 1 of 1. 83 Comments.

As a quick update to the AMD Linux "Performance Marginality Problem" affecting some early Ryzen processors under heavy load, today I received a new Ryzen 7 processor and indeed it's been running strong now for the past few hours under demanding load and has yet to hit the compiler segmentation fault bug.

As a reminder about the issue, this performance marginality problem is exclusive to certain workloads such as running many Linux compilation tasks in parallel. Compiling most software you should be fine unless really hammering the system hardware. Under select conditions, the compiler may then produce a segmentation fault. Under normal Linux desktop workloads, gaming, etc, all Ryzen processors should work just fine. AMD has confirmed this issue doesn't affect EPYC or Threadripper processors, which we'll be testing soon, and for those Linux users affected by the problem they have been handling an RMA process via AMD Customer Care.

Today I received a replacement Ryzen 7 1800X along with the AMD Threadripper platform that will finally be tested under Linux on Phoronix in the days ahead. While as excited as I am for running the Threadripper 1950X with some fun Linux workloads across its 16 cores / 32 threads, I first popped in the Ryzen 7 1800X into the system previously exhibiting the compiler segmentation fault problem.

I've now been running this system all afternoon/evening with the kill-ryzen script and have not encountered any compiler segmentation faults or other problems for that matter. The same motherboard, cooling, BIOS, Linux installation, etc, were maintained the same as the previously affected configuration. Considering how easy it was to reproduce on the previous CPU, I feel pretty confident now this issue indeed is no more and just isolated to the CPU.

AMD has not provided an official public explanation of the fundamental problem, but from those in our forums and elsewhere, it appears to affect Ryzen CPUs manufactured prior to week 25. This Ryzen 7 1800X was from "week 30" where as my original Ryzen 7 1800X review sample was from "week 5" as well as the Ryzen 7 1700. The Ryzen 5 1400 that I bought via retail channels in June was manufactured in week 14. The Ryzen 3 1300X review sample was from week 20 and the Ryzen 3 1200 from week 25.

Week 25 is the middle of June. The week number is shown on the processors in the second line as "UA 1705" where the 17 is representing the year and the next two digits showing the week, in this case 2017 week 5. I am unaware of any way that the date can be queried short of looking at the heat spreader.

I will continue running this Ryzen 7 1800X processor overnight but so far things are running solid under the enduring load thus far. With that, I am now very happy with Ryzen and still running the Ryzen on my main Fedora Workstation production system, even with a pre-week-25 model it's still fine for all of my day-to-day workloads; my only remaining critique of Ryzen outstanding is in regards to having Ryzen thermal monitoring support under Linux with no hwmon/thermal driver yet being available to read CPU temperatures. Stay tuned for AMD Ryzen Threadripper 1950X benchmarks on Phoronix in the next few days; Linux tests on AMD EPYC to follow after.

If you enjoyed this article consider joining Phoronix Premium to view this site ad-free, multi-page articles on a single page, and other benefits. PayPal or Stripe tips are also graciously accepted. Thanks for your support.

Related Articles
About The Author
Michael Larabel

Michael Larabel is the principal author of and founded the site in 2004 with a focus on enriching the Linux hardware experience. Michael has written more than 20,000 articles covering the state of Linux hardware support, Linux performance, graphics drivers, and other topics. Michael is also the lead developer of the Phoronix Test Suite, Phoromatic, and automated benchmarking software. He can be followed via Twitter, LinkedIn, or contacted via