Date: Fri, 1 Aug 2003 14:33:02 -0700 From: Kris Kennaway <kris@obsecurity.org> To: Andrew Gallatin <gallatin@cs.duke.edu> Cc: Kris Kennaway <kris@obsecurity.org> Subject: Re: panic: vm_fault: fault on nofault entry, addr: fffffe0007e8e000 Message-ID: <20030801213302.GA21988@rot13.obsecurity.org> In-Reply-To: <16170.32826.78241.478325@grasshopper.cs.duke.edu> References: <20030731084859.GB36327@rot13.obsecurity.org> <20030731204842.GA14640@rot13.obsecurity.org> <16170.25724.359310.850644@grasshopper.cs.duke.edu> <20030801131430.GA20056@rot13.obsecurity.org> <16170.32826.78241.478325@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--Qxx1br4bt0+wmkIi
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Fri, Aug 01, 2003 at 10:59:06AM -0400, Andrew Gallatin wrote:
>=20
> Kris Kennaway writes:
> > On Fri, Aug 01, 2003 at 09:00:44AM -0400, Andrew Gallatin wrote:
> >=20
> > > The crashdump might actually be useful here. You'd have only the
> > > trap() and vm_fault() frames, but at least you'd have information
> > > about the state of the vm system.
> >=20
> > Two crashdumps coming up! I'll move them onto beast:/j/kris/crash
> > together with the kernel.debug.
> >=20
>=20
> I may have wasted your time. The first one is unusable (lots of ddb
> cruft). Damned gdb -k. Grrr.
That one was the third panic I posted, which was the:
trap entry =3D 0x2 (memory management fault)
> I don't have read perms on vmcore.{1,2}, so I don't know if they are
> helpful. =20
Oops, sorry.
> If you're willing to get your traces via ddb's debug.trace_on_panic
> and to set debug.debugger_on_panic=3D0, then we might get at least a
> partial trace. FWIW, I have to do this to get any sort of crashdump
> at all on SMP x86. I'm amazed you were able to call doadump from ddb.
> When I try that on x86, I just get a continuous stream of panics or
> fatal traps.
Hmm, I don't see this on the UP i386 machines. Bento hasn't panicked
in a while (time to upgrade!), although I do seem to recall problems
the last time it did.
kris
--Qxx1br4bt0+wmkIi
Content-Type: application/pgp-signature
Content-Disposition: inline
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (FreeBSD)
iD8DBQE/KtyOWry0BWjoQKURAhiFAJ48U10d2A4DkIKkeTbaVupV3GBjbQCgnSPn
OyEWLdXmLDt5V1xqLJ1K3VU=
=PoeS
-----END PGP SIGNATURE-----
--Qxx1br4bt0+wmkIi--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030801213302.GA21988>