From owner-freebsd-current@FreeBSD.ORG Mon Feb 7 02:16:34 2005 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1D21C16A4CE for ; Mon, 7 Feb 2005 02:16:34 +0000 (GMT) Received: from ms-smtp-03-eri0.southeast.rr.com (ms-smtp-03-lbl.southeast.rr.com [24.25.9.102]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4C37943D5D for ; Mon, 7 Feb 2005 02:16:33 +0000 (GMT) (envelope-from damon@hopkins-family.org) Received: from [192.168.0.14] (cpe-024-211-175-213.nc.rr.com [24.211.175.213]) j172GMkc029280 for ; Sun, 6 Feb 2005 21:16:27 -0500 (EST) Message-ID: <42060FC9.30305@hopkins-family.org> Date: Sun, 06 Feb 2005 07:38:33 -0500 From: Damon Hopkins User-Agent: Mozilla Thunderbird 0.8 (X11/20041014) X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-current@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: Symantec AntiVirus Scan Engine Subject: panic: lockmgr: locking against myself X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 07 Feb 2005 02:16:34 -0000 I looked in the old archives and searched google. I've been running this box for awhile now. it used to be a 5.0-Release box. In any case, It's just recently been locking up. so I moved it to a monitor and keyboard (was not previously connected) and I've found this error. I know it is related to acpi, softupdates, and background fsck processes. I never really found a fix for it. I assume I can either turn softupdates off, disable bg fsck, or turn off acpi. I'm not sure which would be the correct thing to do. I'm a bit of a hacker and I can help out wherever possible if someone wants to tell me different things to try. If there are people already fixing it I'd be most inclined to just turning off the bg fsck as I try not to reboot the box and the power is fairly stable. I started getting this problem after my /var partition filled up (via snort).. I haven't really kept up w/ the snapshot thing.. can I just delete the .snap directories and solve my problems?? seems to easy to be a real solution. Thanks, Damon Hopkins damon@hopkins-family.org