From owner-freebsd-hackers Wed Apr 25 7:28:36 2001 Delivered-To: freebsd-hackers@freebsd.org Received: from salmon.maths.tcd.ie (salmon.maths.tcd.ie [134.226.81.11]) by hub.freebsd.org (Postfix) with SMTP id E838C37B423 for ; Wed, 25 Apr 2001 07:28:32 -0700 (PDT) (envelope-from iedowse@maths.tcd.ie) Received: from walton.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id ; 25 Apr 2001 15:28:31 +0100 (BST) To: Oliver Cook Cc: freebsd-hackers@freebsd.org, iedowse@maths.tcd.ie Subject: Re: open (vfs_syscalls.c:994) && NFS In-Reply-To: Your message of "Wed, 25 Apr 2001 15:08:52 BST." <20010425150852.B37512@mutare.noc.clara.net> Date: Wed, 25 Apr 2001 15:28:31 +0100 From: Ian Dowse Message-ID: <200104251528.aa35127@salmon.maths.tcd.ie> Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In message <20010425150852.B37512@mutare.noc.clara.net>, Oliver Cook writes: >After about a week there are hundreds of stuck >httpd processes in exactly this state. It is not >possible to attach to them, but information can >be gleaned from a kernel backtrace: Could you post the full output of "ps axl" on one of these machines? In this output, search for other odd process states, especially "vmopar", and include a gdb backtrace from these processes too. This sounds like a problem I described in http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=243599+249172+/usr/local/www/db/text/2000/freebsd-hackers/20001022.freebsd-hackers (split URL is http://www.FreeBSD.org/cgi/getmsg.cgi?fetch=243599+249172+ /usr/local/www/db/text/2000/freebsd-hackers/20001022.freebsd-hackers in case the above doesn't work) Ian To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message