From owner-freebsd-current Sun Mar 29 20:10:54 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA18854 for freebsd-current-outgoing; Sun, 29 Mar 1998 20:10:54 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA18669 for ; Sun, 29 Mar 1998 20:10:04 -0800 (PST) (envelope-from toor@dyson.iquest.net) Received: (from root@localhost) by dyson.iquest.net (8.8.8/8.8.8) id XAA08213; Sun, 29 Mar 1998 23:02:39 -0500 (EST) (envelope-from toor) From: "John S. Dyson" Message-Id: <199803300402.XAA08213@dyson.iquest.net> Subject: Re: panic: "vm_fault: fault on nofault entry" with softupdates In-Reply-To: from Bob Bishop at "Mar 29, 98 01:15:43 pm" To: rb@gid.co.uk (Bob Bishop) Date: Sun, 29 Mar 1998 23:02:39 -0500 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Hi, > > I'm getting occasional "vm_fault: fault on nofault entry" panics running > with softupdates on a recent kernel (CTM src-cur 3301). The traceback looks > like this: > > panic > vm_fault > trap(10,... > --- trap 0xc, ... > generic_bcopy > softdep_setup_allocindir_page > ffs_balloc > ffs_write > vn_write > write > [syscall stuff] > > There seems to be no particular rhyme of reason to this, it happens every > third or fourth buildworld. Any ideas? > That specific bug is a nit leftover from the softupdates port. Will eventually be fixed. I did look at it today, and fixed one bug, but it seems that there are more to be found. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message