Open Daniel451 opened 6 years ago
This was necessary to run on my Ubuntu 18.04 + Ryzen 2700x. Everything was fine, 3 hours run, with this pull request code and using arch folder. This fixed the issue https://github.com/suaefar/ryzen-test/issues/28 I reported earlier.
+1 on merging this and I'll tell if anything different happens on a longer run later.
@m-r-s Yes. I know that. But this is an open source unlicensed code and there's not much I can do but use the original repository for communicating with other interested people.
If you license this... community could keep going on. Have you thought about that?
Does this help? Feel free to improve the script. But remember that you need someone with a faulty CPU to confirm that the version with your modifications actually works (i.e., detects faulty CPUs).
Awesome. Please... keep this PR. This is being referenced in some community + AMD forum conversations and anyone with 2700x will be able to test and maybe find a faulty 2700x.
Mine is able to run this PR but let's have some more confirmations.
PLEASE READER, if you own a Ryzen 2700x able to pass this test without issues... please give a 👍 in this. Or 👎 if the test caught any segfault.
This way we will be able to know this test catches any fault.
Just so you know, I'm keeping an updated version of ryzen-test that you can have a look at: https://github.com/Oxalin/ryzen-test
It is using GCC 7.2.0, but it could be updated to 8.1 or 8.2 if needed. @Daniel451 , I'm using a Ryzen 1XXX here, so if you could give me an update on my branch with your 2700X, that would be appreciated.
I will as soon as I get back to home.
Okay, I will leave this PR open
I have added an arch-linux directory, putting updated copies of
kill-ryzen.sh
andbuildloop.sh
for gcc8.1 there. This worked for me with Ryzen 7 2700X and Arch Linux as well as Ubuntu 18.04 LTS.