From owner-freebsd-current Wed Apr 26 22:50:49 2000 Delivered-To: freebsd-current@freebsd.org Received: from turtle.looksharp.net (cc360882-a.strhg1.mi.home.com [24.2.221.22]) by hub.freebsd.org (Postfix) with ESMTP id DD06537BE64 for ; Wed, 26 Apr 2000 22:50:46 -0700 (PDT) (envelope-from bsdx@looksharp.net) Received: from localhost (bsdx@localhost) by turtle.looksharp.net (8.9.3/8.9.3) with ESMTP id BAA53964 for ; Thu, 27 Apr 2000 01:51:34 -0400 (EDT) (envelope-from bsdx@looksharp.net) Date: Thu, 27 Apr 2000 01:51:33 -0400 (EDT) From: Adam To: current@freebsd.org Subject: Re: cc1 sig 11'ing recently? In-Reply-To: <003c01bfafb6$e138d4d0$0301a8c0@chaos> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 26 Apr 2000, Ron Klinkien wrote: >> > Any getting these too? >> > >> > ild-tools >> > cd /usr/src/bin/sh; make build-tools >> > cc -O -pipe -DSHELL -I. -I/usr/src/bin/sh -Wall -Wformat -c >> > /usr/src/bin/sh/mkinit.c >> > cc: Internal compiler error: program cc1 got fatal signal 11 >> >> Only people with dodgy memory or cache (probably memory). > >Or dodgy CPU's like some of the AMD K6/233 ones, when you install more than >32Mb memory. > >I myself got bitten by this bug yesterday ;( > I have also seem bad cyrix chips cause this - it drove me nuts because I happened to grab a spare cpu which happened to be faulty in the same way from the spare tray and it lead me to building an almost complete clone of the misbehaving computer before I decided to try another cpu :/ Ended up with the original bad and TWO bad cpu's from the spare tray before I found one that worked :) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message