From owner-freebsd-current@FreeBSD.ORG Wed Mar 26 10:27:35 2003 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 D1E8E37B404 for ; Wed, 26 Mar 2003 10:27:35 -0800 (PST) Received: from samson.sentinelchicken.net (h-64-105-205-76.CMBRMAOR.covad.net [64.105.205.76]) by mx1.FreeBSD.org (Postfix) with SMTP id B7AED43F75 for ; Wed, 26 Mar 2003 10:27:34 -0800 (PST) (envelope-from jwm@numbuscus.sentinelchicken.net) Received: (qmail 473 invoked from network); 26 Mar 2003 18:30:09 -0000 Received: from numbuscus.sentinelchicken.net (10.0.0.2) by samson.sentinelchicken.net with SMTP; 26 Mar 2003 18:30:09 -0000 Received: (from jwm@localhost)h2QDZTFR001242 for freebsd-current@freebsd.org; Wed, 26 Mar 2003 13:35:29 GMT Date: Wed, 26 Mar 2003 13:35:28 +0000 From: Jason Morgan To: freebsd-current@freebsd.org Message-ID: <20030326133528.GB533@sentinelchicken.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.4.1i X-Spam-Status: No, hits=-6.4 required=5.0 tests=USER_AGENT_MUTT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) Subject: Kernel panic - never had one before, what do I do? 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: Wed, 26 Mar 2003 18:27:36 -0000 I just got a panic. As I have never had one before, I don't know what to do. It's on another system so I don't have to reboot immediately (that would solve the problem temporarily, wouldn't it?) if someone would give me some advice, I could try to help debug it; however, as I'm not a coder (not a real one anyway), I don't know how much help I would be. It's a 5.0-CURRENT system, just installed and built last week. It paniced right after doing a source update (not a build, just cvsup). The panic error is as follows: panic: mtx_lock() of spin mutex vnode interlock @ /usr/src/sys/kern/vfs_subr.c:3187 Thanks, Jason