Date: Fri, 1 Aug 2003 06:14:30 -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: <20030801131430.GA20056@rot13.obsecurity.org> In-Reply-To: <16170.25724.359310.850644@grasshopper.cs.duke.edu> References: <20030731084859.GB36327@rot13.obsecurity.org> <20030731204842.GA14640@rot13.obsecurity.org> <16170.25724.359310.850644@grasshopper.cs.duke.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
--C7zPtVaVf+AK4Oqc Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Aug 01, 2003 at 09:00:44AM -0400, Andrew Gallatin wrote: > 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. Two crashdumps coming up! I'll move them onto beast:/j/kris/crash together with the kernel.debug. > I updated a UP alpha here at roughly the same time. I was able to > do a buildworld with the new kernel from sources dated July 30, around > noon PDT. The problems I'm seeing are only intermittent (about a dozen spurious port build failures over 27 hours of package building on 9 machines, plus 3 VM panics), but they're definitely ongoing. > Is this GENERIC or an otherwise SMP kernel? Just for the heck of it, > edit GENERIC and get rid of the SMP option if its a UP box. That's > what I always run and I'm curious if that might be your stability problem. It's a UP kernel. Kris --C7zPtVaVf+AK4Oqc Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.2 (FreeBSD) iD8DBQE/Kme2Wry0BWjoQKURAge/AJ465TAzZ7n95+r/lE4hDNk56VutUwCcCe50 vEiGQFjXwp7/kcFLkdug7os= =Vla4 -----END PGP SIGNATURE----- --C7zPtVaVf+AK4Oqc--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20030801131430.GA20056>