From owner-freebsd-questions Thu Apr 22 11:37: 6 1999 Delivered-To: freebsd-questions@freebsd.org Received: from rabbit.eng.miami.edu (rabbit.eng.miami.edu [129.171.33.6]) by hub.freebsd.org (Postfix) with ESMTP id 1ADF41508B for ; Thu, 22 Apr 1999 11:35:57 -0700 (PDT) (envelope-from jack@rabbit.eng.miami.edu) Received: from localhost (jack@localhost) by rabbit.eng.miami.edu (8.9.2/8.9.2) with ESMTP id OAA13557; Thu, 22 Apr 1999 14:33:12 -0400 (EDT) (envelope-from jack@rabbit.eng.miami.edu) Date: Thu, 22 Apr 1999 14:33:12 -0400 (EDT) From: Jack Freelander To: "James A. Mutter" Cc: 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 > 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. > If you do a web search for signal 11 you'll find many a FAQ dedicated > to this problem along with tips for diagnosis and repair. OK. this sounds like a barrell of fun. thanks for your help. PCs suck. -jack To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message