From owner-freebsd-amd64@FreeBSD.ORG Mon Sep 18 09:38:59 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 4F06116A403 for ; Mon, 18 Sep 2006 09:38:59 +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 2BEF943D97 for ; Mon, 18 Sep 2006 09:34:28 +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 1GPFW4-000CHJ-ED; Mon, 18 Sep 2006 12:34:16 +0300 X-Mailer: exmh version 2.7.2 01/07/2005 with nmh-1.2 To: Gary Jennejohn In-reply-to: <200609180911.k8I9BZjS001141@peedub.jennejohn.org> References: <200609180911.k8I9BZjS001141@peedub.jennejohn.org> Comments: In-reply-to Gary Jennejohn message dated "Mon, 18 Sep 2006 11:11:35 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 18 Sep 2006 12:34:16 +0300 From: Danny Braniss Message-ID: Cc: Christos Zoulas , 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: Mon, 18 Sep 2006 09:38:59 -0000 > Danny Braniss writes: > > > > 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 tempor > > arily > > > > | unavailable > > > > | > > > > | or error = EAGAIN (ED :-) > > > > > > > > heh! > > > > > > > > FreeBSD's vm system is very different from NetBSD's, and I am not familia > > r > > > > with it. The first and easiest thing to do is to check if the resource li > > mit > > > > for locked memory is set too low. Then hunt in the kernel sources for mlo > > ckall > > > > 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 :-) > > > > some more information: > > an am-utils child will exit on signal 11 > > (so far can't get the core) whenever memory gets tite. > > > > Maybe you need to set kern.sugid_coredump to 1? no luck :-(, and btw amd is not set-uid, it's just run as root. danny