From owner-freebsd-current Wed Sep 2 22:42:34 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19117 for freebsd-current-outgoing; Wed, 2 Sep 1998 22:42:34 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from home.dragondata.com (home.dragondata.com [204.137.237.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19112 for ; Wed, 2 Sep 1998 22:42:32 -0700 (PDT) (envelope-from toasty@home.dragondata.com) Received: (from toasty@localhost) by home.dragondata.com (8.8.8/8.8.5) id AAA02169 for current@freebsd.org; Thu, 3 Sep 1998 00:41:26 -0500 (CDT) From: Kevin Day Message-Id: <199809030541.AAA02169@home.dragondata.com> Subject: NFS stable before release? To: current@FreeBSD.ORG Date: Thu, 3 Sep 1998 00:41:25 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31 (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 Is anyone currently working on getting NFS fixed before the 3.0 release? If not, is there someone willing to start, that would benefit from getting some core-dumps from crashes, and a testbed that seems to crash daily? :) For those uninformed... I'm able to get the following panic's under heavy nfs client usage: page fault while in kernel mode fault on no fault entry nfs rcvunlock nfsbioread bwrite: buffer is not busy??? nfs physio vm_page_free: freeing free page vm_page_free: invalid wire count (listed in approximate order of frequency) I can also reproduce problems where processes get stuck after the nfs server dies and comes back.... After this, if anyone wants to tackle NIS, i'll help there, too. :) Kevin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message