Date: Thu, 22 Apr 1999 11:47:15 -0700 (PDT) From: Doug White <dwhite@resnet.uoregon.edu> To: Jack Freelander <jack@rabbit.eng.miami.edu> Cc: "James A. Mutter" <jmutter@netwalk.com>, freebsd-questions@FreeBSD.ORG, Jef <jam@winona.cs.miami.edu> Subject: Re: cc in 3.1-STABLE Message-ID: <Pine.BSF.4.03.9904221146520.7869-100000@resnet.uoregon.edu> In-Reply-To: <Pine.BSF.4.10.9904221426480.13540-100000@rabbit.eng.miami.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.03.9904221146520.7869-100000>