From owner-freebsd-current  Fri Mar 19 16:40:29 1999
Delivered-To: freebsd-current@freebsd.org
Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38])
	by hub.freebsd.org (Postfix) with ESMTP id 4E3CD14FDF
	for <freebsd-current@FreeBSD.org>; Fri, 19 Mar 1999 16:40:26 -0800 (PST)
	(envelope-from ambrisko@whistle.com)
Received: from whistle.com (crab.whistle.com [207.76.205.112])
	by alpo.whistle.com (8.9.1a/8.9.1) with ESMTP id QAA68823;
	Fri, 19 Mar 1999 16:33:38 -0800 (PST)
Received: (from ambrisko@localhost)
	by whistle.com (8.9.1/8.9.1) id QAA10236;
	Fri, 19 Mar 1999 16:33:26 -0800 (PST)
	(envelope-from ambrisko)
From: Doug Ambrisko <ambrisko@whistle.com>
Message-Id: <199903200033.QAA10236@whistle.com>
Subject: Re: deadlock in 3.1-RELEASE
In-Reply-To: <199903192159.QAA15741@stiegl.niksun.com> from Andrew Heybey at "Mar 19, 99 04:59:17 pm"
To: ath@niksun.com (Andrew Heybey)
Date: Fri, 19 Mar 1999 16:33:25 -0800 (PST)
Cc: freebsd-current@FreeBSD.org
X-Mailer: ELM [version 2.4ME+ PL29 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-current@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

Andrew Heybey writes:
| When the deadlock does occur, "ps" (in ddb) says that there are many
| processes in vmwait.  The pagedaemon is in an inode wait.  The stack
| trace is in default_halt() (which I assume just means that there are
| no runnable processes).  The system is not short of memory (unless
| "short of memory" means that it is attempting to use it all as a disk
| cache).
| 
| A search of cvs-commiters for "vmwait deadlock" did not reveal (to my
| ignorant eye, anyway) any fixes to -current that would apply to this
| problem.

I have an environment that triggered this in less then 1/2 hour.  Julian
with the help of his friends (ie Matt & Alan) have brought in some changes
from -current that got rid of my problem.  Getting the latest RELENG_3
stuff should fix it.

My processes got stuck on vmwait.

Doug A.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message