From owner-freebsd-stable  Tue Oct 21 15:32:52 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA14390
          for stable-outgoing; Tue, 21 Oct 1997 15:32:52 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: from ganymede.frii.com (ganymede.frii.com [208.146.240.5])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA14385
          for <freebsd-stable@freebsd.org>; Tue, 21 Oct 1997 15:32:49 -0700 (PDT)
          (envelope-from gnat@frii.com)
From: gnat@frii.com
Received: from elara.frii.com (elara.frii.com [208.146.240.9]) by ganymede.frii.com (8.8.5/8.8.4) with ESMTP id QAA01944 for <freebsd-stable@freebsd.org>; Tue, 21 Oct 1997 16:33:25 -0600 (MDT)
Received: (from gnat@localhost) by elara.frii.com (8.8.5/8.6.9) id QAA00429; Tue, 21 Oct 1997 16:31:20 -0600 (MDT)
Date: Tue, 21 Oct 1997 16:31:20 -0600 (MDT)
Message-Id: <199710212231.QAA00429@elara.frii.com>
To: freebsd-stable@freebsd.org
Subject: -STABLE reboots
Mime-Version: 1.0 (generated by tm-edit 7.103)
Content-Type: text/plain; charset=US-ASCII
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

We've been seeing some mysterious kernel panics from FreeBSD
2.2-STABLE.

Oct 21 15:38:45 himalia /kernel: panic: ufs_lock: recursive lock not expected, pid: 105
Oct 21 15:38:45 himalia /kernel: 
Oct 21 15:38:45 himalia /kernel: 
Oct 21 15:38:45 himalia /kernel: syncing disks... Copyright (c) 1992-1997 FreeBSD Inc.

The rebooting machine is our NFS server.  I suspect, but can't
definitively prove, that the reboots are being caused by minivend
running on one of our web servers (which mounts filesystems from the
rebooting machine).

Has anyone else experienced this?  Does this look symptomatic of
the machine not being built with something or other?

Kernel configuration files, relevant sections of /var/log/messages,
etc, on request.

Nat