From owner-freebsd-stable  Fri Oct 10 06:23:27 1997
Return-Path: <owner-freebsd-stable>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id GAA13004
          for stable-outgoing; Fri, 10 Oct 1997 06:23:27 -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 GAA12994
          for <freebsd-stable@freebsd.org>; Fri, 10 Oct 1997 06:23:22 -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 GAA19694; Fri, 10 Oct 1997 06:23:20 -0700 (PDT)
Date: Fri, 10 Oct 1997 06:23:19 -0700 (PDT)
From: Chris Caputo <ccaputo@alt.net>
To: freebsd-stable@freebsd.org
Subject: 2.1-stable: "vnode_pager_input: I/O read error" messages
Message-ID: <Pine.BSI.3.93.971010061432.19137C-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

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. 

This happens in vnode_pager_input(), which no longer appears to exist in
2.2-stable or current.

It does not appear that we actually have a hardware problem (disks check
out, controller checks out, etc.).

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
...