Helmut Jarausch wrote:
Dale, I have better experience with sys-apps/memtester for catching
memory errors - though running it over night. You can tell it what to
test.
Furthermore I had one machine (an AMD Phenom II) where I got random
errors though all memory tests went through without a problem.
I suspected a cache coherence bug since this was quad core processor.
Once, I have replaced this CPU only, i.e. with the same memory, the
spook was over.
Therefore, if you have a multi-core CPU, run memtester simultaneously
(on different parts of the memory) as many times as you have cores.
I hope, this helps,
Helmut.
I'm going to keep this in mind and I'll run memtester here in a bit. I
booted a USB stick and it ran a long time with no problem. I took a nap
and when I got back up, it was still running. It may still be hardware
but this is a good sign. I would rather it be a bad version of gcc, bad
kernel or something than bad hardware. I can update those easily
enough. I have had 30 days of uptime on this specific kernel tho so I
sort of doubt it is that. Still, it could be anything.
I kind of suspect the ram tho. When I added that, I had it to reboot
itself. Before that, solid as a rock. I may just disconnect and
reconnect everything later on too. Just in case I pulled something
slightly off when installing the ram.
Thanks.
Dale
:-) :-)
