What's the current state of ryzen segfaults?
>>61621151
forced meme/10
Using that github test? Intel crashes there too, both are useless, get a SPARC or POWER8
>>61621151
VirtualBox was updated.
>>61621151
>What's the current state
- Very few people seem to care (I'm pretty sure it'd be plastered all over news sites otherwise)
- This is the only active discussion of it: https://community.amd.com/thread/215773?start=450&tstart=0
- There are like ~20 people in this thread, so, again, not that much
- Still there is no definitive solution to it. Some speculate it's an Opcache issue, some say it's only certain RAM/mobo incompatibilities, some say newer GCC versions fixed it (others don't)
- It's not clear whether it is a bug at all, and if it is whether it can be fixed via microcode or it's an actual silicon erratum because AMD has been staying silent all the while
>>61621887
I'd pass any judgment until we get B2 silicon (threadripper)
what is it?
does it affect literally anyone at all?
if yes, who specifically?
Or is it just another non-issue that you want to cling onto anyway because you need to constantly justify your purchase that you'll regret if you know that there is an alternative that is literally better in every single way?
>>61621809
>POWER8
kek, no
funny how intel shills magically turn into tech experts when a competitor is better
>>61622201
>moooooooom, the shills made my ryzen segault again
>>61621809
>get a SPARC or POWER8
>>61622179
What's the matter? Can't handle SMT8?
>itt fanbois desperately try to justify supporting a failed company
>>61621735
It isnt forced if you run virtualization software like ESXi and dont want to have to disable SMT
>>61621887
>Very few people seem to care
Because no one uses AMD in the enterprise space
>This is the only active discussion of it
There is a lot more you fanboi
https://www.google.com/search?q=ryzen+esxi+site%3Avmware.com&ie=utf-8&oe=utf-8
>>61623090
can't handle context switch
>>61623538
We're not talking about Nvidia here.