From owner-freebsd-questions Thu Apr 22 11:50:59 1999 Delivered-To: freebsd-questions@freebsd.org Received: from resnet.uoregon.edu (resnet.uoregon.edu [128.223.144.32]) by hub.freebsd.org (Postfix) with ESMTP id 873301508B for ; Thu, 22 Apr 1999 11:50:04 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Received: from localhost (dwhite@localhost) by resnet.uoregon.edu (8.8.8/8.8.8) with ESMTP id LAA03094; Thu, 22 Apr 1999 11:47:16 -0700 (PDT) (envelope-from dwhite@resnet.uoregon.edu) Date: Thu, 22 Apr 1999 11:47:15 -0700 (PDT) From: Doug White To: Jack Freelander Cc: "James A. Mutter" , freebsd-questions@FreeBSD.ORG, Jef Subject: Re: cc in 3.1-STABLE In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 22 Apr 1999, Jack Freelander wrote: > > What about an error when cc dies? What you're describing sounds like > > the dreaded "Signal 11" most commonly caused by bad hardware, usually > > RAM. > > that sounds unfortunately familiar. one sec .... > cc: Internal compiler error: program cc1 got fatal signal 11 > > great. just great. > > > Are you using PC100 RAM in this machine? Do you have a way to verify > > that? > > yes, we are. The machine is brand new -- new motherboard, new chip, new > RAM. Is this UNQUESTIONALBY a RAM problem? I need to know for certain > because this hardware will have to be returned in a hurry if that is truly > the case. Yup -- or CPU cache, but it's usually RAM. Doug White Internet: dwhite@resnet.uoregon.edu | FreeBSD: The Power to Serve http://gladstone.uoregon.edu/~dwhite | www.freebsd.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message