From owner-freebsd-stable Wed Nov 5 23:36:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA27546 for stable-outgoing; Wed, 5 Nov 1997 23:36:50 -0800 (PST) (envelope-from owner-freebsd-stable) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA27518; Wed, 5 Nov 1997 23:36:34 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost.gsoft.com.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA01751; Thu, 6 Nov 1997 18:02:49 +1030 (CST) Message-Id: <199711060732.SAA01751@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: dyson@FreeBSD.ORG cc: stable@FreeBSD.ORG Subject: Re: Suggestion for those running -stable In-reply-to: Your message of "Thu, 06 Nov 1997 01:49:22 CDT." <199711060649.BAA11016@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 06 Nov 1997 18:02:49 +1030 From: Mike Smith Sender: owner-freebsd-stable@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > FWIW: to those who are using 2.2.X in production: > > If the change that I just made to vm_page.c checks out with everyone, this > should fix a subtile, lurking VM bug. Can you (please?) characterise this bug? We're still chasing the "some things use 3x swap" problem, and if this is it, we have a whole *pile* of machines in remote locations to apply it to. If not, then I can save me a lot of work worrying about it. 8) mike