From owner-freebsd-current Sun Jan 21 11:54:50 2001 Delivered-To: freebsd-current@freebsd.org Received: from earth.backplane.com (earth-nat-cw.backplane.com [208.161.114.67]) by hub.freebsd.org (Postfix) with ESMTP id E703437B400 for ; Sun, 21 Jan 2001 11:54:33 -0800 (PST) Received: (from dillon@localhost) by earth.backplane.com (8.11.1/8.9.3) id f0LJsWI15413; Sun, 21 Jan 2001 11:54:32 -0800 (PST) (envelope-from dillon) Date: Sun, 21 Jan 2001 11:54:32 -0800 (PST) From: Matt Dillon Message-Id: <200101211954.f0LJsWI15413@earth.backplane.com> To: Matthew Jacob Cc: current@FreeBSD.ORG Subject: Re: loopback nfs hangs now propagated to -stable... References: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG : :The loopback nfs hangs that have been with us for a month have now propagated :to -stable. Can you break into DDB and get a 'ps' and a kernel core? There are a bunch of things it could be, including possibly my low-memory deadlock code (which concentrated more on UFS and not so much on NFS), though my low-memory deadlock code was committed all the way back in december (12/29). The only recent commit was to fix an O_EXCL bug, and I doubt that could cause a loopback deadlock. The cause could also be related to MFC's (not by me) related to the network stack, which are more recent. There isn't much in the cvs logs that I can see as having caused the problem to occur only recently. -Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message