From owner-freebsd-questions  Thu Aug 14 05:37:13 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id FAA14883
          for questions-outgoing; Thu, 14 Aug 1997 05:37:13 -0700 (PDT)
Received: from portanc.com (portanc.com [206.74.11.18])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA14874
          for <freebsd-questions@FreeBSD.ORG>; Thu, 14 Aug 1997 05:37:10 -0700 (PDT)
Received: from toshi (toshi [69.0.0.203])
	by portanc.com (8.8.5/8.8.5) with SMTP id UAA01151;
	Wed, 13 Aug 1997 20:36:19 GMT
Message-Id: <199708132036.UAA01151@portanc.com>
Comments: Authenticated sender is <david@[69.0.0.25]>
From: "David Edwards" <david@portanc.com>
To: freebsd-questions@FreeBSD.ORG
Date: Thu, 14 Aug 1997 08:31:47 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Pentium 200 Lockup Problem
Reply-to: david@portanc.com
CC: tom@portanc.com, david@portanc.com
Priority: normal
X-mailer: Pegasus Mail for Win32 (v2.53/R1)
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Hi,
Yesterday, I emailed info about FreeBSD 2.2.2  panic-ing on a Pentium
200, 64K mem. ,with a  Number Nine Reality 332 video card.

I am running an Apache Httpd Server, an X window Server, a mail 
server on this system.

The Generic FreeBSD 2.2.2 release was panic-ing and rebooting, 
causing the filesystems to be manually fsck -ed.

I added the following options to the kernel config file, 
and so far the machine has been up for 14 hours, without a panic.


options 	CHILD_MAX=128
options      OPEN_MAX=128
options      "MAXDSIZ=(256*1024*1024)"
options      "DFLDSIZ=(256*1024*1024)"
options      SYSVSHM
options      SYSVSEM
options      SYSVMSG
options     DB_UNATTENDED


I don't know which one of these fixed the problem. But I wanted to 
let you know. 

thanks,
David Edwards
david@portanc.com