From owner-freebsd-questions Tue Feb 27 13:59:16 2001 Delivered-To: freebsd-questions@freebsd.org Received: from showcase.pdsys.com (showcase.pdsys.com [207.167.12.13]) by hub.freebsd.org (Postfix) with ESMTP id 9943937B71A; Tue, 27 Feb 2001 13:59:06 -0800 (PST) (envelope-from jim@pdsys.com) Received: from jwhitelaw ([139.142.188.35]) by showcase.pdsys.com (Post.Office MTA v3.5.3 release 223 ID# 0-56457U100L100S0V35) with SMTP id com; Tue, 27 Feb 2001 13:18:03 -0700 From: "Jim Whitelaw" To: "Steve Feldman" Cc: "freebsd-stable@freebsd.org" , "freebsd-questions@freebsd.org" Date: Tue, 27 Feb 2001 15:03:30 -0700 Reply-To: "Jim Whitelaw" X-Mailer: PMMail 2000 Professional (2.20.2030) For Windows 2000 (5.0.2195;1) In-Reply-To: <20010227133906.A88572@twincreeks.net> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Re: error in make buildworld Message-ID: <20010227201803093.AAA382@showcase.pdsys.com@jwhitelaw> Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG Yeah, I thought of that but in this case it's suspicious that it happens at the exact same spot in the compile and is preceded by a number of other errors that seem somewhat fatal as well. That is, the errors occur first, then the signal 11. In the past when I've seen a signal 11, everything appears normal until that error at some random point in the compile. In fact the FAQ you refer to below would lead one to believe it's a bug in this particular case: "For example, suppose you're running "make buildworld", and the compile fails while trying to compile ls.c in to ls.o. If you next run "make buildworld" again, and the compile fails in the same place then this is a broken build -- try updating your sources and try again. If the compile fails elsewhere then this is almost certainly hardware." But I can give it different RAM a try anyway, I suppose it can't hurt. I've already tried updating the sources as suggested above. Thanks. On Tue, 27 Feb 2001 13:39:06 -0800, Steve Feldman wrote: >On Tue, Feb 27, 2001 at 10:57:32AM -0700, Jim Whitelaw wrote: >... >> 'make buildworld' fails at the same point every try with this >> error: >> >> cc: {standard input}: cpp: Internal compiler error: program cc1 >> got fatal signal >> 11Assembler messages: > >Check for bad RAM. >Seriously. >I had the same problem a couple of weeks ago >and replacing a bad SIMM cured it. > >Buildworld exercises your RAM better better >than most diagnostics, and signal 11 >is often a sign of memory corruption. > >See http://www.freebsd.org/FAQ/troubleshoot.html#SIGNAL11 >and http://www.bitwizard.nl/sig11/ > > Steve ========================================================================= Jim Whitelaw tel: +1.780.975.1534 jim-at-pdsys-dot-com fax: +1.780.484.9239 Pathways Data Systems Inc. http://www.pdsys.com ========================================================================= "It is best to assume that the network is filled with malevolent entities that will send packets designed to have the worst possible effect." - F.Baker, RFC1812 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message