From owner-freebsd-questions  Thu Jan 16 01:15:59 1997
Return-Path: <owner-questions>
Received: (from root@localhost)
          by freefall.freebsd.org (8.8.4/8.8.4) id BAA11978
          for questions-outgoing; Thu, 16 Jan 1997 01:15:59 -0800 (PST)
Received: from venus.net (venus.net [205.243.72.10])
          by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id BAA11973
          for <freebsd-questions@FreeBSD.ORG>; Thu, 16 Jan 1997 01:15:57 -0800 (PST)
Received: from lostfork (ve1-p0.venus.net [205.243.75.3]) by venus.net (8.7.1/8.7.3) with SMTP id EAA26564; Thu, 16 Jan 1997 04:19:38 -0500 (EST)
Date: Thu, 16 Jan 1997 04:15:13 -0500 (EST)
From: Andre LeClaire <leclaire@venus.net>
X-Sender: leclaire@lostfork
To: Mark Rollings <darkstar@telcentral.com>
cc: freebsd-questions@FreeBSD.ORG
Subject: Re: Signal 11 on custom build
In-Reply-To: <01054478608016@telcentral.com>
Message-ID: <Pine.BSF.3.91.970116040839.142A-100000@lostfork>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

> 
> After the ircd rebuild,  the system continued to run normally for about
> another 4-5 hours.  Then, the sig 11 was reported again from the kernel.
> 
> As of this writing,  I have diverted back to the GENERIC kernel.  Does
> anyone have any ideas as to why such an error would have occured, or might
> have I commented out a device that might have been needed?
> 
Possibly, but it's difficult to tell without seeing your kernel 
configuration file. You might try putting things back in 'til it works.

Andre