From owner-freebsd-amd64@FreeBSD.ORG Sat Sep 16 16:28:31 2006 Return-Path: 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 2745316A403 for ; Sat, 16 Sep 2006 16:28:31 +0000 (UTC) (envelope-from christos@zoulas.com) Received: from rebar.astron.com (rebar.astron.com [38.117.134.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id D92A843D45 for ; Sat, 16 Sep 2006 16:28:30 +0000 (GMT) (envelope-from christos@zoulas.com) Received: by rebar.astron.com (Postfix, from userid 10080) id 64A5856407; Sat, 16 Sep 2006 16:28:30 +0000 (UTC) From: christos@zoulas.com (Christos Zoulas) Date: Sat, 16 Sep 2006 12:28:30 -0400 In-Reply-To: from Danny Braniss (Sep 16, 7:17pm) Organization: Astron Software X-Mailer: Mail User's Shell (7.2.6 beta(4.pl1)+dynamic 20000103) To: Danny Braniss Message-Id: <20060916162830.64A5856407@rebar.astron.com> 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 16 Sep 2006 16:28:31 -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