AMD Confirms Linux Performance Marginality Problem Affecting Some, Doesn't Affect Epyc / TR
Collapse
X
-
Originally posted by Funks View PostHow did AMD come to the conclusion that ThreadRipper isn't affected by these issues given that it's running the same stepping as the Ryzen chips (B1). Does it just have better QA in general? A manufacturing fix on 2017 Week 25+ chips? A microcode fix?Originally posted by tetsuos View PostHow can AMD be sure the B1 Threadripper is unaffected? What's wrong with the chips which fail with SEGV?
No other fix has been applied from what I can tell.
Originally posted by tetsuos View PostDoes AMD believe we are going to buy any Ryzen chip after this fiasco?
I think AMD could definitely have handled this better (and I mean far better), but what they did is more or less par for the course.
Comment
-
-
suaefar
Originally posted by suaefar View Post
Yes, 8 Gb of RAM is not sufficient to successfully complete the builds.
The output of "journalctl -kf", which is appended to the printed log.
It should also show the OOM killer messages, dosn't it?
Some segfaults are caught by the programs itself and not by the kernel.
Hence, these don't appear in the printed log.
You can always go the build directories and look at the end of the individual log files for the actual reason.
Look through the "build.log" files in the corresponding subfolders of "/mnt/ramdisk/"
It is not impossible but unlikely that this was already due to hitting the memory limit.
tee: /sys/block/zram0/disksize: Device or resource busy
Not knowing what to do about that, I restart the system to fix it.
Comment
-
-
I can't use dmesg because it is completely logged up with input device errors.
I'm running the script with sudo. After several minutes the system memory usage was only 4GB with nothing else running. So far one segfault amidst the noise of evbugs:
[loop-5] Mon Aug 14 12:19:55 CDT 2017 start 0
[loop-5] Mon Aug 14 12:22:00 CDT 2017 build failed
[loop-5] TIME TO FAIL: 130 s
[KERN] Aug 14 12:22:00 ronin kernel: bash[6763]: segfault at 7fa18822d7e8 ip 00007fa187f49330 sp 00007fff63fa3eb8 error 4 in libc-2.24.so[7fa187e20000+193000]
Comment
-
-
Originally posted by janweb View Post
They ask me also to do some pictures of my mainboard and settings. This is all very sad.
Didn't buy this system to overclock and muck around with voltages manually - BS.
Comment
-
-
Originally posted by Funks View Post
They'll then take several more days to get back to you, telling you to up the CORE voltage starting at 1.3625 -> 1.425 testing increasing it in increments of .05V and setting the SOC to 1.1. I personally don't understand why they are making end users tweak anything in the BIOS at default settings (not overclocking).
Didn't buy this system to overclock and muck around with voltages manually - BS.
Comment
-
Comment