Date: Tue, 8 Feb 2005 18:59:13 -0800 From: Kris Kennaway <kris@obsecurity.org> To: Christian Brueffer <chris@unixpages.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: panic: _mtx_lock_sleep: recursed on non-recursive mutex bpf2 @ /usr/home/build/src/sys/net/bpf.c:1119 Message-ID: <20050209025912.GA89816@xor.obsecurity.org> In-Reply-To: <20050209011734.GB77038@unixpages.org> References: <20050209010830.GA77038@unixpages.org> <20050209011047.GA86464@xor.obsecurity.org> <20050209011734.GB77038@unixpages.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--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--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20050209025912.GA89816>