From owner-freebsd-current Sun Oct 5 18:01:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21290 for current-outgoing; Sun, 5 Oct 1997 18:01:10 -0700 (PDT) (envelope-from owner-freebsd-current) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21285 for ; Sun, 5 Oct 1997 18:01:06 -0700 (PDT) (envelope-from tlambert@usr05.primenet.com) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id SAA01035; Sun, 5 Oct 1997 18:01:05 -0700 (MST) From: Terry Lambert Message-Id: <199710060101.SAA01035@usr05.primenet.com> Subject: Re: lock manager panics To: ktsin@acm.org (Sin Key Teck) Date: Mon, 6 Oct 1997 01:01:04 +0000 (GMT) Cc: current@FreeBSD.ORG In-Reply-To: <199710040851.QAA08511@cc621.ntu.ac.sg> from "Sin Key Teck" at Oct 4, 97 04:51:25 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I have installed 3.0-971003-SNAP and the lock manager still panics on shutdown > if quota is enabled. I believe the problem has persisted since the SMP code > was merged into 3.0. > > Is there a problem with the lock manager or is it due to misconfiguration? There are a couple of problems with the lock manager because of indeterminate state transitions. Generally, this won't bite you unless you call it with the wrong arguments at the right time; as an alternative, you can call it with the right arguments at the wrong time in SMP. 8-(. The lock manager has issues. I'm not prepared to deal with them in depth at this time. You should consult the list archives for an article with "lockmgr" in the subject; it was posted about 5 weeks ago -- and no, it wasn't me. It identifies at least two race problems that would be pertinent here, give how SMP shutdown progresses. Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.