From owner-freebsd-amd64@FreeBSD.ORG  Wed Aug 15 06:38:41 2007
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
Delivered-To: freebsd-amd64@FreeBSD.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34])
	by hub.freebsd.org (Postfix) with ESMTP id D406F16A417;
	Wed, 15 Aug 2007 06:38:41 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from cs1.cs.huji.ac.il (cs1.cs.huji.ac.il [132.65.16.10])
	by mx1.freebsd.org (Postfix) with ESMTP id 8DC1413C468;
	Wed, 15 Aug 2007 06:38:41 +0000 (UTC)
	(envelope-from danny@cs.huji.ac.il)
Received: from pampa.cs.huji.ac.il ([132.65.80.32])
	by cs1.cs.huji.ac.il with esmtp
	id 1ILCWd-0002bp-OZ; Wed, 15 Aug 2007 09:38:39 +0300
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: am-utils@fsl.cs.sunysb.edu
In-reply-to: Your message of Mon, 06 Aug 2007 13:40:59 +0300 .
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Wed, 15 Aug 2007 09:38:39 +0300
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1ILCWd-0002bp-OZ@cs1.cs.huji.ac.il>
Cc: freebsd-current@FreeBSD.org, freebsd-amd64@FreeBSD.org
Subject: Re: amd crashes when memory is low 
X-BeenThere: freebsd-amd64@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
List-Id: Porting FreeBSD to the AMD64 platform <freebsd-amd64.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-amd64>
List-Post: <mailto:freebsd-amd64@freebsd.org>
List-Help: <mailto:freebsd-amd64-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-amd64>,
	<mailto:freebsd-amd64-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Aug 2007 06:38:42 -0000

> > Hi,
> > 	This is not new, but now that freebsd current is almost out, I'm
> > trying it out again. amd (am-utils version 6.1.5) on an amd64 will crash when
> > vm memory is low. In the past it was suggested to add 'plock=no' to
> > /etc/amd.conf, but I have to check if it's read since I still see:
> > 	Couldn't lock process pages in memory using mlockall(): \
> > 		Resource temporarily unavailable
> > 
> > I'll try it out under i386 and report later.
> 
> ok, it works under i386, because mlockall() does not fail, and hence
> amd is locked in core, while it failes under amd64. this does not explain
> why it crashes when swapped out, but that is another problem?
> 

to the am-utils maintainers:
	changing the call to mlockall, from
		mlockall(MCL_FUTURE|MCL_CURRENT)
	to
		mlockall(MCL_FUTURE)
solves the problem.

danny