From owner-freebsd-current Sun Mar 29 20:41:20 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id UAA02077 for freebsd-current-outgoing; Sun, 29 Mar 1998 20:41:20 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from rah.star-gate.com (rah.star-gate.com [209.133.7.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id UAA02060 for ; Sun, 29 Mar 1998 20:41:14 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.8/8.8.8) with ESMTP id UAA05599; Sun, 29 Mar 1998 20:00:43 -0800 (PST) (envelope-from hasty@rah.star-gate.com) Message-Id: <199803300400.UAA05599@rah.star-gate.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Bob Bishop cc: current@FreeBSD.ORG Subject: Re: panic: "vm_fault: fault on nofault entry" with softupdates In-reply-to: Your message of "Sun, 29 Mar 1998 13:15:43 +0100." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 29 Mar 1998 20:00:42 -0800 From: Amancio Hasty Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG This is an old soft update panic . Try John's latest check in: dyson 1998/03/29 10:23:45 PST Modified files: sys/kern vfs_syscalls.c Log: Correct a significant problem with the softupdates port. Allow fsync to work properly within the softupdates framework, and thereby eliminate some unfortunate panics. Revision Changes Path 1.96 +11 -4 src/sys/kern/vfs_syscalls.c -------- Hope that my testing goes well over here . Usually, I can crash the system within an hour if I enable soft updates. Amancio To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message