Date: Fri, 9 Apr 2004 20:13:15 -0700 From: Kris Kennaway <kris@obsecurity.org> To: David Magda <dmagda@ee.ryerson.ca> Cc: freebsd-stable@freebsd.org Subject: Re: panic on 4.x using star to /dev/nsa0 Message-ID: <20040410031315.GA65829@xor.obsecurity.org> In-Reply-To: <25650060-8A8C-11D8-9C7E-000A95B96FF8@ee.ryerson.ca> References: <25650060-8A8C-11D8-9C7E-000A95B96FF8@ee.ryerson.ca>
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 Fri, Apr 09, 2004 at 09:12:33PM -0400, David Magda wrote: > This has only happened once so far so I haven't filed a PR in case it's= =20 > not reproducible. Since I have the kernel dump I can give more=20 > information if needed if someone would be willing to tell me what to=20 > type into the debugger's CLI. Don't have much experience in this since=20 > I haven't had many panics under FreeBSD. :> (Is there a document=20 > describing this? A kind of "what happens if the system panics"=20 > FAQ/HOWTO.) The chapter on kernel debugging in the Developers Handbook explains how to build a debugging kernel and use it to extract a traceback suitable for someone to diagnose a kernel panic. Kris --/04w6evG8XlLl3ft Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAd2ZLWry0BWjoQKURAt1bAJ9LxI9rZqVRiJwU8lNKX3PA2klPaQCfUFrx VmpnmEk0KG9SlIIwDX2eLL8= =KBC5 -----END PGP SIGNATURE----- --/04w6evG8XlLl3ft--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040410031315.GA65829>