[paulmd]

AMD has never stated that there is a fix for this. If you look at the link you posted, this is Larabel making this claim on the basis that he hasn't seen any forum posts noting this problem on samples manufactured after week 25. Quote:

> 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 problem only affects a minority of chips in the first place (likely a litho flaw in the cache section), it's probable that Larabel's second CPU just didn't happen to be one of the ones with problems. And Week 25 ends June 25, i.e. stock for these date ranges has hardly even made it through packaging/distribution to end users let alone been extensively tested yet.

Larabel is jumping the gun on insufficient evidence and people are racing to make the claim that AMD has fixed this, when that's far from the case. AMD certainly hasn't made any statements to this effect.

AMD is RMA'ing afflicted units, which is really all that can be done until they get a new stepping out. But I've seen no evidence that this is actually fixed.

[powercf]

> This problem only affects a minority of chips in the first place (likely a litho flaw in the cache section)

What are you basing this on? I've seen no good reporting on this* but the AMD Community segfault thread (https://community.amd.com/message/2796982) seems to suggest that almost all Ryzen CPUs manufactured before the end of June (which I assume is most of the current stock) are affected. Very few people load their Ryzens sufficiently to hit this bug, but a large number of those who attempt it seem to get the segfault.

* I would like to know the percentage of processors with the bug, percentage of review units with the bug (I would be very interested in this), and maybe some long-term testing of "bug free" processors etc.

[selectodude]

It may be ridiculous, but I'm not spending a million dollars on CPUs with information gleamed from a forum post.

[powercf]

It's not ridiculous, but there's pratically no more information about it. No major tech sites have covered it, beyond Phoronix. AMD haven't acknowledged it, beyond stating that "a performance marginality problem exclusive to certain workloads on Linux" exists, which is factually incorrect as it also seems to occur on other operating systems.

I'm not spending hundreds of euro on a processor without knowing something more concrete about this issue. If you budget is really ~million dollars, do you have additional information about this that you can share?

[selectodude]

My ~$400 CPU budget went toward a Skylake i7 a couple of years ago, I'm afraid.