From owner-freebsd-current@FreeBSD.ORG Tue Jun 29 18:35:59 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 51E6916A4CE; Tue, 29 Jun 2004 18:35:59 +0000 (GMT) Received: from mailout1.informatik.tu-muenchen.de (mailout1.informatik.tu-muenchen.de [131.159.0.18]) by mx1.FreeBSD.org (Postfix) with ESMTP id B8D1043D39; Tue, 29 Jun 2004 18:35:58 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Tue, 29 Jun 2004 20:35:57 +0200 From: Daniel Lang To: Brian Fundakowski Feldman Message-ID: <20040629183557.GA77135@atrbg11.informatik.tu-muenchen.de> References: <20040628202434.GA73213@atrbg11.informatik.tu-muenchen.de> <20040629153921.GE75577@atrbg11.informatik.tu-muenchen.de> <200406291200.12030.jhb@FreeBSD.org> <20040629163028.GM75577@atrbg11.informatik.tu-muenchen.de> <20040629170014.GC1144@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040629170014.GC1144@green.homeunix.org> X-Geek: GCS/CC d-- s: a- C++$ UBS++++$ P+++$ L- E-(---) W+++(--) N++ o K w--- O? M? V? PS+(++) PE--(+) Y+ PGP+ t++ 5+++ X R+(-) tv+ b+ DI++ D++ G++ e+++ h---(-) r+++ y+ User-Agent: Mutt/1.5.6i X-Virus-Scanned: by amavisd-new at informatik.tu-muenchen.de cc: freebsd-current@FreeBSD.org cc: John Baldwin 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:35:59 -0000 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!). Best regards, Daniel -- IRCnet: Mr-Spock - Soon I will be free, then hungry. - Daniel Lang * dl@leo.org * +49 89 289 18532 * http://www.leo.org/~dl/