From owner-freebsd-current@FreeBSD.ORG Thu Feb 10 04:37:12 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 855BD16A4CE for ; Thu, 10 Feb 2005 04:37:12 +0000 (GMT) Received: from obsecurity.dyndns.org (CPE0050040655c8-CM00111ae02aac.cpe.net.cable.rogers.com [69.199.47.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3EE0D43D1F for ; Thu, 10 Feb 2005 04:37:12 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id B3A8B51247; Wed, 9 Feb 2005 20:37:10 -0800 (PST) Date: Wed, 9 Feb 2005 20:37:10 -0800 From: Kris Kennaway To: Eric Anderson Message-ID: <20050210043710.GA26601@xor.obsecurity.org> References: <420ADAFC.40504@centtech.com> <20050210040102.GA11457@xor.obsecurity.org> <420ADEF7.30003@centtech.com> <20050210042321.GA26438@xor.obsecurity.org> <420AE1E1.5030403@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="VbJkn9YxBvnuCH5J" Content-Disposition: inline In-Reply-To: <420AE1E1.5030403@centtech.com> User-Agent: Mutt/1.4.2.1i cc: freebsd-current@freebsd.org cc: Kris Kennaway 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:37:12 -0000 --VbJkn9YxBvnuCH5J Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 09, 2005 at 10:24:01PM -0600, Eric Anderson wrote: > Kris Kennaway wrote: >=20 > >On Wed, Feb 09, 2005 at 10:11:35PM -0600, Eric Anderson wrote: > > > >=20 > > > >>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 lo= ck > >> > >>cpuid =3D 0 > >>KDB: enter: panic > >>[thread pid 27 tid 100001 ] > >>Stopped at kdb_enter+0x30: leave > >> > >>Backtrace: > >> > [..snip..] >=20 > >> > >>Hope that helps.. Anything else I can give you? > >> =20 > >> > > > >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. > >=20 > > >=20 > Oh.. Ok, well, how do I find the real panic? I can do any debugging=20 > needed - but I'm not sure what to do here as far as examining the core=20 > in gdb.. I already said..look at the backtraces of the other processes. You'll find another one that has panicked. Kris --VbJkn9YxBvnuCH5J Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCuT2Wry0BWjoQKURAgQMAJ9Pdeq/SY0VmmRxmcjETtDbQk6lKwCgqPLM T4rtqDxVY831XKJHT6z36eE= =V5tl -----END PGP SIGNATURE----- --VbJkn9YxBvnuCH5J--