Hmm, I got tired after about 15 mins of testing with no errors, but decided to reload the 'safe' bios defaults and underclocked my memory to 100 mhz from 133. It just finished PERL without errors. I've run my ram at 133 since I got this board, and I guess this explains the hard locks (only 2 before sorceror). My system never got above around 300 megs memory usage, but every time it hard locked I had multiple X sessions or a bunch of programs open. Sorcerer uses /dev/shm very heavily during the compiles, they require 1 gig combined ram/swap.
I'll post back if I am able to narrow down the problem. I have 1 NEC PC133 dimm and 1 Crucial PC133 dimm. I think the problem is more likely that the cpu ran on a 100mhz ddr bus, and ram on 133 sdr (SIS 735 chipset). Quoting Paul Sack <[EMAIL PROTECTED]>: > Today at 11:32pm, [EMAIL PROTECTED] expounded: > > ++ I was having some issues with debian unstable, and decided to give > sorceror > ++ linux a try, but it keeps locking my machine up during the initial > package > ++ compiles. The kernel compiled quickly with no errors, so I know gcc > is at least > ++ partially functional, but I wouldn't rule out 'cc' as the culprit. > > A lockup or SIGSEGV during compilation most often means that you have > faulty RAM. Look at memtest-86 <http://www.teresaudio.com/memtest86/> > or > another memory test. (I would advise against using any that run on top > of > an OS.) > > Good luck with all of that. > > -Paul > > -- > Corrupt, adj.: > In politics, holding an office of trust or profit. > > _______________________________________________ Siglinux mailing list [EMAIL PROTECTED] http://www.utacm.org/mailman/listinfo/siglinux
