From owner-freebsd-questions@FreeBSD.ORG Sun Feb 26 06:13:44 2006 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7AB6516A420 for ; Sun, 26 Feb 2006 06:13:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 33E6F43D46 for ; Sun, 26 Feb 2006 06:13:44 +0000 (GMT) (envelope-from kris@obsecurity.org) Received: from obsecurity.dyndns.org (elvis.mu.org [192.203.228.196]) by elvis.mu.org (Postfix) with ESMTP id 102F01A4DC4; Sat, 25 Feb 2006 22:13:44 -0800 (PST) Received: by obsecurity.dyndns.org (Postfix, from userid 1000) id 6569A51456; Sun, 26 Feb 2006 01:13:43 -0500 (EST) Date: Sun, 26 Feb 2006 01:13:43 -0500 From: Kris Kennaway To: Garrett Cooper Message-ID: <20060226061343.GA4483@xor.obsecurity.org> References: <17409.8562.677322.222883@jerusalem.litteratus.org> <20060226033858.GA10985@xor.obsecurity.org> <440145EF.5000101@u.washington.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="OgqxwSJOaUobr8KG" Content-Disposition: inline In-Reply-To: <440145EF.5000101@u.washington.edu> User-Agent: Mutt/1.4.2.1i Cc: freebsd-questions@freebsd.org Subject: Re: anyone recognize this panic? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 26 Feb 2006 06:13:44 -0000 --OgqxwSJOaUobr8KG Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 25, 2006 at 10:08:47PM -0800, Garrett Cooper wrote: > Kris Kennaway wrote: >=20 > >On Sat, Feb 25, 2006 at 10:33:06PM -0500, Robert Huff wrote: > >=20 > > > >> I just had my -CURRENT* machine crash under moderate load. No > >>dump is available because the machine locked hard, but I did copy > >>this off the screen: > >> > >>re0: diagnostic failed to receive packet in loopback mode > >>re0: attach aborted due to hardware diagnostic failure > >>panic: mtx_lock() of spin mutex (null) @ /usr/src/sys/netinet/in_pcb,c:= 862 > >> > >> "re0" is a Linksys EG-1032, less than two months old. It was > >>connected, but had zero traffic at the time of the crash. > >> Before I take this to current@ - has anyone seen anything like > >>this before? A quick check of the archives and the web in general > >>didn't show anything. > >> =20 > >> > > > >You need to at least get a traceback from the panic, and preferably a > >crashdump. > > > >Kris > >=20 > > > Probably should pass this onto some devs. It seems like a null value was= =20 > passed for locking a mutex in the OS, which is important. Having a=20 > traceback would be good though... but at least mentioning that the issue= =20 > laid with the re (?) kernel driver would be a start. Unfortunately without a traceback the panic string is useless since it gives you no clue about how the system got into that state. This kind of panic is often a secondary effect of some other problem. Kris --OgqxwSJOaUobr8KG Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEAUcXWry0BWjoQKURAoMSAKCPmQmPceIMWxJRNSAc7ItuMeoFbwCg0Kpf RQm0CF2I58CBfFQXoBMd0TU= =1SB0 -----END PGP SIGNATURE----- --OgqxwSJOaUobr8KG--