From owner-freebsd-questions  Wed Feb 14 10:23:29 1996
Return-Path: owner-questions
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id KAA04858
          for questions-outgoing; Wed, 14 Feb 1996 10:23:29 -0800 (PST)
Received: from bubba.tribe.com ([205.184.207.7])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id KAA04853
          for <freebsd-questions@freebsd.org>; Wed, 14 Feb 1996 10:23:27 -0800 (PST)
Received: (from archie@localhost) by bubba.tribe.com (8.6.12/8.6.12) id KAA17487 for freebsd-questions@freebsd.org; Wed, 14 Feb 1996 10:22:51 -0800
From: Archie Cobbs <archie@tribe.com>
Message-Id: <199602141822.KAA17487@bubba.tribe.com>
Subject: FreeBSD in 5 megs?
To: freebsd-questions@freebsd.org
Date: Wed, 14 Feb 1996 10:22:49 -0800 (PST)
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-questions@freebsd.org
Precedence: bulk


Hi,

FreeBSD 2.1.0 should be able to run in 5 megs of memory, right?
I just got the following error on a rather minimalist machine
I'm trying to bring up:

  CPU: Cy486DLC (486-class CPU)
    Origin = "Cyrix"
    real memory  = 5242880 (5120K bytes)
    avail memory = 3858432 (3768K bytes)
  Probing for devices on the ISA bus:

  [ ... normal devices come up ... ]

  clearing /tmp
  recording kernel -c changes
  starting daemons: syslogd inetd cron.
  setting ldconfig path: /usr/lib /usr/local/lib
  Feb 14 10:11:35 mini /kernel: pid 5: sh: uid 0: exited on signal 11
  Feb 14 10:11:35 mini init: /bin/sh on /etc/rc terminated abnormally,
    going to single user mode
  Enter pathname of shell or RETURN for sh:
  erase ^H, kill ^U, intr ^C
  # swapinfo -k
  Device      1K-blocks     Used    Avail Capacity  Type
  /dev/wd0b       51200        0    51136     0%    Interleaved
  #

This has happened pretty rarely and randomly, but it definately happens.
In general, some random process gets a signal and dies. This machine is
also booted diskless via NFS sometimes, and this seems to increase the
likelihood of this happening.

My guess is that there's some hardware problem, but this has happened on
a couple of different machines and I'd like to try to eliminate other
possibilities as well.

Thanks for any insights,
-Archie

_______________________________________________________________________________
Archie L. Cobbs, archie@tribe.com  *  Tribe Computer Works http://www.tribe.com