From nobody  Thu Feb 11 07:37:46 1999
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id HAA03174;
          Thu, 11 Feb 1999 07:37:46 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199902111537.HAA03174@hub.freebsd.org>
Date: Thu, 11 Feb 1999 07:37:46 -0800 (PST)
From: david@inty.net
To: freebsd-gnats-submit@freebsd.org
Subject: many vm_fault: pager read errors
X-Send-Pr-Version: www-1.0

>Number:         10029
>Category:       kern
>Synopsis:       many vm_fault: pager read errors
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Thu Feb 11 07:40:00 PST 1999
>Closed-Date:    Tue Aug 10 05:54:54 PDT 1999
>Last-Modified:  Thu Dec  9 03:30:01 PST 1999
>Originator:     David Hedley
>Release:        2.2.x and 3.0
>Organization:
Intelligent Network Technologies Ltd
>Environment:
FreeBSD inty.david.inty.net 3.0-RELEASE FreeBSD 3.0-RELEASE #2: Fri Jan  8 19:02:26 GMT 1999     david@brian.visint.co.uk:/usr/src/sys/compile/NEWINTY  i386
>Description:
Quite often when a program I have written exits on a signal (usually INT),
the kernel generates an endless stream of 'vm_fault: pager read error, pid ....'
on the console. Doing a kill -9 on the process in question stops the error
messages. This is definitely _not_ a hardware problem and occurs both with
2.2.5-8 and 3.0 kernels.
>How-To-Repeat:

>Fix:
kill -9 on the problem process.
>Release-Note:
>Audit-Trail:

From: David Greenman <dg@root.com>
To: david@inty.net
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/10029: many vm_fault: pager read errors 
Date: Thu, 11 Feb 1999 08:45:35 -0800

 >>Description:
 >Quite often when a program I have written exits on a signal (usually INT),
 >the kernel generates an endless stream of 'vm_fault: pager read error, pid ....'
 >on the console. Doing a kill -9 on the process in question stops the error
 >messages. This is definitely _not_ a hardware problem and occurs both with
 >2.2.5-8 and 3.0 kernels.
 
    Are you running the binaries over NFS?
 
 -DG
 
 David Greenman
 Co-founder/Principal Architect, The FreeBSD Project

From: David Hedley <david@inty.co.uk>
To: David Greenman <dg@root.com>
Cc: freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/10029: many vm_fault: pager read errors 
Date: Thu, 11 Feb 1999 16:49:19 +0000 (GMT)

 On Thu, 11 Feb 1999, David Greenman wrote:
 
 > >>Description:
 > >Quite often when a program I have written exits on a signal (usually INT),
 > >the kernel generates an endless stream of 'vm_fault: pager read error, pid ....'
 > >on the console. Doing a kill -9 on the process in question stops the error
 > >messages. This is definitely _not_ a hardware problem and occurs both with
 > >2.2.5-8 and 3.0 kernels.
 > 
 >    Are you running the binaries over NFS?
 > 
 
 Yes, served from another FreeBSD machine.
 
 David
 --
 Dr David Hedley,Inty Development,Bristol,UK,0117 9050500,http://www.inty.net/
 

From: Matthew Dillon <dillon@apollo.backplane.com>
To: David Hedley <david@inty.co.uk>
Cc: David Greenman <dg@root.com>, freebsd-gnats-submit@FreeBSD.ORG
Subject: Re: kern/10029: many vm_fault: pager read errors 
Date: Sat, 13 Feb 1999 02:18:56 -0800 (PST)

     This report appears to be based on a 3.0 release kernel.  There were a 
     number of NFS bugs fixed between that release and the 3.x stable
     release.  If this is a bug report based on the 3.x stable branch 
     rather then 3.0 release, there were a significant number of NFS bugs
     fixed after the January 8th kernel shown in the report.  The fact
     that it also occurs with a 2.2.8 kernel is also telling - it means
     that it is a long standing NFS bug.
 
     I presume these are NFS V2 mounts?  If not, try making them NFS V2
     mounts.
 
     It's hard to tell whether this bug has been fixed due to the number
     of bug fixes that have gone into NFS.  I think David is going to
     have to upgrade ( or wait for the 3.1 release and upgrade to that )
     in order to determine whether the bug has been addressed already.
 
 					-Matt
 					Matthew Dillon 
 					<dillon@backplane.com>
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? 

From: David Hedley <david@inty.co.uk>
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
 
 
State-Changed-From-To: feedback->suspended 
State-Changed-By: sheldonh 
State-Changed-When: Tue Jun 22 04:49:18 PDT 1999 
State-Changed-Why:  
Submitter confirms that the problem exists in 3.2-RELEASE using NFS 
defaults. Will re-open when NFS fixes in CURRENT have been back-ported 
to STABLE (*hollow.laugh*) . 
 
State-Changed-From-To: suspended->feedback 
State-Changed-By: sheldonh 
State-Changed-When: Mon Jul 5 05:29:20 PDT 1999 
State-Changed-Why:  
David, you might want to give this another bash using 3.2-STABLE, since 
a number of NFS cleanups were committed to RELENG_3 last week. 
State-Changed-From-To: feedback->closed 
State-Changed-By: sheldonh 
State-Changed-When: Tue Aug 10 05:54:54 PDT 1999 
State-Changed-Why:  
Timed out waiting for feedback from originator. 

From: Lars Eggert <larse@isi.edu>
To: freebsd-gnats-submit@freebsd.org, david@inty.net
Cc:  
Subject: Re: kern/10029: many vm_fault: pager read errors
Date: Fri, 12 Nov 1999 10:46:50 -0800 (PST)

 Hi,
 
 I think I see the same problem David described using 3.2-RELEASE. Recompiling
 a binary that is NFS mounted and currently running results in "/kernel:
 vm_fault: pager read error" in some cases, in other cases, the machine just
 freezes up.
 
 Has this been resolved in the meantime? Otherwise, maybe the problem report
 should be reopened. Please let me know if I can provide any additional info to
 help track down this problem.
 
 Lars
 ______________________________________________________________________________
 Lars Eggert <larse@isi.edu>                     Information Sciences Institute
 http://www.isi.edu/~larse/                   University of Southern California
 

From: "David Hedley" <david@inty.co.uk>
To: <freebsd-gnats-submit@freebsd.org>
Cc:  
Subject: Re: kern/10029: many vm_fault: pager read errors
Date: Thu, 9 Dec 1999 11:22:05 -0000

 Just to let you know that I'm still seeing this with the 3.3-RELEASE kernel
 
 Cheers,
 
 David
 --
 Dr David Hedley, Head of Development
 Intelligent Network Technology Ltd, Bristol, UK
 http://www.inty.net/
 
 
 This email has been virus scanned using Sophos Anti-Virus by intY (www.inty.net)
 
 
>Unformatted:
