On 01/08/2014 11:39:21 PM, Stefan G. Weichinger wrote:
Am 08.01.2014 19:47, schrieb Grant Edwards:
> On 2014-01-08, Stefan G. Weichinger <[email protected]> wrote:
>
>> Looking forward to some clever suggestions ;-)
>
> Well, I'd start by running memtest86 overnight just to eliminate the
> possibility of marginal memory. But, if memory serves, this is a
> remote server at a customer site -- so that may not be a viable
> option.
Sure. Good suggestion. I would do that if I had physical access to the
server ... for now I don't. And I assume the box would behave much
more
problematic if the memory was faulty.
You can use sys-apps/memtester without physical access to the machine.
I had cases where memtester found errors which memtest86 didn't.
One of these cases was a machine which probably had a cache coherence
problem
since the error showed up only when more than one process ran memtester.
Replacing the CPU but not the memory fixed that problem.
Did you try www.sysresccd.org/ version 3.8.1? I'm not sure if it is
based on
glibc-2.17, yet.
Helmut.
