Date: Wed, 9 Jun 2004 00:11:47 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Alex Dupre <ale@FreeBSD.org> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: kernel panic on smb activity Message-ID: <20040609071147.GA65144@xor.obsecurity.org> In-Reply-To: <40C6B5D8.4000505@FreeBSD.org> References: <40C6AC62.2070604@FreeBSD.org> <20040609062719.GA63934@xor.obsecurity.org> <40C6B5D8.4000505@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
--ew6BAiZeqk4r7MaW Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Wed, Jun 09, 2004 at 09:01:44AM +0200, Alex Dupre wrote: > Kris Kennaway wrote: > >You snipped the most important bit. >=20 > Fatal trap 12: page fault while in kernel mode > fault virtual address =3D 0xc > fault code =3D supervisor write, page not present > instruction pointer =3D 0x8:0xc05ae885 > stack pointer =3D 0x10:0xd3655a40 > frame pointer =3D 0x10:0xd3655a8c > code segment =3D base 0x0, limit 0xfffff, type 0x1b > =3D DPL 0, pres 1, def32 1, gran 1 > processor eflags =3D interrupt enabled, resume, IOPL =3D 0 > current process =3D 733 (cp) > trap number =3D 12 > panic: page fault What backtrace, or which source code line is it faulting at (use addr2line)? Kris P.S. Please try to be proactive with this kind of information (see developers' handbook) when reporting panics, it really shouldn't take 3 emails to extract it from someone who is a committer. --ew6BAiZeqk4r7MaW Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.4 (FreeBSD) iD8DBQFAxrgxWry0BWjoQKURAvFPAKDmtZqL28l5tkZ86QKOhwRvmDnGiACgnhhg yUN2OVujBwgfNvnUsMm7VXw= =3TsL -----END PGP SIGNATURE----- --ew6BAiZeqk4r7MaW--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040609071147.GA65144>