Jason Edson ([EMAIL PROTECTED]) scribbled: > Mark Brier wrote: > >Jason Edson wrote: [snip] > >>I had the same problem when after I got the install done i would > >>reboot then try and "emerge kde". It would get a part of the way done > >>then crap out at diffrent points. I finnally found the problem. I > >>have 2 sticks of 512Mb RAM and I took out one of them and boom, it > >>works great now. I thought it was a heat problem but I guess I just > >>got some bad RAM. Just my 2 cents. > > > >Memtest ran for a day and found nothing. > > > >Rebuilding a brand-spanking new nptlonly. Fingers crossed! > > > I was the one stating that i emerged kde and had the same problem. I > also ran memtest over night and had little or no problems ( i dont > remember) but taking out (or replacing) the 1 ram stick worked. I dont > know why and now I have it back in and the compiling works fine now. I > dont understand why but it does. So I would suggest just trying it so > see if thats the problem. If it's not, good luck figuring out what it is > and please reply if you solve.
memtest86 will find physical errors in your ram, however, it has trouble nailing down transient errors. The transient errors I've seen is when cheap ram is sold as useable at two speeds, but at the higher one you get errors. The cells aren't bad, but the stick has trouble with the faster freq. If bad enough this will manifest itself as bad cells in memtest86, but will be in different, or non-existent areas when memtest86 is re-run. In a nutshell, memtest86 doesn't find all ram errors. Try one stick at a time or swapping out sticks from other machines if your builds keep failing. hth, Cooper. -- gentoo-user@gentoo.org mailing list
