From owner-freebsd-bugs  Thu Jun  1 03:20:25 1995
Return-Path: bugs-owner
Received: (from majordom@localhost)
          by freefall.cdrom.com (8.6.10/8.6.6) id DAA10045
          for bugs-outgoing; Thu, 1 Jun 1995 03:20:25 -0700
Received: from ie.tiasur.tomsk.su (ie.tiasur.tomsk.su [193.125.215.163])
          by freefall.cdrom.com (8.6.10/8.6.6) with ESMTP id DAA09986
          for <FreeBSD-bugs@FreeBSD.org>; Thu, 1 Jun 1995 03:19:26 -0700
Received: by ie.tiasur.tomsk.su  id SAA01430; Thu, 1 Jun 1995 18:16:41 +0800
From: Pavel Gubin <pg@ie.tiasur.tomsk.su>
Message-Id: <199506011016.SAA01430@ie.tiasur.tomsk.su>
Subject: NFS bug...
To: FreeBSD-bugs@FreeBSD.org
Date: Thu, 1 Jun 1995 18:16:40 +0800 (TSD)
X-Mailer: ELM [version 2.4 PL23]
Content-Type: text
Content-Length: 768       
Sender: bugs-owner@FreeBSD.org
Precedence: bulk


Hello,

   Seems to me I've found some bug in FreeBSD's NFS.

   Bug appears when my BSD works as NFS client connected to NetWare
NFS server. When NFS is heavily loaded, like untaring archive from NFS
to NFS, system more or less regularily crashes with "page fault while
in kernel mode". Kernel debugger's trace shows that trap occurs in
nfs_reply at offset 0xc4 (in my kernel). This location matches
source line 750 in file nfs_socket.c when function nfsm_disct called
(from nfsm_dissect macro). Actually offset 0xc4 is immediately after
call to nfsm_disct.

   I'm wondering if you already know about this bug and should I
continue to dig in that direction? ;-)

PS: Please reply with email(to pg@ie.tiasur.tomsk.su), because I'm
    not a mailing list subscriber.