From owner-freebsd-current Mon Jan 22 16:56:19 2001 Delivered-To: freebsd-current@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id D072E37B400 for ; Mon, 22 Jan 2001 16:55:58 -0800 (PST) Received: from zeppo.feral.com (IDENT:mjacob@zeppo [192.67.166.71]) by feral.com (8.9.3/8.9.3) with ESMTP id QAA08883; Mon, 22 Jan 2001 16:55:52 -0800 Date: Mon, 22 Jan 2001 16:55:51 -0800 (PST) From: Matthew Jacob Reply-To: mjacob@feral.com To: Matt Dillon Cc: current@FreeBSD.ORG Subject: Re: loopback nfs hangs now propagated to -stable... In-Reply-To: <200101211954.f0LJsWI15413@earth.backplane.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG I would, except that several attempts to get this to work have failed. It hangs syncing disks, I couldn't get into ddb....I'll keep trying as I can, but, you know, this is really really easy to reproduce- can't you do it? The best I can tell you at the moment is that objcopy is in sleeping on 'sbwait'. -matt > : > :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