Date: Wed, 4 Feb 1998 12:51:09 -0500 From: dlr <dlr@insane.asylum.org> To: dlr <dlr@insane.asylum.org> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: kernel compile error Message-ID: <19980204125109.57281@insane.asylum.org> In-Reply-To: <19980202183230.08286@insane.asylum.org>; from dlr on Mon, Feb 02, 1998 at 06:32:30PM -0500 References: <19980201231330.57003@insane.asylum.org> <Pine.SGI.3.96.980203085349.7503B-100000@tui.pinnacle.co.nz> <19980202183230.08286@insane.asylum.org>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19980204125109.57281>