From owner-freebsd-hackers Mon Feb 16 16:50:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA20782 for freebsd-hackers-outgoing; Mon, 16 Feb 1998 16:50:49 -0800 (PST) (envelope-from owner-freebsd-hackers@FreeBSD.ORG) Received: from pat.idi.ntnu.no (0@pat.idi.ntnu.no [129.241.103.5]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA20667 for ; Mon, 16 Feb 1998 16:50:13 -0800 (PST) (envelope-from Tor.Egge@idi.ntnu.no) Received: from idi.ntnu.no (tegge@presis.idi.ntnu.no [129.241.111.173]) by pat.idi.ntnu.no (8.8.8/8.8.8) with ESMTP id BAA19740; Tue, 17 Feb 1998 01:41:20 +0100 (MET) Message-Id: <199802170041.BAA19740@pat.idi.ntnu.no> To: mike@smith.net.au Cc: toor@dyson.iquest.net, hackers@FreeBSD.ORG Subject: Re: VM messed: vm_page_free panic problem In-Reply-To: Your message of "Mon, 16 Feb 1998 15:58:17 -0800" References: <199802162358.PAA08389@dingo.cdrom.com> X-Mailer: Mew version 1.70 on Emacs 19.34.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Tue, 17 Feb 1998 01:41:20 +0100 From: Tor Egge Sender: owner-freebsd-hackers@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > Would this mean that in "normal" use, attempting to execute something > off an MFS would also cause problems? Yes. A lot of swapping and a highly fragmented file system on MFS should help provoking this problem. I've not tested this change when mfs uses a file image (i.e. the -F option to mount_mfs). > Thanks for the fix; it looks as though I was, indeed, chasing yet > another wrong (but oddly functional) answer to the problem. I owe you > a beer. I assume you are going to commit this and check whether 2.2.5-STABLE should have a similar change. Would a Diet Coke or a Pepsi Max be acceptable instead of a beer ? - Tor Egge To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message