From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6727995572123336704 X-Received: by 2002:a05:6512:304:: with SMTP id t4mr21866024lfp.15.1567527836654; Tue, 03 Sep 2019 09:23:56 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a2e:87d5:: with SMTP id v21ls2020396ljj.5.gmail; Tue, 03 Sep 2019 09:23:55 -0700 (PDT) X-Google-Smtp-Source: APXvYqxhJuURxBRnUfT2UQh6cL7zxpAVDR4DcsGTcJJ07NbSoKfyOkvV4JnHnX7Jxm2mxBxjgkOT X-Received: by 2002:a2e:5d17:: with SMTP id r23mr10815263ljb.229.1567527835965; Tue, 03 Sep 2019 09:23:55 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1567527835; cv=none; d=google.com; s=arc-20160816; b=h3l7vOhKnXEx3ZPo4TZEiM+CxLc1U4vRjVMrxqsn7ARsiByyUJmW7/t3Qxu/H5rCVr NNSa1g0ux6zwPHozmDUeGcRPs5Vr4aordlCoNgPYLCbSq/EAgQUm2mnxjhHsQAdG1s7e a32cXySZyXw3ph5PEhaFMlwCGe5BCa7LszF0denR6I4z86B8BrGrS5E5eU3+v3hyGdTo Ibh61pOJtGsZSxJyIbm7JRDTU0hfLObZSXYBgOtJ02anruTh/TtiS9jKx1Afn0L1Hxom Q6x8qjtcgcTu7DfOtLT4PK6axHK4uowlNXvD1NdP1I0c6hhKDo636PvTsUbwOCh3KcSA tnUg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=content-transfer-encoding:content-language:in-reply-to:mime-version :user-agent:date:message-id:from:references:to:subject; bh=03k4lMyOrPkjGOv348yqNHdZgE92IE2o10UaqHey6Gc=; b=jn3o73tnEexevBV+9h4ecab6Ulk3gsBAz/m8D0vXwrnDoYgnthtYGX7EIhylLGsDCY nDmc6PhRMNvKHmaOBiMkWxFEqvC4YXFe7sBCWTvvfr3FSpqT1x8bizYjJdvSDcBJRTzq OS4YWPkwTHHowQ0IAMC59I89luxvknDIPCyZSrJwfWCOvSZARTiPZ6ooFPgM/aFiY3pm ZZ67xiCThvcwViewiQRFopiSFbGjv3B/nhfKrBAh1OBcDQg7bxfHyqS9o6vWdIHrg0eZ RBcSgvvP1vqp15trzX9S/0wYykpBe43/n64YZ8ytreU+FatKUORUVnbO+JE7MBvUCDH7 nlfw== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Return-Path: Received: from thoth.sbs.de (thoth.sbs.de. [192.35.17.2]) by gmr-mx.google.com with ESMTPS id i21si791371ljj.1.2019.09.03.09.23.55 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Sep 2019 09:23:55 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) client-ip=192.35.17.2; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 192.35.17.2 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by thoth.sbs.de (8.15.2/8.15.2) with ESMTPS id x83GNtEp027726 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK) for ; Tue, 3 Sep 2019 18:23:55 +0200 Received: from [139.25.68.37] (md1q0hnc.ad001.siemens.net [139.25.68.37] (may be forged)) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x83GNssU022238 for ; Tue, 3 Sep 2019 18:23:55 +0200 Subject: Re: isar-bootstrap failures with debian-buster targets To: isar-users References: <20190822144706.GA6062@yssyq.m.ilbers.de> <00b7f2ea-a868-c06e-e64f-e735482be819@siemens.com> <20190822152700.GB6062@yssyq.m.ilbers.de> <20190827043332.GJ6062@yssyq.m.ilbers.de> <5b671fed-4dbc-1beb-e9bd-3f67b1a804df@siemens.com> <20190903154447.GE6062@yssyq.m.ilbers.de> From: Jan Kiszka Message-ID: Date: Tue, 3 Sep 2019 18:23:54 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: <20190903154447.GE6062@yssyq.m.ilbers.de> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit X-TUID: gaTVIZpjOo+d On 03.09.19 17:44, Baurzhan Ismagulov wrote: > On Tue, Aug 27, 2019 at 09:10:21AM +0200, Jan Kiszka wrote: >>> FWIW, this also occurred on an internal Jenkins machine (stretch host, stretch >>> workspace, no docker). This happening only with buster target, we have only two >>> candidates: bug in qemu or bug Debian, no? >> >> Yeah, stretch host does not seem to make a difference. I've seen it >> meanwhile also with the stretch-based kas image. >> >> Should we try to file bug? Question is: against which component? debootstrap? > > I think the best candidate would be the package containing the binary that > fails -- presumably apt. > > For me, the questions are: > > 1. Can we rule out qemu in some way? > > 2. Is it reproducible in a simple way? Well, for me at least: Just started the OrangePi Zero build of jailhouse-images, which is now buster-based, and it failed again. I suspect I can trigger this now for a couple of times in a row. > > I.e., ideally, it should be reproducible from the command line on the host > natively, otherwise we'll probably end up just having reported the problem -- > which is admittedly also necessary. > That's not where I am yet, only seeing it on my SUSE host. > > That said, the links below (at least one of which appears to be an automated > translation from English) refer to the same problem in the context of > Singularity, which would point rather into the direction of qemu. What is > actually the size of RAM available to the guest in our case? Apt has the > history of requiring considerable amounts of RAM. > > 1. https://issue.life/questions/51632062 > 2. https://bug200.com/post/51632062 > Well, we only saw the issue with armhf and mipsel so far, right? I did a lot of arm64 builds recently on the very same machine, which are qemu-based, and none failed this way. I do not know how much virtual memory qemu-user leaves the application, but it is already constrained to 32-bit. Hmm, there some tunables to qemu-user. I'm currently playing with QEMU_RESERVED_VA, will keep you posted... Jan -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux