public inbox for isar-users@googlegroups.com
 help / color / mirror / Atom feed
From: Alexander Smirnov <asmirnov@ilbers.de>
To: Claudius Heine <claudius.heine.ext@siemens.com>,
	isar-users@googlegroups.com
Subject: Re: [PATCH] isar-bootstrap: Increase cache room
Date: Mon, 14 May 2018 12:21:12 +0300	[thread overview]
Message-ID: <3b32103f-8766-6633-503e-04220b68e9b2@ilbers.de> (raw)
In-Reply-To: <3c2e0ed3-a0c2-5aca-37b8-ef5b884f8697@siemens.com>

Hi,

On 05/14/2018 12:11 PM, Claudius Heine wrote:
> On 2018-05-14 10:54, [ext] Claudius Heine wrote:
>> Hi Alex,
>>
>> On 2018-05-07 17:48, Alexander Smirnov wrote:
>>> According to the man page for 'apt.conf', there are three variables:
>>>   - Cache-Start: initial size of mmap cache room
>>>   - Cache-Grow: gap for dynamic mmap cache growth
>>>   - Cache-Limit: maximal cache size after growth
>>>
>>> If dynamic resize of mmap region is not avaialbe, the apt uses
>>> pre-allocated Cache-Start room [1] for mmap file.
>>>
>>> Building Isar on one of the Debian host with kernel 3.4, I got the
>>> following problem for 'qemuarm64-stretch' configuration:
>>>
>>> 8<--
>>> Hit:1 http://security.debian.org stretch/updates InRelease
>>> Ign:2 http://ftp.de.debian.org/debian stretch InRelease
>>> Hit:3 http://ftp.de.debian.org/debian stretch-updates InRelease
>>> Hit:4 http://ftp.de.debian.org/debian stretch Release
>>> E: Dynamic MMap ran out of room. Please increase the size of 
>>> APT::Cache-Start. Current value: 25165824. (man 5 apt.conf)
>>> qemu: uncaught target signal 11 (Segmentation fault) - core dumped
>>> Segmentation fault
>>> 8<--
>>>
>>> I have no information, why exactly the room could not be re-sized on 
>>> this
>>> system, but it would be better to increase the initial room size for 
>>> apt.
>>> This patch increases the default apt cache twice.
>>>
>>> Signed-off-by: Alexander Smirnov <asmirnov@ilbers.de>
>>> ---
>>>   meta/recipes-core/isar-bootstrap/isar-bootstrap.bb | 4 +++-
>>>   1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb 
>>> b/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
>>> index a38dd88..4cdefaa 100644
>>> --- a/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
>>> +++ b/meta/recipes-core/isar-bootstrap/isar-bootstrap.bb
>>> @@ -187,7 +187,9 @@ do_apt_update() {
>>>       E="${@bb.utils.export_proxies(d)}"
>>>       export DEBIAN_FRONTEND=noninteractive
>>> -    sudo -E chroot "${ROOTFSDIR}" /usr/bin/apt-get update -y
>>> +    sudo -E chroot "${ROOTFSDIR}" /usr/bin/apt-get update -y \
>>> +                                      -o APT::Cache-Start=50331648
>>> +
>>
>> If this is needed, then it might be better to set this option in a 
>> apt-preferences file with the "DISTRO_APT_PREFERENCES" variable.
> 
> Ah, sorry. I was wrong. I meant setting this is isar-apt.conf.
> 

This option is needed only for isar build and should be dropped from 
target rootfs, because target rootfs has correct versions of apt and 
kernel. So please see v2 version of this patch: I've added the temporary 
conf file which is removed during rootfs creation. I found this easier 
than 'sedding' isar-apt.conf.

Alex

>>
>> Cheers,
>> Claudius
>>
>>>       sudo -E chroot "${ROOTFSDIR}" /usr/bin/apt-get dist-upgrade -y \
>>>                                         -o Debug::pkgProblemResolver=yes
>>>   }
>>>
>>
> 

      reply	other threads:[~2018-05-14  9:21 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-07 15:48 Alexander Smirnov
2018-05-07 15:57 ` Alexander Smirnov
2018-05-07 16:31   ` Henning Schild
2018-05-07 16:48     ` Alexander Smirnov
2018-05-07 17:12       ` Henning Schild
2018-05-08  7:56         ` Alexander Smirnov
2018-05-08  8:56           ` Henning Schild
2018-05-08  9:07             ` Alexander Smirnov
2018-05-08  9:22               ` Henning Schild
2018-05-08  9:27                 ` Alexander Smirnov
2018-05-08 10:30                   ` Henning Schild
2018-05-14  8:54 ` Claudius Heine
2018-05-14  9:11   ` Claudius Heine
2018-05-14  9:21     ` Alexander Smirnov [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=3b32103f-8766-6633-503e-04220b68e9b2@ilbers.de \
    --to=asmirnov@ilbers.de \
    --cc=claudius.heine.ext@siemens.com \
    --cc=isar-users@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox