From owner-freebsd-questions  Tue Aug 20 23:03:08 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id XAA26821
          for questions-outgoing; Tue, 20 Aug 1996 23:03:08 -0700 (PDT)
Received: from ime.net (ime.net [204.97.248.4])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id XAA26791
          for <questions@freebsd.org>; Tue, 20 Aug 1996 23:03:04 -0700 (PDT)
Received: from kimiko.tcguy.net (buxton-1.ime.net [206.231.148.130]) by ime.net (8.7.4/8.6.12) with SMTP id WAA06591; Tue, 20 Aug 1996 22:03:50 -0400 (EDT)
Message-ID: <321A6F17.2BD4@ime.net>
Date: Tue, 20 Aug 1996 22:06:15 -0400
From: Gary Chrysler <tcg@ime.net>
Reply-To: tcg@ime.net
Organization: The Computer Guy
X-Mailer: Mozilla 3.0b6 (Win95; I)
MIME-Version: 1.0
To: Eric Yagerlener <eyager@novagate.com>
CC: questions@freebsd.org
Subject: Re: Config crashes.  Kernel will not compile.
References: <Pine.BSF.3.91.960820194556.257A-100000@localhost>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

Eric Yagerlener wrote:
> 
> I have a 60 mhz Pentium with a Mercury Chipset.  8 megs of Ram and about
> 25 Megs worth of swap space.   I have FreeBSD version 2.1.0 with
> the generic kernel.  Whenever I try to run config, the program
> will run maybe 2 or 3 seconds, and then it will exit on signal 11.
> (Segmentation Fault.)  I thought that I might be running low on swap, so
> I tried booting up into the single user mode and tried again.  No change
> whatsoever occured.  (Instead it will call it a Memory Fault.)  Some
> people thought that I didn't have enough swap space period to compile a
> kernel.  I mounted an unused partition on the hard drive for use as swap
> and that brought the total to 50 megs.  Still, it didn't seem to make any
> difference.
> 
> I don't know what else could cause trouble.  It could be that the chipset
> is too buggy to do kernel compiles.  Turning off all caching didn't seem
> to cure the problem.  Config could be corrupt, but I don't know how to
> verify that.  I did have great difficulty getting hold of and
> installing the kernel source codes.  I may have to try reinstalling
> them.
> 
> Could anyone tell me if I'm on the right track?
> 
> -- Eric

I had problems like this on a 486 and it turned out to be
wait state settings in CMOS.
Of course finding this after I had already replaced the SIMMS!

Now the machine is back on the original SIMMS and has been
running for several weeks without one problem!
Before I was lucky to make it through a kernel build!

Just thought I would throw it out there.. :)

-Enjoy
Gary
~~~~~~~~~~~~~~~~
Improve America's Knowledge... Share yours
The Borg... Where minds meet
(207) 929-3848