From owner-freebsd-hardware@FreeBSD.ORG Wed Jun 13 01:46:50 2007 Return-Path: X-Original-To: freebsd-hardware@freebsd.org Delivered-To: freebsd-hardware@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 43B0016A46B for ; Wed, 13 Jun 2007 01:46:50 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: from smtp116.sbc.mail.sp1.yahoo.com (smtp116.sbc.mail.sp1.yahoo.com [69.147.64.89]) by mx1.freebsd.org (Postfix) with SMTP id 27FCC13C469 for ; Wed, 13 Jun 2007 01:46:50 +0000 (UTC) (envelope-from jin@george.lbl.gov) Received: (qmail 57654 invoked from network); 13 Jun 2007 01:20:10 -0000 Received: from unknown (HELO ?192.168.1.201?) (jinmtb@sbcglobal.net@67.111.218.237 with plain) by smtp116.sbc.mail.sp1.yahoo.com with SMTP; 13 Jun 2007 01:20:09 -0000 X-YMail-OSG: g9K.TIgVM1mSVT0m0b0Bk1evXF1oBn4mekgh_xILT.4.0PaSz2zXyDpk1QAwT0TvjmSAytb2GA-- Message-ID: <466F4642.8070001@george.lbl.gov> Date: Tue, 12 Jun 2007 18:20:02 -0700 From: Jin Guojun User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.13) Gecko/20061027 X-Accept-Language: zh, zh-CN, en To: John Baldwin References: <466B2B9F.5010308@lbl.gov> <466B4694.3060204@lbl.gov> <466B4B7E.4000006@lbl.gov> <200706121527.04274.jhb@freebsd.org> In-Reply-To: <200706121527.04274.jhb@freebsd.org> Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: what causes error -- ELF interpreter /libexec/ld-elf.so.1 not found X-BeenThere: freebsd-hardware@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: General discussion of FreeBSD hardware List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 13 Jun 2007 01:46:50 -0000 John Baldwin wrote: On Saturday 09 June 2007 08:53:18 pm Jin Guojun [VFFS] wrote: I believe that this is a memory sub-system bug somewhere because anything equal to or below 1G options MAXDSIZ="(1024*1024*1024)" will work regardless how many memory is installed in the system. I doubt this could be a hardware related issue although is memory size related. Finally find cause but no idea why -- in kernel configuration, following line causes the problem: options MAXDSIZ="(2097152U*1024)" Can anyone explain why this can cause /libexec/ld-elf.so.1 not seen for some program? This is setting aside 2GB for malloc which leaves only 1GB for all of mmap and stack. You probably don't have enough address space to map your binary. This does not quite explain the problem. First of all, the MAXDSIZ is the maximum size for users to set their own datasize limit by 'limit' utility. If user do not set a high limit for datasize, it should not be a problem. The second aspect also counters this assumption, for machines that have less than or equal to 1 GB memory, and setting the MAXDISZ = the maximum memory size will not cause such problem. For example, if the physical memory size is 512 MB, and setting MAXDSIZ=(512*1024*1024) will not cause this problem. Or if the physical memory is 1GB, setting MAXDSIZ=(1024*1024*1024) will not cause the problem either. I will try to build a similar system on an AMD box with 2GB and more memory to see if this will be a problem. -Jin