[ale] compiling kernel - disappearing segfaults
John Wells
jbwellsiv at yahoo.com
Sun Feb 17 16:51:14 EST 2002
Sheesh...more ram problems.
I have not found a utility that will accurately
identify RAM probs. I use crucial tech. ram
exclusively and have found them great in the past.
They'll take it back if I identify the RAM as a
problem, but it's a week to two week turnaround and I
don't want to do without the machine if possible. Are
there any end-all be-all utilities out there that will
identify bad RAM once and for all?
Thanks for the help!
John
--- Joseph A Knapka <jknapka at earthlink.net> wrote:
> John Wells wrote:
> >
> > While compiling 2.4.9, I would get an occasional
> > segfault. However, rerunning make would cause the
> > segfault to disappear and the compile would
> continue.
> >
> > What's going on here?
>
> Could easily be bad RAM. When the compiler starts
> hitting
> a damaged page hard, you get a segfault; restarting
> the build pretty much ensures that the bad page
> won't be used the same way for a while, so the
> build gets a little further along each time you
> run make.
>
> Cheers,
> -- Joe
> "I should like to close this book by sticking out
> any part of my neck
> which is not yet exposed, and making a few
> predictions about how the
> problem of quantum gravity will in the end be
> solved."
> --- Physicist Lee Smolin, "Three Roads to Quantum
> Gravity"
>
> ---
> This message has been sent through the ALE general
> discussion list.
> See http://www.ale.org/mailing-lists.shtml for more
> info. Problems should be
> sent to listmaster at ale dot org.
>
__________________________________________________
Do You Yahoo!?
Yahoo! Sports - Coverage of the 2002 Olympic Games
http://sports.yahoo.com
---
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.
More information about the Ale
mailing list