From owner-freebsd-current  Sun Sep 10 11:10:10 1995
Return-Path: current-owner
Received: (from majordom@localhost)
          by freefall.freebsd.org (8.6.12/8.6.6) id LAA14206
          for current-outgoing; Sun, 10 Sep 1995 11:10:10 -0700
Received: from cps201.cps.cmich.edu (cps201.cps.cmich.edu [141.209.20.201])
          by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id LAA14200
          for <freebsd-current@freebsd.org>; Sun, 10 Sep 1995 11:10:09 -0700
Received: from cps201 (cps201.cps.cmich.edu [141.209.20.201]) by cps201.cps.cmich.edu (8.6.12/8.6.12) with SMTP id OAA15330; Sun, 10 Sep 1995 14:10:10 -0400
Date: Sun, 10 Sep 1995 14:10:08 -0400 (EDT)
From: Mail Archive <archive@cps.cmich.edu>
X-Sender: archive@cps201
To: David Greenman <davidg@Root.COM>
cc: John Capo <jc@irbs.com>, roberto@keltia.freenix.fr,
        freebsd-current@freebsd.org
Subject: Re: sig 11 
In-Reply-To: <199509092031.NAA00235@corbin.Root.COM>
Message-ID: <Pine.SUN.3.91.950910140903.15242B-100000@cps201>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: current-owner@freebsd.org
Precedence: bulk

On Sat, 9 Sep 1995, David Greenman wrote:

> 
>    Okay, everyone else has reported back that the problems have gone away
> after rebuilding everything. The only remaining report of sig 11 type of
> trouble is yours. Can you send me more information about your system, a
> "dmesg" would be useful, for example. Also, when was the last time you
> updated your sources? It's possible that the update you did was during a
> time when changes were being made and thus the changes may be incomplete.
> 

Whooops no it wasn't sed still cores on the new kernel it doesn't on the 
old release kernel...

-current kernel looks to be hosed as of a 4pm EST sup yesterday...