Does anyone here use a ryzen ? I got a 1300X recently, and building current rustc - and using that to build firefox - seems to work fine. BUT - I had not bothered to run the rustc testsuite because it takes so long.
But those initial builds of rustc were to install it in /opt - seemed good enough, so I decided to install it in /usr and to see how the test results looked. Disaster. Every time I run the tests, within a couple of minutes I get two traps for invalid opcodes, followed a few minutes later by two segfaults (noted by reading syslog, the tests seem to continue as normal). But if I leave the tests running, about 20 to 30 minutes later (before the end of the tests, according to what got written to the log) the machine reboots. These are all that got logged the first time, nothingrelated to the reboot. Apr 6 06:37:48 origin kernel: [ 3695.201558] traps: backtrace.stage trap invalid opcode ip:7f1e76696498 sp:7ffc6848af80 error:0 in libstd-23815cc482a70678.so[7f1e7663c000+155000] Apr 6 06:37:48 origin kernel: [ 3695.231521] traps: backtrace.stage trap invalid opcode ip:7f76e0ff0498 sp:7ffc2bf46850 error:0 in libstd-23815cc482a70678.so[7f76e0f96000+155000] Apr 6 06:41:17 origin kernel: [ 3903.999612] segfault-no-out: segfault at 0 ip 0000555aa6cd0b69 sp 00007ffeb0d96fa0 error 6 in segfault-no-out-of-stack.stage2-x86_64-unknown-linux-gnu[555aa6ccd000+5000] Apr 6 06:41:23 origin kernel: [ 3910.633482] signal-exit-sta: segfault at 1 ip 000055afe3b44efc sp 00007fffc985f660 error 6 in signal-exit-status.stage2-x86_64-unknown-linux-gnu[55afe3b42000+4000] Apr 6 06:41:26 origin kernel: [ 3913.231883] traps: simd-target-fea trap invalid opcode ip:55b72481e89c sp:7fff97757750 error:0 in simd-target-feature-mixup.stage2-x86_64-unknown-linux-gnu[55b72481b000+7000] Now that I know it will reboot, I've spend some hours trying to work around this (I'm assuming it uses opcodes not valid on Ryzen, but for somiething which is only exercised by the testsuite) - failed completely - and eventually raised an issue. However, I've now looked at rustc-1.22.1 and that too gets the same two traps. so, I'm thinking that I should put a big warning in the book to not run the tests on a Ryzen. But confirmation that the tests segfault on somebody else's ryzen would be conclusive, which is why I'm asking: has anyone already run the rustc tests on a ryzen ? If not, is anybody willing to give it a go on a ryzen ? Waiting for it to reboot is not required, just keep an eye on the system log or journal and stop the tests if the segfaults occur. My machine otherwise seems stable (I replaced the nvidia graphics card with a low-nd radeon because nouveau frequently locked up X, since then it has seemed fine apart from this. And no, I'm not overclocking, the CPU seems to run cool (maximum I've seen was low 50s degrees). ĸen -- In my seventh decade astride this planet, and as my own cells degrade, there are some things I cannot do now: skydiving, marathon running, calculus. I couldn't do them in my 20s either, so no big loss. -- Derek Smalls, formerly of Spinal Tap -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page