From owner-freebsd-current Sat May 2 14:52:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA22856 for freebsd-current-outgoing; Sat, 2 May 1998 14:52:25 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from cimlogic.com.au (cimlog.lnk.telstra.net [139.130.51.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA22848; Sat, 2 May 1998 14:52:20 -0700 (PDT) (envelope-from jb@cimlogic.com.au) Received: (from jb@localhost) by cimlogic.com.au (8.8.8/8.8.7) id HAA09919; Sun, 3 May 1998 07:54:18 +1000 (EST) (envelope-from jb) From: John Birrell Message-Id: <199805022154.HAA09919@cimlogic.com.au> Subject: VM changes broke SYSVSHM? To: dyson@FreeBSD.ORG Date: Sun, 3 May 1998 07:54:18 +1000 (EST) Cc: current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG John, With a kernel including vm_map.c 1.123, my SYSVSHM tests fail in a process that forks. I tried a kernel from Apr 20 sources and that is OK. Are we entering another period of sustained VM instability? 8-) Now is not a good time. Is it possible/practical for you to branch your VM changes and have a few brave souls follow you down the branch to shake out the bugs? -- John Birrell - jb@cimlogic.com.au; jb@freebsd.org http://www.cimlogic.com.au/ CIMlogic Pty Ltd, GPO Box 117A, Melbourne Vic 3001, Australia +61 418 353 137 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message