From owner-freebsd-amd64@FreeBSD.ORG Wed Mar 9 18:50:05 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 344AD16A4DA for ; Wed, 9 Mar 2005 18:50:05 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id C8A3343D5D for ; Wed, 9 Mar 2005 18:50:04 +0000 (GMT) (envelope-from daubman@gmail.com) Received: by wproxy.gmail.com with SMTP id 69so381803wri for ; Wed, 09 Mar 2005 10:50:04 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=CtJXU2n/fdr4EksKvoCW0W6pkkPcULvPkTFqlNXKAXe1Uk2mCMYhZcqmL1hcKfjUnjnNxyNubAb9nI1au22qXlPmb96pTmQpNQLgw63rodOvKihKb/HRcs+ti6WSmhYEcGQSGSBpcY/gPdek+TIzz6xRXyDl5zXSeaDY4KLZsTc= Received: by 10.54.81.17 with SMTP id e17mr191384wrb; Wed, 09 Mar 2005 10:50:03 -0800 (PST) Received: by 10.54.2.59 with HTTP; Wed, 9 Mar 2005 10:50:03 -0800 (PST) Message-ID: Date: Wed, 9 Mar 2005 13:50:03 -0500 From: Aaron Daubman To: Doug White In-Reply-To: <3e4aa11492a6bd41859f0490f2e94202@gumbysoft.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <3e4aa11492a6bd41859f0490f2e94202@gumbysoft.com> cc: freebsd-amd64@freebsd.org 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 Reply-To: Aaron Daubman 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 18:50:05 -0000 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? Thanks again, ~Aaron