From owner-freebsd-current@FreeBSD.ORG Thu Feb 10 04:23:23 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 660CB16A4CE for ; Thu, 10 Feb 2005 04:23:23 +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 232B243D31 for ; Thu, 10 Feb 2005 04:23:23 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id F1404512F2; Wed, 9 Feb 2005 20:23:21 -0800 (PST) Date: Wed, 9 Feb 2005 20:23:21 -0800 From: Kris Kennaway To: Eric Anderson Message-ID: <20050210042321.GA26438@xor.obsecurity.org> References: <420ADAFC.40504@centtech.com> <20050210040102.GA11457@xor.obsecurity.org> <420ADEF7.30003@centtech.com> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="h31gzZEtNLTqOjlF" Content-Disposition: inline In-Reply-To: <420ADEF7.30003@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:23:23 -0000 --h31gzZEtNLTqOjlF Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable 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 >=20 > cpuid =3D 0 > KDB: enter: panic > [thread pid 27 tid 100001 ] > Stopped at kdb_enter+0x30: leave >=20 > Backtrace: > Tracing pid 27 tid 100001 td 0xc2211170 > kdb_enter(c0979fd7,0,c097b542,311,c2211170) at kdb_enter+0x30 > panic(c097d225,186ef,c255d57c,2,c098bfd2) at panic+0x14e > propagate_priority(c2211170,0,c097d184,254,c0a4b950) at=20 > propagate_priority+0x158 >=20 > turnstile_wait(c0a44e00,c255ecf0,c09793e7,216,c0a44e00) at=20 > turnstile_wait+0x39d > _mtx_lock_sleep(c0a44e00,c2211170,0,c097b054,106) at _mtx_lock_sleep+0x191 > _mtx_lock_flags(c0a44e00,0,c097b054,106,c07588b0) at _mtx_lock_flags+0xc0 > softclock(0,0,c0977972,256,c0a44dc0) at softclock+0x1c4 > ithread_loop(c224e580,dc848d48,c097775d,30e,0) at ithread_loop+0x172 > fork_exit(c06c4580,c224e580,dc848d48) at fork_exit+0xc6 > fork_trampoline() at fork_trampoline+0x8 > --- trap 0x1, eip =3D 0, esp =3D 0xdc848d7c, ebp =3D 0 --- >=20 > 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. Kris --h31gzZEtNLTqOjlF Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCuG5Wry0BWjoQKURAn7zAJ9ELGWpKnVc2N5RtlbeKLHZyyfshwCeOi7U Txfrf8acEk6V9Xu67RJYJD0= =2XFr -----END PGP SIGNATURE----- --h31gzZEtNLTqOjlF--