From owner-freebsd-questions@FreeBSD.ORG Wed Jul 16 07:03:52 2003 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9756C37B401 for ; Wed, 16 Jul 2003 07:03:52 -0700 (PDT) Received: from franklin-belle.com (adsl-65-68-247-73.dsl.crchtx.swbell.net [65.68.247.73]) by mx1.FreeBSD.org (Postfix) with ESMTP id BC53543F85 for ; Wed, 16 Jul 2003 07:03:49 -0700 (PDT) (envelope-from jackstone@sage-one.net) Received: from sagea (sagea.sage-american [10.0.0.3]) by franklin-belle.com (8.12.8p1/8.12.8) with SMTP id h6GE3lt1097013 for ; Wed, 16 Jul 2003 09:03:48 -0500 (CDT) (envelope-from jackstone@sage-one.net) Message-Id: <3.0.5.32.20030716090351.012da450@sage-one.net> X-Sender: jackstone@sage-one.net X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.5 (32) Date: Wed, 16 Jul 2003 09:03:51 -0500 To: freebsd-questions@freebsd.org From: "Jack L. Stone" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Spam-Status: No, hits=-0.7 required=4.5 tests=AWL version=2.55-fbelle.rules_v1 X-Spam-Checker-Version: SpamAssassin 2.55-fbelle.rules_v1 (1.174.2.19-2003-05-19-exp) Subject: Panic - Locking Against Myself X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 16 Jul 2003 14:03:52 -0000 Running FBSD-4.8 Release "Random panic & reboot" - cause locking against myself..... appears related to "lockmgr." I had asked the list about this a few weeks ago, but had no takers. Previously, all I could find via google was about "lockmgr", but any discussions was about "code" which is way beyond my skills. References were made to "stale mounts", but there are none in this case. I'm having the problem on a mail server that incurs the panic following an attempt at an ssh login. It happens about once a week or so, but no pattern. It's not hardware. Have changed everything, including the server itself -- bit, not the system contents though which remained on a new hard drive replacement. If anyone knows what causes this and what the fix may be, I could sure use the help. This has been going on for several months and not a good thing. Thanks! Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net