From owner-freebsd-bugs Tue Jun 22 5: 0: 3 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from freefall.freebsd.org (freefall.FreeBSD.ORG [204.216.27.21]) by hub.freebsd.org (Postfix) with ESMTP id D9882152CB for ; Tue, 22 Jun 1999 05:00:01 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.9.3/8.9.2) id FAA37866; Tue, 22 Jun 1999 05:00:02 -0700 (PDT) (envelope-from gnats@FreeBSD.org) Date: Tue, 22 Jun 1999 05:00:02 -0700 (PDT) Message-Id: <199906221200.FAA37866@freefall.freebsd.org> To: freebsd-bugs@FreeBSD.org Cc: From: David Hedley Subject: Re: kern/10029: many vm_fault: pager read errors Reply-To: David Hedley Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org The following reply was made to PR kern/10029; it has been noted by GNATS. From: David Hedley To: sheldonh@FreeBSD.org Cc: Subject: Re: kern/10029: many vm_fault: pager read errors Date: Tue, 22 Jun 1999 11:44:32 +0000 (GMT) On Tue, 22 Jun 1999 sheldonh@FreeBSD.org wrote: > Synopsis: many vm_fault: pager read errors > > State-Changed-From-To: open->feedback > State-Changed-By: sheldonh > State-Changed-When: Tue Jun 22 03:57:16 PDT 1999 > State-Changed-Why: > David, have you had an opportunity to test for closure on a more recent > version of FreeBSD, possibly even CURRENT? I haven't tried current. The problem was still present with 3.2 though. It's fairly easy to reproduce (although the following doesn't always work). If machine A is an NFS server and machine B is an NFS client. Run an executable on machine B from the NFS filesystem. While the executable is still running, recompile it on machine A. Then send the running process a signal of some description (I usually notice the problem when I control-C the process). There is then a good chance that the problem described above will occur. David This email has been virus scanned by intY using Sophos Anti-Virus To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message