From owner-freebsd-hackers  Mon Jul  7 18:40:19 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA20838
          for hackers-outgoing; Mon, 7 Jul 1997 18:40:19 -0700 (PDT)
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA20832
          for <hackers@freebsd.org>; Mon, 7 Jul 1997 18:40:16 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id SAA09549
	for <hackers@freebsd.org>; Mon, 7 Jul 1997 18:39:58 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd009547; Tue Jul  8 01:39:48 1997
Message-ID: <33C19A05.15FB7483@whistle.com>
Date: Mon, 07 Jul 1997 18:38:13 -0700
From: Julian Elischer <julian@whistle.com>
Organization: Whistle Communications
X-Mailer: Mozilla 3.0Gold (X11; I; FreeBSD 2.2-CURRENT i386)
MIME-Version: 1.0
To: hackers@freebsd.org
Subject: Something screwy with 2.2.x?
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I've been seeing sporadic SIG-11 failures on busy machines
with 2.2.2+ (sources from last week.

for example forking off 34 'ping -c 17 -s 500'
(don't ask) will cause failures in random sh and ping processes.

It's a small machine (8MB) so there's paging going on..
Unfortunatl;y the ping is not giving core dumps (why not?)
even wne  not suid root.
the shell was doing so, but as more of the failures are happenning
in ping, I'd like to see that core-file.

Any ideas ?

Am persuing my own inquiries..

julian