4 ms·
It can be the other hand round: We once had multiple enterprise class server in a data center that suffered from a strange problem. After a couple of days, som
by sllabres 7y ago
It can be the other hand round:
We once had multiple enterprise class server in a data center that suffered from a strange problem.
After a couple of days, sometimes weeks, they stopped working with memory nearly always reported as the culprit.
It took some time to find the true reason, which we discovered with the vendor after many hours of analyzing and swapping hardware.
The error only occurred when the server was lightly loaded and could be mitigated by disabling the CPU C states entirely in the server configuration.
As memory, CPU test or test jobs we had written produced high system load, they never showed any sign of error during test runs because they prevented the CPU from entering higher C states.
- rsecora 7y agoThat shall be the one of the issues with the Xeon E5-26xx[1]. Some state changes produced either reset or unpredictable system behavior. The workaround was disable c-state or patch the microcode when the patch was available. [1] https://www.intel.co.uk/content/www/uk/en/processors/xeon/xeon-e5-v4-spec-update.html https://www.intel.co.uk/content/www/uk/en/processors/xeon/xe...