Closed Oxalin closed 6 years ago
Thank you for all the improvements. Did anyone test it on Ubuntu 17.04? Did it segfault? I don't have any faulty CPU anymore to test if the script still does what it is supposed to do with the source of GCC 7.2. I would assume yes, but who knows.
FWIW I tested it on Ubuntu 17.10 beta. I can confirm that it fixed the normal compilation error I was having before. Unfortunately I still got a segfault after several hours, which is likely bad news for my CPU.
I confirmed with gcc 7.2.0 that my CPU was segfaulting (under ArchLinux though)
I've received my new CPU and I had a go with it against GCC 7.2.0 (with my branch) without any problem on ArchLinux. No more segmentation faults.
@evsh reported an issue with Ubuntu Artful with main branch (since Artful is now using glib 2.26). Maybe he could try this branch and give his feedback?
Okay, now that Artful is released this is really an issue, so I merged the changes. I am confident that faulty Ryzens should fail fine with gcc-7.2.
I will leave this open just in case there there will be problems.
@Oxalin, thank you again for your input! I am looking for someone who helps me to maintain this script. Would you be willing to help out? A problem is that we don't have faulty CPUs to test anymore. We would need to take actions based on user reports.
Hm, it was closed automatically after merging.
Of course, I would happy to help maintain and improve the script.
Alexandre
On Tue, Oct 24, 2017, 02:27 Marc notifications@github.com wrote:
Okay, now that Artful is released this is really an issue, so I merged the changes. I am confident that faulty Ryzens should fail fine with gcc-7.2.
I will leave this open just in case there there will be problems.
@Oxalin https://github.com/oxalin, thank you again for your input! I am looking for someone who helps me to maintain this script. Would you be willing to help out? A problem is that we don't have faulty CPUs to test anymore. We would need to take actions based on user reports.
— You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/suaefar/ryzen-test/pull/18#issuecomment-338887264, or mute the thread https://github.com/notifications/unsubscribe-auth/AASgszKweRaLZWYYyC3tgYI1OWW-N9wnks5svYNbgaJpZM4PzWoh .
Improve warnings and how we handle unsupported distributions. Check if ramdisk already exists and deal accordingly. Move to GCC 7.2.0 source code to fix a bug with systems using glib 2.26.
Cherrypick whatever please you.