From owner-freebsd-current@FreeBSD.ORG Tue Aug 10 20:15:34 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 CC34716A4CE; Tue, 10 Aug 2004 20:15:34 +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 160EC43D39; Tue, 10 Aug 2004 20:15:34 +0000 (GMT) (envelope-from langd@informatik.tu-muenchen.de) Date: Tue, 10 Aug 2004 22:15:32 +0200 From: Daniel Lang To: Terrence Koeman Message-ID: <20040810201532.GA53289@atrbg11.informatik.tu-muenchen.de> References: <200408101535.11863.jhb@FreeBSD.org> <200408102141323.SM01804@manrikigusari> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <200408102141323.SM01804@manrikigusari> 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/sophie/sophos at mailrelay1.informatik.tu-muenchen.de cc: freebsd-current@FreeBSD.org cc: 'John Baldwin' Subject: Re: Lock order reversal in 5.2-CURRENT 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, 10 Aug 2004 20:15:35 -0000 Hi Terrence, Terrence Koeman wrote on Tue, Aug 10, 2004 at 09:40:22PM +0200: [..] > > --- trap 0xc, eip = 0xc04b3ed2, esp = 0xd4dd7c90, ebp = 0xd4dd7ce0 --- > > mi_switch(1,0,c060d2be,9c,dbba0) at mi_switch+0x102 > > > > Does the original poster have a debug kernel built? > > > > Yes I have, but I have no experience with the debugger. I'll be happy to > carry out whatever's needed. [..] The process is documented in the developers handbook: http://www.freebsd.org/doc/en/books/developers-handbook/kerneldebug.html In short: - first make sure dumpdevice is set and savecore enabled in /etc/rc.conf - after a panic get a crash-dump, e.g. in ddb enter "call doadump()" - after reboot the dump should be saved to e.g. /var/crash/vmcore.0 - analyse the dump with kernel-gdb: gdb -k /usr/obj/usr/src/sys//kernel.debug /var/crash/vmcore.0 (IIRC), so this is where the debug kernel is required. Please not that stock gdb is currently not able to act as kernel-debugger, you need to install the gdb6 port. - Start with a backtrace (bt) of the kernel, look out for corrupted data. Obvious things are 0x0 pointers, where valid data is expected. If spotted, try to trace the source of corruption. - Post any of your discoveries. Often just the stack-trace with function, arguments and source-lines can give valuable hints to the developers. HTH, Daniel -- IRCnet: Mr-Spock - Agartim billiard bumba m'abdul in papejim twista - rumba rock n rolla. Leik'ab mai. Spirzon Heroin se'osit gaula. - - Marijuana esit gaula. Haschisch. Opis. - Daniel Lang * dl@leo.org * +49 89 2600 8122 * http://www.leo.org/~dl/