From owner-freebsd-stable  Tue Oct 14 07:34:50 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id HAA20249
          for stable-outgoing; Tue, 14 Oct 1997 07:34:50 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: from serge.jbj.org (serge.JBJ.ORG [198.49.244.129])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA20241
          for <stable@FreeBSD.ORG>; Tue, 14 Oct 1997 07:34:47 -0700 (PDT)
          (envelope-from serge@jbj.org)
Received: (from serge@localhost) by serge.jbj.org (8.8.6/8.6.12) id KAA05328; Tue, 14 Oct 1997 10:33:15 -0400 (EDT)
Date: Tue, 14 Oct 1997 10:33:15 -0400 (EDT)
Message-Id: <199710141433.KAA05328@serge.jbj.org>
From: Serge Pashenkov <serge@jbj.org>
To: joerg_wunsch@interface-business.de
CC: stable@FreeBSD.ORG
In-reply-to: <19971014111611.43194@interface-business.de> (message from J
	Wunsch on Tue, 14 Oct 1997 11:16:11 +0200)
Subject: Re: 2.2-stable NFS panic
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

Look at kern/4501 problem report, I think it's te same. There is a
patch for nfs_vfsops.c there, it fixes the panic, but I'm not sure it
fits into the grand schema of things.

Hope that helps,

	serge