This is a non-article, an exercise in bias confirmation. Without a control with no segfaults, or a root cause, it's not useful.
50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
21–30 of 45 posts
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#22I have the same with a Kaby Lake laptop btw (XPS 13) where random segfaults happen. This is with the very latest BIOS update from a day or two ago. Modern CPUs suck.
I wonder if this can also be attributed to the highly-microcoded nature of modern CPUs. (Then, at least, it may be software that sucks, not hardware.)
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#23Should people planning to buy a Ryzen system hold off until this is fixed?
personally, I would say yes.
I've been happily using my 1700x on my personal machine for months without much issue (except when as noted above, the issue was induced with very very high CPU load, manually and in a controlled manner).
Unless you do very CPU heavy work that lasts several minutes or longer (like kernel compiling, chromium compiling, autotools, starting electron apps), especially when you run gentoo (most likely), it should not be an issue.
I do a lot of dev work myself, so I do compile often but a short compiler run hasn't ever induced this bug and longer linux kernel builds suffered more from my inadequate cooling solutions rather than the CPU having bugs.
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#24This is a non-article, an exercise in bias confirmation. Without a control with no segfaults, or a root cause, it's not useful.
In the article (or perhaps the original article that is linked in this one) they explain that they ran the same tests on Intel processors without any issues whatsoever...
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#25Should people planning to buy a Ryzen system hold off until this is fixed?
I would wait. I bought a 1800x Ryzen and had some stability problems under Debian Buster which disappeared after a BIOS update, but I'm not compiling large projects continuously nor it has been up for a lot of time (maybe 3 days uptime? Got the new computer two weeks ago.. when it gets to 100+ days uptime I will be happy)
Under Windows it worked flawlessly even with the old BIOS.
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#26similar problem on EPYC https://www.reddit.com/r/Amd/comments/6rmq6q/epyc_7551_minin... https://www.reddit.com/r/Amd/comments/6rrbsp/epyc_confirmed_...
[deleted]
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#27Earlier quoted context omitted.
Can we all switch to Xeons and ? Or do those have similar issues?
No idea, but honestly I can't be arsed anymore with new stuff when it's so unreliable. This is from a few minutes ago (the timestamps are hours old, but that's because dmesg timestamps don't take into account sleep time) [Sat Aug 5 13:46:21 2017] ------------[ cut here ]------------ [Sat Aug 5 13:46:21 2017] WARNING: CPU: 0 PID: 16026 at drivers/base/firmware_class.c:1225 _request_firmware+0x51f/0x8a0 [Sat Aug 5 13:4…
Modern hardware is unreliable, especially under GNU/Linux. Ryzen didn't give me any problem under Windows, but GNU/Linux.. the same can be said of Skylake/Broadwell i915 gpu driver. Both my Thinkpad T450s and X250 are not able to get past a few weeks uptime while using Debian. Under Windows they can go on for months.
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#28Note that it appears that a large number of the segfaults which Michael (phoronix) is reporting may be coming from a software issue. In particular, people on the phoronix forums are reporting that conftest segfaults are a known software issue and also one has reported that he was able to reproduce the conftest segfaults on an intel CPU. So not saying that there's not a problem with Ryzen, but it is possible a large n…
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)
Most likely to generate clicks.
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#29This is a non-article, an exercise in bias confirmation. Without a control with no segfaults, or a root cause, it's not useful.
In the article (or perhaps the original article that is linked in this one) they explain that they ran the same tests on Intel processors without any issues whatsoever...
Could be an issue with the motherboard, BIOS, or RAM though. If this was repeated across multiple motherboards, CPUs and RAM combinations to exclude the possibility of it being a flaky part, then yes, sure.
Re: 50+ Segmentation Faults per Hour: Continuing to Stress Ryzen
#30similar problem on EPYC https://www.reddit.com/r/Amd/comments/6rmq6q/epyc_7551_minin... https://www.reddit.com/r/Amd/comments/6rrbsp/epyc_confirmed_...
The segfaults repro on Intel systems as well with his setup:
https://www.phoronix.com/forums/forum/phoronix/latest-phoron...
The segfaults being seen on that Epyc test are not the fault of the hardware - either that, or they're a problem that is common between Intel and AMD processors somehow.