Date: Fri, 26 Nov 2004 13:12:15 -0600 From: Vulpes Velox <v.velox@vvelox.net> To: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> Cc: freebsd-questions@freebsd.org Subject: Re: Is this a sign of memory going bad? Message-ID: <20041126131215.4faca6b4@vixen42.24-119-122-191.cpe.cableone.net> In-Reply-To: <20041125201623.GA72323@dogma.freebsd-uk.eu.org> References: <20041125201623.GA72323@dogma.freebsd-uk.eu.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Not seen this exact error before, but I recently had a mobo go bad that would produce errors with compiles and ect before it would hardlock. It would go flaky under heavy I/O. I tested for it by swapping out the proc and ram. On Thu, 25 Nov 2004 20:16:23 +0000 Jonathon McKitrick <jcm@FreeBSD-uk.eu.org> wrote: > > This is what I get from make buildworld. I've gotten signal 10, 11, > and now 5. > > Is this bad memory? > > > S -DYP -c /usr/src/lib/libc/../libc/net/res_debug.c -o res_debug.o > cc -O -pipe -DLIBC_RCS -DSYSLIBC_RCS -I/usr/src/lib/libc/include > -D__DBINTERFACE_PRIVATE -DINET6 -DPOSIX_MISTAKE > -I/usr/src/lib/libc/../libc/locale -DBROKEN_DES -DYP -c > /usr/src/lib/libc/../libc/net/res_init.c -o res_init.o > cc: Internal compiler error: program cc1 got fatal signal 5 > *** Error code 1 > > Stop in /usr/src/lib/libc. > *** Error code 1 > > Stop in /usr/src/lib. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > *** Error code 1 > > Stop in /usr/src. > neptune# >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20041126131215.4faca6b4>