From owner-freebsd-stable@FreeBSD.ORG Sat Dec 4 21:42:33 2004 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 3F1C416A4CE for ; Sat, 4 Dec 2004 21:42:33 +0000 (GMT) Received: from smtp.servingpeace.com (servingpeace.com [69.55.225.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id E629F43D58 for ; Sat, 4 Dec 2004 21:42:32 +0000 (GMT) (envelope-from sam@servingpeace.com) Received: from [10.0.0.2] (adsl-68-122-12-222.dsl.pltn13.pacbell.net [68.122.12.222]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by smtp.servingpeace.com (Postfix) with ESMTP id 8E362B96FC for ; Sat, 4 Dec 2004 13:42:32 -0800 (PST) Message-ID: <41B22F48.4070203@servingpeace.com> Date: Sat, 04 Dec 2004 13:42:32 -0800 From: Sam Nilsson User-Agent: Mozilla Thunderbird 1.0RC1 (Macintosh/20041201) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-stable@freebsd.org References: <20041204202322.GD12622@crom.vickiandstacey.com> <20041204213345.44dc9e1b.gstewart@bonivet.net> In-Reply-To: <20041204213345.44dc9e1b.gstewart@bonivet.net> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: make buildworld fails for 5-Stable cvsup'd today X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 04 Dec 2004 21:42:33 -0000 Godwin Stewart wrote: > On Sat, 4 Dec 2004 20:23:22 +0000, Stacey Roberts > wrote: > > >>internal compiler error: Segmentation fault > > > Faulty RAM, maybe? > > A machine throwing a segfault is fairly characteristic of a CPU overheating > and/or of a faulty RAM stick. > I'll chime in here (again!) and mention that I was having the same problem yesterday trying to make buildworld (5.3 Release). It turned out that one of my RAM modules was bad and the bios must not have fully mapped out all of the bad parts. After removing the offending memory module (through trial and error), freebsd is as stable as ever and my builds went flawlessly. So Godwin is probably right. It is probably bad RAM. - Sam