From owner-freebsd-bugs  Mon Jun 17 22:00:04 1996
Return-Path: owner-bugs
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA26620
          for bugs-outgoing; Mon, 17 Jun 1996 22:00:04 -0700 (PDT)
Received: (from gnats@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id WAA26608;
          Mon, 17 Jun 1996 22:00:02 -0700 (PDT)
Date: Mon, 17 Jun 1996 22:00:02 -0700 (PDT)
Message-Id: <199606180500.WAA26608@freefall.freebsd.org>
To: freebsd-bugs
Cc: 
From: "John S. Dyson" <toor@dyson.iquest.net>
Subject: Re: kern/1330: vm_pageout_scan: page not inactive?
Reply-To: "John S. Dyson" <toor@dyson.iquest.net>
Sender: owner-bugs@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

The following reply was made to PR kern/1330; it has been noted by GNATS.

From: "John S. Dyson" <toor@dyson.iquest.net>
To: smpatel@freebsd.org
Cc: FreeBSD-gnats-submit@freebsd.org
Subject: Re: kern/1330: vm_pageout_scan: page not inactive?
Date: Mon, 17 Jun 1996 23:57:25 -0500 (EST)

 > 
 > I normally wouldn't report a bug on a kernel this out of date, but it's the
 > first time I've ever seen it, and I may never see it again.  The message
 > "vm_pageout_scan: page not inactive?" was repeatedly printed, and the system
 > hung.  This kernel has been running for ~ 2 weeks without any problems, the
 > only unusual thing was a modem hangup (ppp), only a few seconds before this
 > problem erupted.  Here is an exerpt from syslog:
 > 
 That problem *very* well understood, and has been fixed in the pageout
 daemon.  It was a very very tricky problem.
 
 Thanks!!!
 John