From owner-freebsd-current@FreeBSD.ORG Tue Jun 29 18:53:15 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 1FE5816A4CE for ; Tue, 29 Jun 2004 18:53:15 +0000 (GMT) Received: from mail5.speakeasy.net (mail5.speakeasy.net [216.254.0.205]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2EB943D2F for ; Tue, 29 Jun 2004 18:53:14 +0000 (GMT) (envelope-from jhb@FreeBSD.org) Received: (qmail 29525 invoked from network); 29 Jun 2004 18:53:04 -0000 Received: from dsl027-160-063.atl1.dsl.speakeasy.net (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender ) encrypted SMTP for ; 29 Jun 2004 18:53:03 -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 i5TIqOgF011887; Tue, 29 Jun 2004 14:52:48 -0400 (EDT) (envelope-from jhb@FreeBSD.org) From: John Baldwin To: freebsd-current@FreeBSD.org Date: Tue, 29 Jun 2004 14:53:34 -0400 User-Agent: KMail/1.6 References: <20040628202434.GA73213@atrbg11.informatik.tu-muenchen.de> <20040629170014.GC1144@green.homeunix.org> <20040629183557.GA77135@atrbg11.informatik.tu-muenchen.de> In-Reply-To: <20040629183557.GA77135@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: <200406291453.34291.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: Tue, 29 Jun 2004 18:53:15 -0000 On Tuesday 29 June 2004 02:35 pm, Daniel Lang wrote: > Hi Brian, > > Brian Fundakowski Feldman wrote on Tue, Jun 29, 2004 at 01:00:14PM -0400: > [..] > > > You can find it out without using gdb, too. This will work for > > only main kernel symbols, but you can do something similar for > > KLDs. Say I want to find a symbol that's in the main kernel object: > > > > $ objdump -t /boot/kernel/kernel | ruby -ne 'fields = $_.split; if > > fields[3] == ".text" and fields[2] == "F" and > > 0xc048a800.between?(fields[0].hex, fields[0].hex + fields[4].hex) then > > puts $_ end' c048a7ac l F .text 0000006b cbb_removal > > [..] > > Thanks for that hint, but Colin suggested to use "addr2line", which > produced some result. Maybe addr2line does a similar thing > as your objdump/ruby script: > > So I have a line of code for the failing address: > > # addr2line -e kernel.debug 0xc053932b > /usr/src/sys/kern/subr_witness.c:898 > > which is (in my kernel): > > [..] > lock1 = &(*lock_list)->ll_children[(*lock_list)->ll_count - 1]; > [..] > > Well, I'm not sure if this is a big help. I doubt there is a bug > in witness code. > > I'll cross-check with gdb to see if there is the same > result. Too bad I couldn't get a crashdump. > > (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!). Well, it may be a hint sadly enough. The fact that it thinks Giant is a spin lock means that witness is confused, and this panic may be further such confusion. One possibility is that somehow the sleep queue chain mutexes have been corrupted. -- John Baldwin <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve" = http://www.FreeBSD.org