From owner-freebsd-bugs  Tue Jun  5 13:45:24 2001
Delivered-To: freebsd-bugs@hub.freebsd.org
Received: from freefall.freebsd.org (freefall.freebsd.org [216.136.204.21])
	by hub.freebsd.org (Postfix) with ESMTP
	id 70E3A37B403; Tue,  5 Jun 2001 13:45:20 -0700 (PDT)
	(envelope-from iedowse@FreeBSD.org)
Received: (from iedowse@localhost)
	by freefall.freebsd.org (8.11.3/8.11.3) id f55KjKN34876;
	Tue, 5 Jun 2001 13:45:20 -0700 (PDT)
	(envelope-from iedowse)
Date: Tue, 5 Jun 2001 13:45:20 -0700 (PDT)
From: <iedowse@FreeBSD.org>
Message-Id: <200106052045.f55KjKN34876@freefall.freebsd.org>
To: doconnor@gsoft.com.au, iedowse@FreeBSD.org,
	freebsd-bugs@FreeBSD.org
Subject: Re: kern/14033: Data acq process gets stuck in vmopar
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
List-ID: <freebsd-bugs.FreeBSD.ORG>
List-Archive: <http://docs.freebsd.org/mail/> (Web Archive)
List-Help: <mailto:majordomo?subject=help> (List Instructions)
List-Subscribe: <mailto:majordomo?subject=subscribe%20freebsd-bugs>
List-Unsubscribe: <mailto:majordomo?subject=unsubscribe%20freebsd-bugs>
X-Loop: FreeBSD.org

Synopsis: Data acq process gets stuck in vmopar

State-Changed-From-To: open->feedback
State-Changed-By: iedowse
State-Changed-When: Tue Jun 5 13:40:59 PDT 2001
State-Changed-Why: 

Is this still a problem with recent releases? The most common case
of processes getting stuck in 'vmopar' was fixed before 4.2-RELEASE
(nfs_subs.c rev 1.96 + related changes).


http://www.FreeBSD.org/cgi/query-pr.cgi?pr=14033

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