From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 9 19:04:30 2005 Return-Path: Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0445816A4E1 for ; Wed, 9 Mar 2005 19:04:30 +0000 (GMT) Received: from anuket.mj.niksun.com (gwnew.niksun.com [65.115.46.162]) by mx1.FreeBSD.org (Postfix) with ESMTP id 420D943D4C for ; Wed, 9 Mar 2005 19:04:29 +0000 (GMT) (envelope-from jkim@niksun.com) Received: from [10.70.0.244] (daemon.mj.niksun.com [10.70.0.244]) by anuket.mj.niksun.com (8.13.1/8.12.11) with ESMTP id j29J4QJ4093498; Wed, 9 Mar 2005 14:04:28 -0500 (EST) (envelope-from jkim@niksun.com) From: Jung-uk Kim Organization: Niksun, Inc. To: freebsd-amd64@freebsd.org, Aaron Daubman Date: Wed, 9 Mar 2005 14:04:25 -0500 User-Agent: KMail/1.6.2 References: <3e4aa11492a6bd41859f0490f2e94202@gumbysoft.com> In-Reply-To: MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200503091404.25226.jkim@niksun.com> X-Virus-Scanned: ClamAV 0.83/758/Wed Mar 9 07:03:56 2005 on anuket.mj.niksun.com X-Virus-Status: Clean Subject: Re: Consistant buildworld Segmentation fault at '===> gnu/usr.bin/cc/cpp' after latest RELENG_5 cvsup X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 19:04:30 -0000 On Wednesday 09 March 2005 01:50 pm, Aaron Daubman wrote: > Hi Doug, > > > > ===> gnu/usr.bin/cc/cpp > > > Segmentation fault (core dumped) > > > *** Error code 139 > > > > [...] > > > > The typical reason for segfaults is bad hardware. A v20z is a > > pretty decent server class machine, though, so unless its > > suffering from an undetected condition it should scream bloody > > murder if something goes bad. This is assuming it has ECC memory > > and you aren't ignoring that big yellow "maintenance" light that > > comes on when something bad happens, like a fan going down. > > > > Can you get into the LOM and check the environmentals? > > Everything is showing up as "Nominal" status. > One note that might make a difference: > The system is a Dual Opteron - not single. I was going by dmesg > output (and since GENERIC is non-SMP...), not on what I had > actually ordered (or LOM status showed ;-). > > Also, isn't segfault usually only indicative of hardware failure > when it does not reliably occur at the exact same spot? > > I should mention that this box was running some fairly intensive > network management software under Windows 2003 server for a month > or so solid as well - which would make me lean away from hardware > faults... > > Any suggestions as to what to change HT settings to - or if that's > a worthwhile avenue to go down? Can you try again without /etc/make.conf? Jung-uk Kim > Thanks again, > ~Aaron