Date: Sun, 26 Feb 2006 02:03:00 -0500 From: Kris Kennaway <kris@obsecurity.org> To: Garrett Cooper <youshi10@u.washington.edu> Cc: freebsd-questions@freebsd.org Subject: Re: anyone recognize this panic? Message-ID: <20060226070300.GA59714@xor.obsecurity.org> In-Reply-To: <44014943.8050905@u.washington.edu> References: <17409.8562.677322.222883@jerusalem.litteratus.org> <20060226033858.GA10985@xor.obsecurity.org> <440145EF.5000101@u.washington.edu> <20060226061343.GA4483@xor.obsecurity.org> <44014943.8050905@u.washington.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--/04w6evG8XlLl3ft Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Feb 25, 2006 at 10:22:59PM -0800, Garrett Cooper wrote: > >>>>re0: diagnostic failed to receive packet in loopback mode > >>>>re0: attach aborted due to hardware diagnostic failure > >>>>panic: mtx_lock() of spin mutex (null) @=20 > >>>>/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 > >>>> > >>>> =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 wa= s=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 issu= e=20 > >>laid with the re (?) kernel driver would be a start. > >> =20 > >> > > > >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 > >=20 > > > True, but at least you'd be able to find a way to the affected code...=20 > After that it's just tests and debugging =3D\... I don't understand what you're suggesting; how do you find the affected code without a traceback? Kris --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.1 (FreeBSD) iD8DBQFEAVKkWry0BWjoQKURAloWAJ4gLVvVnhiqWsnO0pkU7+kpJ7cvpwCfV6Fm pU2dzkAkbRe0th+xOWVW48o= =kOu1 -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060226070300.GA59714>