From owner-freebsd-current@FreeBSD.ORG Thu Feb 10 04:25:57 2005 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 7966916A4CF for ; Thu, 10 Feb 2005 04:25:57 +0000 (GMT) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 12FEA43D3F for ; Thu, 10 Feb 2005 04:25:57 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from centtech.com ([192.168.42.25]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j1A4Puc1069184; Wed, 9 Feb 2005 22:25:56 -0600 (CST) (envelope-from anderson@centtech.com) Message-ID: <420AE1E1.5030403@centtech.com> Date: Wed, 09 Feb 2005 22:24:01 -0600 From: Eric Anderson User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7b) Gecko/20040316 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Kris Kennaway References: <420ADAFC.40504@centtech.com> <20050210040102.GA11457@xor.obsecurity.org> <420ADEF7.30003@centtech.com> <20050210042321.GA26438@xor.obsecurity.org> In-Reply-To: <20050210042321.GA26438@xor.obsecurity.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: ClamAV 0.80/585/Thu Nov 11 06:22:42 2004 clamav-milter version 0.80j on mh2.centtech.com X-Virus-Status: Clean cc: freebsd-current@freebsd.org Subject: Re: Panic - FFS background buffer bla bla 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: Thu, 10 Feb 2005 04:25:57 -0000 Kris Kennaway wrote: >On Wed, Feb 09, 2005 at 10:11:35PM -0600, Eric Anderson wrote: > > > >>After rebooting (with a console plugged in), I get this: >>Fast boot: skipping disk checks. >>panic: panic: thread 100079(cp):2 holds Giant but isn't blocked on a lock >> >>cpuid = 0 >>KDB: enter: panic >>[thread pid 27 tid 100001 ] >>Stopped at kdb_enter+0x30: leave >> >>Backtrace: >> [..snip..] >> >>Hope that helps.. Anything else I can give you? >> >> > >That's actually not the real panic. Look at the backtraces of other >processes to find the first panic. If you can examine the core in gdb >to obtain source code line numbers, that would help too. > > Oh.. Ok, well, how do I find the real panic? I can do any debugging needed - but I'm not sure what to do here as far as examining the core in gdb.. Eric