From owner-freebsd-stable@FreeBSD.ORG Wed Feb 9 02:59:14 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DCE6516A4CE for ; Wed, 9 Feb 2005 02:59:14 +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 8B2DA43D39 for ; Wed, 9 Feb 2005 02:59:14 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 281B651456; Tue, 8 Feb 2005 18:59:13 -0800 (PST) Date: Tue, 8 Feb 2005 18:59:13 -0800 From: Kris Kennaway To: Christian Brueffer Message-ID: <20050209025912.GA89816@xor.obsecurity.org> References: <20050209010830.GA77038@unixpages.org> <20050209011047.GA86464@xor.obsecurity.org> <20050209011734.GB77038@unixpages.org> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="X1bOJ3K7DJ5YkBrT" Content-Disposition: inline In-Reply-To: <20050209011734.GB77038@unixpages.org> User-Agent: Mutt/1.4.2.1i cc: stable@freebsd.org cc: Kris Kennaway Subject: Re: panic: _mtx_lock_sleep: recursed on non-recursive mutex bpf2 @ /usr/home/build/src/sys/net/bpf.c:1119 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Feb 2005 02:59:15 -0000 --X1bOJ3K7DJ5YkBrT Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Feb 09, 2005 at 02:17:34AM +0100, Christian Brueffer wrote: > On Tue, Feb 08, 2005 at 05:10:47PM -0800, Kris Kennaway wrote: > > On Wed, Feb 09, 2005 at 02:08:30AM +0100, Christian Brueffer wrote: > > > I'm getting this reproducible panic with a 5-STABLE system based on > > > sources from yesterday. The machine in question is an i386 SMP box. > > >=20 > > > The panic is reproducible by running an updated version of the > > > security/scanssh port which is based on libevent. > > >=20 > > > A crashdump is available for further investigation. > >=20 > > Is the kernel compiled with -O2? This confuses the gdb stack trace > > unwinder, so you should try instead with -O. > >=20 >=20 > No, it's compiled with -O. Could a custom CPUTYPE have anything to do > with that? Not AFAIK. Maybe the missing frames in your trace are OK. Kris --X1bOJ3K7DJ5YkBrT Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.0 (FreeBSD) iD8DBQFCCXyAWry0BWjoQKURAoeQAKCWFcnUt9x7CHbLwHQzlwoZ4zvWFgCfYNGv BA8gYyoA2ak/OxzXaMFbZ6U= =euut -----END PGP SIGNATURE----- --X1bOJ3K7DJ5YkBrT--