You can also pull out all the memory modules except one
and see if it segfaults. If so put another one in and see
what happens. If it doesn't, try another one again until
you find the culprit(s).
On 28 Mar 2003 08:33:27 +0000
Peter Berkenbosch <[EMAIL PROTECTED]> wrote:
On Fri, 2003-03-28 at 03:29, Scott Thomason wrote:
On Thu, 27 Mar 2003 17:12:12 -0800
david mattatall <[EMAIL PROTECTED]> wrote:
> Try pulling out your RAM, scrub the leads with an
eraser and reseed
> them. It worked for me!
You might want to emerge the memtest86 package and use
it to test your memory before you conclude you have bad
RAM, or that you need to "scrub" your leads.
---scott
--
[EMAIL PROTECTED] mailing list
--
I will try to do that, the system clock is also falling
behind.
I'm feeling a bit unlucky with my hardware. Let's hope
nothing's wrong.
Compiling a new kernel also segments ....aarrrgggg
--
[EMAIL PROTECTED] mailing list
