Posts by AlphaC
|
1)
(Message 5438)
Posted 9 Jul 2017 by AlphaC Post: I don't see the benefit in hoarding units unless A. All you crunch is Asteroids@home and have zero power saving features (i.e. fixed voltage, overclocked, NO C-STATES) B. it's the Pentathlon and you want to build a massive bunker C. your internet goes down days at a time regularly |
|
2)
(Message 5437)
Posted 8 Jul 2017 by AlphaC Post: Haven't been crunching A@H in bit , are those errors avx or the sse2/sse3 ones? I started crunching A@H again, in Virtualbox, and I had 2 avx WUs error out but not all of them. |
|
3)
(Message 5436)
Posted 8 Jul 2017 by AlphaC Post: Seems some avx WUs error out on my Ryzen 7. A@H is running in Virtualbox in Linux Mint + Manjaro guest OSes. Any way to find out why? If not can the avx WUs be disabled from options? Every sse2 or sse3 WU validated. edit: both times had <core_client_version>7.6.31</core_client_version> <![CDATA[ <message> process exited with code 193 (0xc1, -63) </message> <stderr_txt> SIGSEGV: segmentation violation If a project admin can PM me I can provide more details |