From owner-freebsd-current@FreeBSD.ORG Fri Aug 1 06:00:53 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 607AA37B405; Fri, 1 Aug 2003 06:00:53 -0700 (PDT) Received: from duke.cs.duke.edu (duke.cs.duke.edu [152.3.140.1]) by mx1.FreeBSD.org (Postfix) with ESMTP id 29BF243FBD; Fri, 1 Aug 2003 06:00:50 -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 h71D0nnq013742 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO); Fri, 1 Aug 2003 09:00:49 -0400 (EDT) Received: (from gallatin@localhost) by grasshopper.cs.duke.edu (8.11.6/8.9.1) id h71D0ic79171; Fri, 1 Aug 2003 09:00:44 -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.25724.359310.850644@grasshopper.cs.duke.edu> Date: Fri, 1 Aug 2003 09:00:44 -0400 (EDT) To: Kris Kennaway In-Reply-To: <20030731204842.GA14640@rot13.obsecurity.org> References: <20030731084859.GB36327@rot13.obsecurity.org> <20030731204842.GA14640@rot13.obsecurity.org> X-Mailer: VM 6.75 under 21.1 (patch 12) "Channel Islands" XEmacs Lucid cc: alc@FreeBSD.org 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 13:00:53 -0000 Kris Kennaway writes: > On Thu, Jul 31, 2003 at 01:48:59AM -0700, Kris Kennaway wrote: > > I upgraded the alpha package machines tonight, and one of them fell > > over shortly after taking load, with the following: <..> > Two more panics on alpha: > > panic: vm_fault: fault on nofault entry, addr: fffffe0007fde000 > Debugger() at Debugger+0x38 > panic() at panic+0x168 > vm_fault() at vm_fault+0x1360 > trap() at trap+0x5c8 > XentMM() at XentMM+0x2c > --- memory management fault (from ipl 0) --- > bcopy_samealign_lp() at bcopy_samealign_lp+0x8 > copyout() at copyout+0x38 > uiomove() at uiomove+0x19c > pipe_read() at pipe_read+0x290 > dofileread() at dofileread+0x100 > read() at read+0x64 > syscall() at syscall+0x33c > XentSys() at XentSys+0x64 > --- syscall (3, FreeBSD ELF64, read) --- > --- user mode --- 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. 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. 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. Drew