From owner-freebsd-questions@FreeBSD.ORG  Fri Nov 26 19:13:29 2004
Return-Path: <owner-freebsd-questions@FreeBSD.ORG>
Delivered-To: freebsd-questions@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id DB59416A4CE
	for <freebsd-questions@freebsd.org>;
	Fri, 26 Nov 2004 19:13:29 +0000 (GMT)
Received: from S3.cableone.net (smtp3.cableone.net [24.116.0.229])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 91B1D43D4C
	for <freebsd-questions@freebsd.org>;
	Fri, 26 Nov 2004 19:13:29 +0000 (GMT)
	(envelope-from v.velox@vvelox.net)
Received: from vixen42.24-119-122-191.cpe.cableone.net (unverified
	[24.119.122.25]) 
	by S3.cableone.net (CableOne SMTP Service S3) with ESMTP id 2390653 
	for multiple; Fri, 26 Nov 2004 12:20:37 -0700
Date: Fri, 26 Nov 2004 13:12:15 -0600
From: Vulpes Velox <v.velox@vvelox.net>
To: Jonathon McKitrick <jcm@FreeBSD-uk.eu.org>
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>
X-Mailer: Sylpheed-Claws 0.9.12b (GTK+ 1.2.10; i386-portbld-freebsd5.3)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
X-Abuse-Info: Send abuse complaints to abuse@cableone.net
cc: freebsd-questions@freebsd.org
Subject: Re: Is this a sign of memory going bad?
X-BeenThere: freebsd-questions@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: User questions <freebsd-questions.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-questions>
List-Post: <mailto:freebsd-questions@freebsd.org>
List-Help: <mailto:freebsd-questions-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-questions>,
	<mailto:freebsd-questions-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 26 Nov 2004 19:13:30 -0000

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# 
>