From owner-freebsd-current@FreeBSD.ORG Fri Aug 1 07:59:12 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 A637037B401 for ; Fri, 1 Aug 2003 07:59:12 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id D56CD43FDD for ; Fri, 1 Aug 2003 07:59:11 -0700 (PDT) (envelope-from gallatin@cs.duke.edu) Received: from grasshopper.cs.duke.edu (grasshopper.cs.duke.edu [152.3.145.30]) by duke.cs.duke.edu (8.12.9/8.12.9) with ESMTP id h71ExBnq023164 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Aug 2003 10:59:11 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h71Ex6u79285; Fri, 1 Aug 2003 10:59:06 -0400 (EDT) (envelope-from gallatin@cs.duke.edu) From: Andrew Gallatin MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-ID: <16170.32826.78241.478325@grasshopper.cs.duke.edu> Date: Fri, 1 Aug 2003 10:59:06 -0400 (EDT) To: Kris Kennaway In-Reply-To: <20030801131430.GA20056@rot13.obsecurity.org> References: <20030731084859.GB36327@rot13.obsecurity.org> <20030731204842.GA14640@rot13.obsecurity.org> <16170.25724.359310.850644@grasshopper.cs.duke.edu> <20030801131430.GA20056@rot13.obsecurity.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: current@FreeBSD.org 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 14:59:12 -0000 Kris Kennaway writes: > 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 may have wasted your time. The first one is unusable (lots of ddb cruft). Damned gdb -k. Grrr. I don't have read perms on vmcore.{1,2}, so I don't know if they are helpful. If you're willing to get your traces via ddb's debug.trace_on_panic and to set debug.debugger_on_panic=0, 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. Drew