From owner-freebsd-current@FreeBSD.ORG Fri Aug 1 06:14:35 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 045D837B401; Fri, 1 Aug 2003 06:14:35 -0700 (PDT) Received: from obsecurity.dyndns.org (adsl-63-207-60-135.dsl.lsan03.pacbell.net [63.207.60.135]) by mx1.FreeBSD.org (Postfix) with ESMTP id EE50A43FDD; Fri, 1 Aug 2003 06:14:33 -0700 (PDT) (envelope-from kris@obsecurity.org) Received: from rot13.obsecurity.org (rot13.obsecurity.org [10.0.0.5]) by obsecurity.dyndns.org (Postfix) with ESMTP id BD9FD66BE5; Fri, 1 Aug 2003 06:14:30 -0700 (PDT) Received: by rot13.obsecurity.org (Postfix, from userid 1000) id 7CFBA44D; Fri, 1 Aug 2003 06:14:30 -0700 (PDT) Date: Fri, 1 Aug 2003 06:14:30 -0700 From: Kris Kennaway To: Andrew Gallatin Message-ID: <20030801131430.GA20056@rot13.obsecurity.org> References: <20030731084859.GB36327@rot13.obsecurity.org> <20030731204842.GA14640@rot13.obsecurity.org> <16170.25724.359310.850644@grasshopper.cs.duke.edu> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="C7zPtVaVf+AK4Oqc" Content-Disposition: inline In-Reply-To: <16170.25724.359310.850644@grasshopper.cs.duke.edu> User-Agent: Mutt/1.4.1i cc: alc@FreeBSD.org cc: current@FreeBSD.org cc: Kris Kennaway Subject: Re: panic: vm_fault: fault on nofault entry, addr: fffffe0007e8e000 X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 01 Aug 2003 13:14:35 -0000 --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--