From owner-freebsd-current@FreeBSD.ORG Wed Apr 28 13:53:42 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 7683016A4CF; Wed, 28 Apr 2004 13:53:42 -0700 (PDT) Received: from newtrinity.zeist.de (newtrinity.zeist.de [217.24.217.8]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB47E43D31; Wed, 28 Apr 2004 13:53:41 -0700 (PDT) (envelope-from marius@newtrinity.zeist.de) Received: from newtrinity.zeist.de (localhost [127.0.0.1]) i3SKrf6F086943; Wed, 28 Apr 2004 22:53:41 +0200 (CEST) (envelope-from marius@newtrinity.zeist.de) Received: (from marius@localhost) by newtrinity.zeist.de (8.12.10/8.12.10/Submit) id i3SKraTp086942; Wed, 28 Apr 2004 22:53:36 +0200 (CEST) (envelope-from marius) Date: Wed, 28 Apr 2004 22:53:36 +0200 From: Marius Strobl To: Brian Fundakowski Feldman Message-ID: <20040428225336.E11722@newtrinity.zeist.de> References: <200404272254.i3RMscjL019357@green.homeunix.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <200404272254.i3RMscjL019357@green.homeunix.org>; from green@freebsd.org on Tue, Apr 27, 2004 at 06:54:37PM -0400 X-AntiVirus: checked by AntiVir Milter 1.1-beta; AVE 6.25.0.2; VDF 6.25.0.38 (host: newtrinity.zeist.de) cc: bms@freebsd.org cc: current@freebsd.org Subject: Re: mlockall(2 fixed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Apr 2004 20:53:42 -0000 On Tue, Apr 27, 2004 at 06:54:37PM -0400, Brian Fundakowski Feldman wrote: > Please try the following if you are having strange SIGBUS problems/leaked > wired memory and you are running programs that use mlockall(2). There were > several distinct bugs that caused pages to never get unwired and completely > unrelated processes to act as if mlockall(2) was called when they had not > done so. > This patch appears to fix the problems on the one box I could reproduce it.