From owner-freebsd-stable  Sat Oct 11 15:02:25 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id PAA12624
          for stable-outgoing; Sat, 11 Oct 1997 15:02:25 -0700 (PDT)
          (envelope-from owner-freebsd-stable)
Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA12584
          for <freebsd-stable@FreeBSD.ORG>; Sat, 11 Oct 1997 15:02:16 -0700 (PDT)
          (envelope-from ccaputo@alt.net)
Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id PAA24704 for <freebsd-stable@FreeBSD.ORG>; Sat, 11 Oct 1997 15:02:14 -0700 (PDT)
Date: Sat, 11 Oct 1997 15:02:14 -0700 (PDT)
From: Chris Caputo <ccaputo@alt.net>
Reply-To: Chris Caputo <ccaputo@alt.net>
To: freebsd-stable@FreeBSD.ORG
Subject: Re: 2.1-stable: "vnode_pager_input: I/O read error" messages 
In-Reply-To: <199710110933.TAA01099@word.smith.net.au>
Message-ID: <Pine.BSI.3.93.971011145523.21512M-100000@baklava.alt.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 11 Oct 1997, Mike Smith wrote:
> > Hi.  Does anyone have any insight into what these messages really mean or
> > what the fix is (besides going to 2.2-stable ;-)?  They seem to come in
> > spurts - none for a few days, then some for a few hours, then none for a
> > few days, etc. 
> 
> The error message means exactly what it says; an I/O read error 
> (probably hardware) has occurred.
> 
> This normally means that (surprise, surprise) you have harware problems.
> Are there any error messages coming from your disk controller?

Nope, no messages from the bt or sd device drivers.  No other kernel
messages besides these.  No system crashes happening either. 

> Sometimes RAM faults can cause these symptoms as well.

Possibly, but since the faults are isolated in a specific code area and
come and go, I doubt it.

> > It does not appear that we actually have a hardware problem (disks check
> > out, controller checks out, etc.).
> 
> What do you mean by "check out"?

Meaning no SCSI errors spewed by the kernel and no problems using
filesystems on them.

Funny thing is the problem will happen for a few hours one day and than go
for days without happening, and return, and then stop, etc. 

Thanks,
Chris

> > ...
> > Oct  9 08:23:43 x /kernel: vnode_pager_input: I/O read error
> > Oct  9 08:23:43 x /kernel: vm_fault: pager input (probably hardware) error, PID 14142 failure
> > Oct  9 08:23:43 x /kernel: pid 14142 (in.nnrpd), uid 0: exited on signal 11
> > Oct  9 08:34:57 x /kernel: vnode_pager_input: I/O read error
> > Oct  9 08:34:57 x /kernel: vm_fault: pager input (probably hardware) error, PID 17219 failure
> > Oct  9 08:34:57 x /kernel: pid 17219 (in.nnrpd), uid 0: exited on signal 11
> > ...