Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
by laydn on Saturday August 05, 2017 @05:01PM
(#14937875)
Agreed. It is a very basic comparison, which should be done before posting the article. I don't understand why he keeps posting these before running the exact same test on different processors (an Intel or even a different AMD should be ok)
Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
by catdog on Saturday August 05, 2017 @05:26PM
(#14938006)
Most likely to generate clicks.
Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
by igravious on Saturday August 05, 2017 @05:43PM
(#14938078)
Phoronix likes the clicks?
Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
by makomk on Saturday August 05, 2017 @05:04PM
(#14937893)
It may not even be a software issue. conftest is the name autoconf uses for various short snippets of code used to test properties of the toolchain and host system, and if I recall correctly some of them generate code that's expected to segfault when run if some guess about the host system is wrong.
Re:50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
by foofloobar on Monday August 07, 2017 @04:52AM
(#14946108)
This isn't the case. I see segfaults in multiple tests with Ryzen and none of them are conftest related. The CPU is broken.
I don't have Threadripper or Epyc to test.
So not saying that there's not a problem with Ryzen, but it is possible a large number of the errors are false positives arising from a known software issue.
I would wait Michael runs the same test on an Intel CPU with no problems to pass judgement.