On Sun, 2010-02-14 at 18:27 -0500, Michael Scheidell wrote:
> On 2/14/10 9:50 AM, Karsten Bräckelmann wrote:
> > Bad RAM?
>
> well, it didn't start till SA 3.30, and deleting those two rules stopped
> the seg fault and crash..
Well, I've seen bad RAM do strange things like that before. In the
middle of a full desktop build, the build randomly crapped out. Resuming
the build helped, and I eventually got to the end. Yes, the entire time
I was working on that machine with no issue...
It was the description and the identical setup of a bunch of machines,
with *one* only showing the issue that triggered my suspicion.
> more likely a bad ST 504 controller.
Maybe. *shrug* I'd check the RAM nonetheless. You know, it usually just
takes a few seconds for memtest to light up like a Christmas tree if the
RAM is faulty.
--
char *t="\10pse\0r\0dtu...@ghno\x4e\xc8\x79\xf4\xab\x51\x8a\x10\xf4\xf4\xc4";
main(){ char h,m=h=*t++,*x=t+2*h,c,i,l=*x,s=0; for (i=0;i<l;i++){ i%8? c<<=1:
(c=*++x); c&128 && (s+=h); if (!(h>>=1)||!t[s+h]){ putchar(t[s]);h=m;s=0; }}}
