Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 4 Jan 2006 04:15:26 -0600
From:      Nikolas Britton <nikolas.britton@gmail.com>
To:        Crispy Beef <crispy.beef@ntlworld.com>
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Kernel Compilation...
Message-ID:  <ef10de9a0601040215o1a700779k60f2d27713b080b1@mail.gmail.com>
In-Reply-To: <43BA9432.6090409@ntlworld.com>
References:  <43B951B4.1060601@ntlworld.com> <20060102184137.GI7533@osiris.chen.org.nz> <43BA9432.6090409@ntlworld.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 1/3/06, Crispy Beef <crispy.beef@ntlworld.com> wrote:
> Jonathan Chen wrote:
> > On Mon, Jan 02, 2006 at 04:15:48PM +0000, Crispy Beef wrote:
> >
> >>Hi All,
> >>
> >>Just joined this list.  The last time I used FreeBSD was with 4.6-RELEA=
SE,
> >>so a while ago now.  I have just installed 6.0-RELEASE on my old laptop=
 and
> >>have been configuring the system, am onto the kernel at the moment, hav=
e
> >>followed the traditional method in the FreeBSD handbook.  All works fin=
e
> >>(make depends) until I do 'make' then I get a compilation error as foll=
ows:
> >>
> >>--------------------------------------------------------------------
> >>/usr/src/sys/modules/ata/atapci/../../../dev/ata/ata-chipset.c:617:
> >>internal compiler error: Segmentation fault: 11
> >>Please submit a full bug report,
> >>with preprocessed source if appropriate.
> >
> >
> > Internal compiler errors usually indicate faulty memory. If you rerun
> > your compilation and it fails in the same spot, then it could be
> > software. If the compilations fails in a different area, you've
> > probably got faulty hardward.
>
> It's looking very much like faulty hardware at the moment...bit of a sham=
e
> really.  Have used Gentoo Linux on this machine before (compiling from so=
urce)
> and that's always worked just fine, I only ditched it a couple of weeks a=
go to
> have a play with FreeBSD again.
>
> Also tried the memtest86 util from a floppy, that doesn't even boot prope=
rly
> so looks like it might be a no go.  :-/
>

To rule out hardware problems rebuild the generic kernel using the
virgin GENERIC kernel config file:

0. If you've messed with /etc/make.conf change it back to the defaults!
1. su
2. cd /usr/src/sys/i386/conf
3. rm -r ../compile/GENERIC
4. config GENERIC
5. cd ../compile/GENERIC
6. make depend
7. make
8. make install
9. reboot

If you can't get to step 8 you have a hardware problem (or FreeBSD
wasn't installed correctly, see step 5 below):

(Very Basic/Limited Flow chart)

1. Go into the BIOS and reset everything to their safety defaults
etc., repeat generic kernel build and if it's successful...

2. Pull the Mem, Hard drive, etc. clean/dust/etc. Reinsert etc.,
repeat generic kernel build and if it's successful...

3. Sub Out/Replace Memory, repeat generic kernel build...

4. Wipe (zero out) Hard Drive and Reinstall a virgin copy of FreeBSD 6 from=
 CD:
ftp://ftp.freebsd.org/pub/FreeBSD/ISO-IMAGES-i386/6.0/6.0-RELEASE-i386-disc=
1.iso
MD5 (6.0-RELEASE-i386-disc1.iso) =3D cfe3c1a2b4991edd6a294ca9b422b9d5
Check the MD5 hash before you burn the disc and verify the disc after
it's burned. Hit "A" then "Q" for FDISK and Disklabel and Install only
the "Kern-Developer" Distribution set, don't install the ports system.
repeat generic kernel build...  Oh... and run a defective sector scan
of the hard drive using the diag disk that came with it, you can find
the zero out and diag software on the UBCD CD link below.

5. If you've done steps 1 - 4 and still can't build the kernel your
system is broke, I'll take it off your hands if you'd like. :-)
Also... you may want to start with step 4 then do 1, 2, and 3.

http://www.ultimatebootcd.com/
http://www.ultimatebootcd.com/download.html



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?ef10de9a0601040215o1a700779k60f2d27713b080b1>