From owner-freebsd-current  Wed Oct 15 22:10:45 1997
Return-Path: <owner-freebsd-current>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA05034
          for current-outgoing; Wed, 15 Oct 1997 22:10:45 -0700 (PDT)
          (envelope-from owner-freebsd-current)
Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA05027
          for <freebsd-current@FreeBSD.ORG>; Wed, 15 Oct 1997 22:10:42 -0700 (PDT)
          (envelope-from bde@zeta.org.au)
Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.7/8.6.9) id PAA08005; Thu, 16 Oct 1997 15:09:25 +1000
Date: Thu, 16 Oct 1997 15:09:25 +1000
From: Bruce Evans <bde@zeta.org.au>
Message-Id: <199710160509.PAA08005@godzilla.zeta.org.au>
To: freebsd-current@FreeBSD.ORG, j@uriah.heep.sax.de
Subject: Re: lockmgr panic
Sender: owner-freebsd-current@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>Speaking of bandaids, would anybody mind me committing Mr. KATO's
>fix/hack?  (Of course, unless he's going to commit it himself.)  The
>patch seems to solve the vn(4) lockmgr problem.

I think it substitutes panics with deadlock possibilities.  Perhaps
the deadlocks are rare.

>I haven't made a release on a 2.2.5-BETA system lately.  If the
>problem there is the same, i would vote for moving the fix there as

I think the problem is the same but the symptoms are worse - endless
recursion and at best a panic for a double fault.

Bruce