Richard Freeman on 30 Dec 2009 07:25:45 -0800

[Date Prev] [Date Next] [Thread Prev] [Thread Next] [Date Index] [Thread Index]

Re: [PLUG] How To Diagnose System Instability?

On 12/30/2009 10:11 AM, Casey Bralla wrote:
> But wouldn't RAM issues to isolated to individual chips?

That seems likely to me - I'm not sold that you're having RAM problems.

> Also, is it possible that I've built a bunch of defective system libraries
> since they were built with bad RAM?

Anything is possible where bad hardware is concerned (whether it turns 
out to be RAM, motherboard, or CPU).  However, it is not likely to be 
the cause of your problems if you're actually getting errors in memtest 
running from BIOS or from a boot CD.

If you fix your problems just re-emerge system and you should be 
perfectly fine (sure, there is a minute risk that an error in the 
toolchain will propagate, even past the two-stage gcc bootstrap, but 
that seems extremely remote).

The other thing I've done when I've been desperate to rescue a package 
is to just copy the appropriate files from the stage3.  Chances are that 
system packages are available as binaries as well (have never installed 
from binary before, but chances are that its documented on a 
la emerge -k.  Worst case you can probably just do a backup and then 
copy all of a stage 3 over except for /etc and then do an emerge sync 
and end up with a slightly older but otherwise working system.  If you 
use a weekly stage3 you shouldn't have too many issues with that, but 
don't use a two-year-old build or you could have glibc/ABI/etc issues.

And by all means try the forum and lists - gentoo does a good job with 
that (I guess I'm slightly partial)...

Rich (aka rich0@g.o)
Philadelphia Linux Users Group         --
Announcements -
General Discussion  --