From owner-freebsd-hackers  Tue Jun 10 20:00:15 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id UAA24057
          for hackers-outgoing; Tue, 10 Jun 1997 20:00:15 -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 UAA24052
          for <hackers@freebsd.org>; Tue, 10 Jun 1997 20:00:11 -0700 (PDT)
Received: (from daemon@localhost)
	by alpo.whistle.com (8.8.5/8.8.5) id TAA02867
	for <hackers@freebsd.org>; Tue, 10 Jun 1997 19:58:33 -0700 (PDT)
Received: from current1.whistle.com(207.76.205.22)
 via SMTP by alpo.whistle.com, id smtpd002863; Wed Jun 11 02:58:25 1997
Message-ID: <339E1415.446B9B3D@whistle.com>
Date: Tue, 10 Jun 1997 19:57:25 -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: hangs in FreeBSD2.2
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

We have been seeing occasional hangs (processes hanging)
on our 2.2 (a few months old) kernels

the mechanism is:

process a does vfork() and waiths with wchan = "ppwait"
child waits with wchan of "kmaw".

(in kmem_alloc_wait())

without going into great detail,
can you say if anything has been done 
recently that  would aleviate this problem?
and is htere a tuning parameter that would build more
 of whatever it is that is running short?


we end up with all processes haung (from csh)

I'm off home now but If you guys don't have an easy answer off the top
of your heads, I'll spend real energy on it tomorrow.

thanks

julian