Date: Mon, 1 May 2006 21:20:13 GMT From: Kris Kennaway <kris@obsecurity.org> To: freebsd-bugs@FreeBSD.org Subject: Re: kern/96605: kernel panic: FreeBSD 7.0 Message-ID: <200605012120.k41LKDvl093589@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
The following reply was made to PR kern/96605; it has been noted by GNATS. From: Kris Kennaway <kris@obsecurity.org> To: Ron Scheckelhoff <rscheckelhoff@yahoo.com> Cc: freebsd-gnats-submit@FreeBSD.org Subject: Re: kern/96605: kernel panic: FreeBSD 7.0 Date: Mon, 1 May 2006 17:18:21 -0400 On Mon, May 01, 2006 at 04:02:08PM +0000, Ron Scheckelhoff wrote: > > >Number: 96605 > >Category: kern > >Synopsis: kernel panic: FreeBSD 7.0 > >Confidential: no > >Severity: non-critical > >Priority: low > >Responsible: freebsd-bugs > >State: open > >Quarter: > >Keywords: > >Date-Required: > >Class: sw-bug > >Submitter-Id: current-users > >Arrival-Date: Mon May 01 16:10:20 GMT 2006 > >Closed-Date: > >Last-Modified: > >Originator: Ron Scheckelhoff > >Release: FreeBSD 7.0 > >Organization: > >Environment: > >Description: > panic: _mtx_lock_sleep: recursed on non-recursive mutex > rtentry@/usr/src/sys/net/route.c:1287 > cpuid=1 > KDBienter: panic > [ thread PID 695 tid 100040 ] > Stopped at Kdb_enter+0x2b:nop > > The aforementioned panic occurred after a second NIC was installed on the computer, and it was first used with the "ping" utility. The first NIC was operating OK prior to the panic. Please raise bugs in -current on the -current mailing list; PRs are not the best first line of aproach to such problems (only if you don't get a quick response on the mailing list). Also you need to obtain better debugging before reporting the problem, see the chapter on kernel debugging in the developers handbook. Kris
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200605012120.k41LKDvl093589>