From owner-freebsd-questions Wed Feb 4 09:50:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA28310 for questions-outgoing; Wed, 4 Feb 1998 09:50:25 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from insane.asylum.org ([208.13.58.137]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA28303 for ; Wed, 4 Feb 1998 09:50:19 -0800 (PST) (envelope-from dlr@insane.asylum.org) Received: (from dlr@localhost) by insane.asylum.org (8.8.6/8.8.6) id MAA28456; Wed, 4 Feb 1998 12:51:10 -0500 (EST) Message-ID: <19980204125109.57281@insane.asylum.org> Date: Wed, 4 Feb 1998 12:51:09 -0500 From: dlr To: dlr Cc: freebsd-questions@FreeBSD.ORG Subject: Re: kernel compile error References: <19980201231330.57003@insane.asylum.org> <19980202183230.08286@insane.asylum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74e In-Reply-To: <19980202183230.08286@insane.asylum.org>; from dlr on Mon, Feb 02, 1998 at 06:32:30PM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG X-To-Unsubscribe: mail to majordomo@FreeBSD.org "unsubscribe questions" On Mon, Feb 02, 1998 at 06:32:30PM -0500, dlr wrote: > > The last time this started happening to me, it got traced to bad memory > > chips. > > > I put a new cpu in (intel P166) and am getting the same errors. It is now > intermittant as i have gotten it to compile a few times. I get no errors on > bootup that there is a bad simm. i have 64meg edo(2x32). It is going to be the > next thing i change out tonight. > > This is the new error that i got today > > > OSFS -DNFS -DFFS -DINET -DKERNEL ../../dev/vx/if_vx.c > cc: Internal compiler error: program cc1 got fatal signal 6 > *** Error code 1 > > It is also not wanting to compile things out of the ports section, which also > leads me to believe it must be a hardware problem. I've reinstalled Freebsd 4 > times this weekend (2x with 2.2.5 and 2x with 2.2.2). Initially i went with > 2.2.5 but i'm getting the same thing with all four installs.... > > thanks for the tip on the simms....i'll report back when i change them out. I > tried switching them in the sockets and reseating to no avail. This did appear to be a bad simm. I changed the memory out and it is working fine now. I put the "bad" memory into a windoz box, that way when it crashes i can just blame windoz. dave