From owner-freebsd-current@FreeBSD.ORG Thu Mar 27 22:12:54 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 400B737B401; Thu, 27 Mar 2003 22:12:54 -0800 (PST) Received: from smtp.acd.net (smtp.acd.net [207.179.102.146]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3425643F85; Thu, 27 Mar 2003 22:12:53 -0800 (PST) (envelope-from taxman@ACD.NET) Received: from 207.179.99.129 ([207.179.99.129]) by smtp.acd.net with Microsoft SMTPSVC(5.0.2195.5329); Fri, 28 Mar 2003 00:50:27 -0500 From: taxman To: Greg 'groggy' Lehey , Jason Morgan Date: Fri, 28 Mar 2003 00:54:16 -0500 User-Agent: KMail/1.5 References: <20030326133528.GB533@sentinelchicken.net> <20030327005444.GA31856@wantadilla.lemis.com> In-Reply-To: <20030327005444.GA31856@wantadilla.lemis.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200303280054.16360.taxman@acd.net> X-OriginalArrivalTime: 28 Mar 2003 05:50:28.0556 (UTC) FILETIME=[EFB0C0C0:01C2F4ED] X-Spam-Status: No, hits=-25.8 required=5.0 tests=AWL,EMAIL_ATTRIBUTION,IN_REP_TO,QUOTED_EMAIL_TEXT, REFERENCES,REPLY_WITH_QUOTES,USER_AGENT autolearn=ham version=2.50 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.50 (1.173-2003-02-20-exp) cc: freebsd-current@freebsd.org Subject: Re: 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: Fri, 28 Mar 2003 06:12:56 -0000 On Wednesday 26 March 2003 07:54 pm, Greg 'groggy' Lehey wrote: > On Wednesday, 26 March 2003 at 13:35:28 +0000, Jason Morgan wrote: > > 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 > > Take a look at http://www.lemis.com/texts/panic.txt or > http://www.lemis.com/texts/panic.pdf and tell me if that helps. This > will be going into the new edition of "The Complete FreeBSD" in a few > days time, so I'm interested in getting something which is helpful. Hi Greg, I've been looking at doing the same thing, learn how to capture a crash dump, and analyze it etc. I'm a definite newbie at that so I thought it would be a good test for the article. It's pretty readable, but I had a problem with enabling the crash dump as noted: To enable dumping, put something like this in /boot/loader.conf: dumpdev=/dev/ad0s1b that gives an error that is similiar to: WARNING: syntax error on file /boot/loader.conf dumpdev=/dev/ad0s1b ^ the same syntax in /etc/rc.conf worked fine, however. This was on 4.8 RC2, but the syntax error appeared on a recent -current too. Thanks, Tim