From owner-freebsd-current Tue Apr 30 9:35:46 2002 Delivered-To: freebsd-current@freebsd.org Received: from damnhippie.dyndns.org (12-253-177-2.client.attbi.com [12.253.177.2]) by hub.freebsd.org (Postfix) with ESMTP id 3F5D037B405 for ; Tue, 30 Apr 2002 09:35:42 -0700 (PDT) Received: from [172.22.42.2] (peace.hippie.lan [172.22.42.2]) by damnhippie.dyndns.org (8.11.6/8.11.6) with ESMTP id g3UGZb453283 for ; Tue, 30 Apr 2002 10:35:37 -0600 (MDT) (envelope-from freebsd@damnhippie.dyndns.org) User-Agent: Microsoft Outlook Express Macintosh Edition - 5.01 (1630) Date: Tue, 30 Apr 2002 10:35:37 -0600 Subject: Re: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 From: Ian To: freebsd-current Message-ID: In-Reply-To: <20020430112848.C229@v-ger.we.lc.ehu.es> Mime-version: 1.0 Content-type: text/plain; charset="US-ASCII" Content-transfer-encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG > From: "Jose M. Alcaide" > Date: Tue, 30 Apr 2002 11:28:48 +0200 > To: current@FreeBSD.ORG > Subject: cc1 crashes with SIGBUS while building XFree86-Server-4.2.0_2 > > I am getting this error while building XFree86-Server-4.2.0_2 on a > recently updated -CURRENT (Mon Apr 29 10:55:43 GMT): > > [snip] > > cpp0: cc: output pipe has been closedInternal compiler error: program cc1 got > fatal signal 10 > I have seen cc1 die like this many many times, and have only ever seen 2 root causes for the death: 1) bad ram 2) you overclocked the cpu or bus just a bit too much cc1 dying on a long complex source module when you've overclocked beyond what your silicon can handle is so reliable a test that it's the first thing I use when trying to find the true speed a new system will run at. If you're not overclocking, then bad ram would make a good second suspect, I had a failing DIMM a couple years ago first manifest as signal 10 and 11 errors in cc1. -- Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message