From owner-freebsd-current@FreeBSD.ORG Wed Jan 12 09:06:42 2011 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 47A231065670 for ; Wed, 12 Jan 2011 09:06:42 +0000 (UTC) (envelope-from pluknet@gmail.com) Received: from mail-qy0-f182.google.com (mail-qy0-f182.google.com [209.85.216.182]) by mx1.freebsd.org (Postfix) with ESMTP id 006CC8FC13 for ; Wed, 12 Jan 2011 09:06:41 +0000 (UTC) Received: by qyk36 with SMTP id 36so351030qyk.13 for ; Wed, 12 Jan 2011 01:06:41 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:date:message-id:subject:from:to :content-type; bh=UYFoZdng1nAoPQ5Zr8db5hZGVWkZKBn2/yCAEA0+tTA=; b=Vb/eY5JUv3G1I20bNa+ew15xsg3MrXRTIXBOxZVPWwWcrRsf2EEu44z5mW1MNBgnHP 3BrIHo+O0YDzfqth8yp6H0tqRjm2eknUDZ1MUncrf+qpzXrtm2bbhukIQHQJf5autbc6 iT79x/JBxnQE2jCEp9Y9IT1rtEcRJOVxq89Ys= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=o9sT2AWlY6ZbcZQ7tvQMbgdtXxDIR0dmZnfci58FZzwesA8OVVrHZ1+IBy9cIsah1H Lvq8pvIkY1toSyQwzfFTDIdU6KNe/KP32TO7Nxi50SV9i0t4RAYxNcZYQXygyVb3/fy6 jTEerhDcH9asm4ZJoy0wL9scOVArIRLqjDAP0= MIME-Version: 1.0 Received: by 10.229.211.138 with SMTP id go10mr635186qcb.195.1294823201017; Wed, 12 Jan 2011 01:06:41 -0800 (PST) Received: by 10.229.39.147 with HTTP; Wed, 12 Jan 2011 01:06:40 -0800 (PST) Date: Wed, 12 Jan 2011 12:06:40 +0300 Message-ID: From: Sergey Kandaurov To: FreeBSD Current Content-Type: text/plain; charset=ISO-8859-1 Subject: /sbin/init refuses to start with large physmem installed X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2011 09:06:42 -0000 Hi. The box I have observed such a problem has 458752 MB of real memory (RAM). With this high value /sbin/init refuses to start with "Out of memory". I suspect there may be sort of (type) overflow somewhere. A corresponding part of console output below: start_init: trying /sbin/init Cannot map anonymous memory(null): Out of memory: Cannot map anonymous memoryCannot allocate memory Enter full pathname of shell or RETURN for /bin/sh: Cannot map anonymous memory(null): Out of memory: Cannot map anonymous memoryCannot allocate memory Cannot map anonymous memory(null): Out of memory: Cannot map anonymous memoryCannot allocate memory Enter full pathname of shell or RETURN for /bin/sh: ^CCannot map anonymous memory(null): Out of memory: Cannot map anonymous memoryCannot allocate memory Cannot map anonymous memory(null): Out of memory: Cannot map anonymous memoryCannot allocate memory Enter full pathname of shell or RETURN for /bin/sh: Full dmesg + remain: http://plukky.net/~pluknet/misc/ibmx5.verbosedmesg.txt This is confirmed by the fact that it started to pass multiuser (up to login) after I've reduced hw.physmem down to 8GB. Any tips are appreciated. -- wbr, pluknet