From owner-freebsd-current@FreeBSD.ORG Wed Jun 30 01:38:27 2004 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 7DC6916A4CE for ; Wed, 30 Jun 2004 01:38:27 +0000 (GMT) Received: from mail1.speakeasy.net (mail1.speakeasy.net [216.254.0.201]) by mx1.FreeBSD.org (Postfix) with ESMTP id 5C7AC43D54 for ; Wed, 30 Jun 2004 01:38:27 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 11670 invoked from network); 30 Jun 2004 01:37:31 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 30 Jun 2004 01:37:31 -0000 Received: from 131.106.56.214 (p58.n-nypop02.stsn.com [199.106.89.58]) by server.baldwin.cx (8.12.11/8.12.11) with ESMTP id i5U1bLxJ014025; Tue, 29 Jun 2004 21:37:27 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 29 Jun 2004 21:28:44 -0400 User-Agent: KMail/1.6 References: <20040628202434.GA73213@atrbg11.informatik.tu-muenchen.de> <20040629184946.GE1144@green.homeunix.org> <20040629193157.GA77322@atrbg11.informatik.tu-muenchen.de> In-Reply-To: <20040629193157.GA77322@atrbg11.informatik.tu-muenchen.de> MIME-Version: 1.0 Content-Disposition: inline Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Message-Id: <200406292128.45379.jhb@FreeBSD.org> X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on server.baldwin.cx cc: Brian Fundakowski Feldman cc: Daniel Lang Subject: Re: kern/68442: panic - acquiring duplicate lock of same type: "sleepq chain" 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, 30 Jun 2004 01:38:27 -0000 On Tuesday 29 June 2004 03:31 pm, Daniel Lang wrote: > Hi again, > > I installed gdb6 from ports, which works. > It just confirms the addr2line result: > > (kgdb) l *0xc053932b > 0xc053932b is in witness_checkorder (/usr/src/sys/kern/subr_witness.c:898). > > > Brian Fundakowski Feldman wrote on Tue, Jun 29, 2004 at 02:49:46PM -0400: > [..] > > > > (What hurts most, is, that in one occasion I had a ddb prompt > > > and could call doadump() successfully. But after reboot, damn > > > /var was full, so savecore could not write it to disk, argl!). > > > > You can make /var/crash a symlink to a directory with more space. > > Yes, I usually have enough space there. It was an ill coincidence. :-/ > > Don: > Thanks for the hint to run savecore later on. I should have guessed > as long as there is not much going on and swap did not need to used > yet, I would have gotten a good core. Unfortunately it is to late > for now. I'll keep it in mind, though. > > John: > Ok, mutex/witness confusion is maybe going on. How would you suggest > to proceed. I am a little reluctant to boot the machine to multi-user > and wait for the next crash (which most of the time does not > produce a dump or ddb prompt), since I would have to hit the > reset button and right now, I'm at home now and have only remote > access. Unfortunately, I don't have any good ideas off the top of my head. If you have a crashdump and a working gdb binary of some sort then you can try looking at the sleepq_chains[] hash table in the core file to look for a mutex that is corrupted. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org