From owner-freebsd-arm@FreeBSD.ORG Thu Jun 20 13:43:56 2013 Return-Path: Delivered-To: freebsd-arm@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id E8481D07 for ; Thu, 20 Jun 2013 13:43:56 +0000 (UTC) (envelope-from zbb@semihalf.com) Received: from mail-bk0-x234.google.com (mail-bk0-x234.google.com [IPv6:2a00:1450:4008:c01::234]) by mx1.freebsd.org (Postfix) with ESMTP id 77A321A26 for ; Thu, 20 Jun 2013 13:43:56 +0000 (UTC) Received: by mail-bk0-f52.google.com with SMTP id d7so2861409bkh.39 for ; Thu, 20 Jun 2013 06:43:55 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=message-id:date:from:organization:user-agent:mime-version:to:cc :subject:references:in-reply-to:content-type :content-transfer-encoding:x-gm-message-state; bh=iOLclm+MkryW2DydlBXQtcvucbPALMAVXQyT/ijFB4w=; b=FsvWC19hITRwvfQq913sGEZf1LLSimmnAqCzHWPXS/slVj11sQrHBABdF8SQARpNSf TkwTUPSvnwRiidMtdvUbeY0Bq0MZy7wCM+Em+dVgdH8hW38QObx0UN/34DE9ULoNgXwH ab8PqvafcofTL65z7WZojMS9K/w2YuIJo3zxlmPNY+QcInmYsFdE+YJEd/yapqgaYk52 keMaLYoM0uZbGpCYWEiZ4MW5p35bPu6lhNFVBVB8xuWo7FjGqoSi0/WcJeg3l2Qcb5pe jSi4Rtl7NpHYc5PZ3yCcNtY0ZNubPe3fX5ZISuFNufCqKKVh84smli1uDWzyWKnpDi70 0yig== X-Received: by 10.204.231.137 with SMTP id jq9mr1124019bkb.150.1371735835401; Thu, 20 Jun 2013 06:43:55 -0700 (PDT) Received: from [10.0.2.117] (cardhu.semihalf.com. [213.17.239.108]) by mx.google.com with ESMTPSA id eu16sm247855bkc.0.2013.06.20.06.43.53 for (version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Thu, 20 Jun 2013 06:43:54 -0700 (PDT) Message-ID: <51C30718.4030805@semihalf.com> Date: Thu, 20 Jun 2013 15:43:52 +0200 From: Zbyszek Bodek Organization: Semihalf User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:17.0) Gecko/20130510 Thunderbird/17.0.6 MIME-Version: 1.0 To: Andrey Fesenko Subject: Re: Kernel build fails on ARM: Cannot fork: Cannot allocate memory References: <51C1F53B.2080502@semihalf.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit X-Gm-Message-State: ALoCoQkpEhk+YhC7/C2+DyXESfkfY9SsOS1VforEBNwB6Yqy8auqMYKKbAnJ7b21A+hx0iFZNbjf Cc: "freebsd-arm@freebsd.org" , freebsd-current X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting FreeBSD to the StrongARM Processor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 20 Jun 2013 13:43:57 -0000 On 19.06.2013 20:22, Andrey Fesenko wrote: > On Wed, Jun 19, 2013 at 10:15 PM, Zbyszek Bodek wrote: >> Hello, >> >> I've been trying to compile the kernel on my ARMv7 platform using the >> sources from the current FreeBSD HEAD. >> >> make buildkernel <.....> -j5 >> >> 1/2 builds fails in the way described below: >> -------------------------------------------------------------------------- >> ing-include-dirs -fdiagnostics-show-option -nostdinc -I. >> -I/root/src/freebsd-arm-superpages/sys >> -I/root/src/freebsd-arm-superpages/sys/contrib/altq >> -I/root/src/freebsd-arm-superpages/sys/contrib/libfdt -D_KERNEL >> -DHAVE_KERNEL_OPTION_HEADERS -include opt_global.h -fno-common >> -finline-limit=8000 --param inline-unit-growth=100 --param >> large-function-growth=1000 -mno-thumb-interwork -ffreestanding -Werror >> /root/src/freebsd-arm-superpages/sys/ufs/ffs/ffs_snapshot.c >> Cannot fork: Cannot allocate memory >> *** [ffs_snapshot.o] Error code 2 >> 1 error >> *** [buildkernel] Error code 2 >> 1 error >> *** [buildkernel] Error code 2 >> 1 error >> 5487.888u 481.569s 7:35.65 1310.0% 1443+167k 1741+5388io 221pf+0w >> -------------------------------------------------------------------------- >> > > -j5 tricky :) I think it is necessary to build one may be in two > streams, as well as make the swap > Hello Andrey, I'm not sure whether you see my point. Just for the record, I've checked make <...> -j1 and with a swap file. The results are the same. Nevertheless, I have 2GB of main memory on my ARM target and this is more than sufficient to build the kernel without a necessity of swap, etc. What more, I never use more than ~300-400MB of memory during build even when the error occurs. What I'm saying is that, starting from the earlier mentioned commit I'm suffering from the Cannot fork: Cannot allocate memory + vm_thread_new: kstack allocation failed errors, while using exactly the same setup, etc. Best regards Zbyszek Bodek