From owner-freebsd-amd64@FreeBSD.ORG  Sat Sep 16 16:55:32 2006
Return-Path: <owner-freebsd-amd64@FreeBSD.ORG>
X-Original-To: freebsd-amd64@FreeBSD.org
Delivered-To: freebsd-amd64@FreeBSD.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id B018C16A587
	for <freebsd-amd64@FreeBSD.org>; Sat, 16 Sep 2006 16:55:32 +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 216C543D45
	for <freebsd-amd64@FreeBSD.org>; Sat, 16 Sep 2006 16:55:31 +0000 (GMT)
	(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 1GOdRv-000H5P-Nt; Sat, 16 Sep 2006 19:55:27 +0300
X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2
To: christos@zoulas.com (Christos Zoulas)
In-reply-to: Your message of Sat, 16 Sep 2006 12:28:30 -0400 .
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Sat, 16 Sep 2006 19:55:27 +0300
From: Danny Braniss <danny@cs.huji.ac.il>
Message-ID: <E1GOdRv-000H5P-Nt@cs1.cs.huji.ac.il>
Cc: freebsd-amd64@FreeBSD.org, am-utils@fsl.cs.sunysb.edu
Subject: Re: mlockall() failes on amd64 
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: Sat, 16 Sep 2006 16:55:32 -0000

> On Sep 16,  7:17pm, danny@cs.huji.ac.il (Danny Braniss) wrote:
> -- Subject: Re: mlockall() failes on amd64
> 
> | > On Sep 16,  2:55pm, danny@cs.huji.ac.il (Danny Braniss) wrote:
> | > -- Subject: mlockall() failes on amd64
> | > 
> | > | with am-utils  6.1.5, on a amd64 6.1-STABLE kernel i see:
> | > | 	Couldn't lock process pages in memory using mlockall()
> | > | while it's ok on a i386:
> | > | 	Locked process pages in memory
> | > | 
> | > 
> | > We should really fix amd to print the errno string when system calls
> | > fail; now we can only scratch our heads.
> | > 
> | > christos
> | sorry, here is the full message:
> | Couldn't lock process pages in memory using mlockall(): Resource temporarily 
> | unavailable
> | 
> | or error = EAGAIN (ED :-)
> 
> heh!
> 
> FreeBSD's vm system is very different from NetBSD's, and I am not familiar
> with it. The first and easiest thing to do is to check if the resource limit
> for locked memory is set too low. Then hunt in the kernel sources for mlockall
> and print the arguments it passes to the vm system. Anyway, the error is not
> fatal, and amd should keep working after that.
> 
> christos

im trying to figure out why it core dumped, for the very first time, 
(and i don't have the core :-(, and the only thing that was special
on this host, is that we are trying out postgres with allot of memory
requierements, so i thought that maybe it's memory ...
oh well, bug-hunting hat still on :-)

thanks,
	danny