Date: Sat, 16 Sep 2006 19:55:27 +0300 From: Danny Braniss <danny@cs.huji.ac.il> To: christos@zoulas.com (Christos Zoulas) Cc: freebsd-amd64@FreeBSD.org, am-utils@fsl.cs.sunysb.edu Subject: Re: mlockall() failes on amd64 Message-ID: <E1GOdRv-000H5P-Nt@cs1.cs.huji.ac.il> In-Reply-To: Your message of Sat, 16 Sep 2006 12:28:30 -0400 .
next in thread | raw e-mail | index | archive | help
> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?E1GOdRv-000H5P-Nt>