From mboxrd@z Thu Jan 1 00:00:00 1970 X-GM-THRID: 6675131030513385472 X-Received: by 2002:a19:7418:: with SMTP id v24mr1068363lfe.3.1554270908608; Tue, 02 Apr 2019 22:55:08 -0700 (PDT) X-BeenThere: isar-users@googlegroups.com Received: by 2002:a19:7916:: with SMTP id u22ls82976lfc.10.gmail; Tue, 02 Apr 2019 22:55:07 -0700 (PDT) X-Google-Smtp-Source: APXvYqzbJLH+7q6fRZrzBk1NPxAA9VTByYwwFO3ds5g6Cdiggjc3JP2nVzAQ2NLADm8znJanBsT5 X-Received: by 2002:ac2:4427:: with SMTP id w7mr15319lfl.17.1554270907934; Tue, 02 Apr 2019 22:55:07 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1554270907; cv=none; d=google.com; s=arc-20160816; b=zOkSVbMWT0LSeujfvbOG9QuG2m+ulWLBFOIC5a297hQ8ZeORQOFMlWjqeS6RLYoAyE QJDEcGQ6LEZEt/cVdakfYEht6ZP91S8tuAdfok2FyUhO35tzt/V8yZ88aFmlqN/GImb6 4Xc7CFe1uKqdhLWdJ7iNHCFVJKKMtHFKYyV0l52lTyVPofAGZBj9oWkxtQjBr2WJPJUj zeoea0lXdqsGYEXGR6SbUdxGRnNebkCr8qqWiNRHwhh85pi93Ry5cpsz8hlUaNgGVRg1 xOJLbbFjazzCoJvW6H7+HesnRgWkN3ZdiZJ7hjxzn4qC4QHXaVTkKK2vKG5DzVvSFtmc US9w== 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:cc:to:subject; bh=2fM455SosAXun94lQTQZXmSlgN6JTT2hQBZfCkyiOjw=; b=rxfsDvIFtUIlt9GUifOKloVFHCmQcZwmHHfPlPbs373hF5aJp+31l0+0NKh+Amt/sL ptppyPhqwH1W1+yPorDrlCmrxpRCzRxH5aRcasL2wpeP7iH5v0lnuJV5iOFZ4X6XApCB 7WTCsTW4XAXcQE+fndWqyIAuD5X97xJtnLnFG44yc+oP419n7b1tSHi5F/ke/QOmyhiZ 0QklanGgM0hshtjPDWNoLif2+2Ht+klhQ9ZHbVmy4K3Ed2/mDHV71EddJJTl6oe1nH75 B6RdMy1Z0ERFFOhYo4Q4QohtEW/obFyRLUmsY02s+tziJIcTqJmluI4MVUPLAbBCRcq/ SCxQ== ARC-Authentication-Results: i=1; gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Return-Path: Received: from gecko.sbs.de (gecko.sbs.de. [194.138.37.40]) by gmr-mx.google.com with ESMTPS id h21si683433lfm.4.2019.04.02.22.55.07 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 02 Apr 2019 22:55:07 -0700 (PDT) Received-SPF: pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) client-ip=194.138.37.40; Authentication-Results: gmr-mx.google.com; spf=pass (google.com: domain of jan.kiszka@siemens.com designates 194.138.37.40 as permitted sender) smtp.mailfrom=jan.kiszka@siemens.com Received: from mail1.sbs.de (mail1.sbs.de [192.129.41.35]) by gecko.sbs.de (8.15.2/8.15.2) with ESMTPS id x335t6X6025625 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 3 Apr 2019 07:55:06 +0200 Received: from [167.87.8.24] ([167.87.8.24]) by mail1.sbs.de (8.15.2/8.15.2) with ESMTP id x335t5fk019794; Wed, 3 Apr 2019 07:55:05 +0200 Subject: Re: isar error log To: daniel.sangorrin@toshiba.co.jp Cc: cip-dev@lists.cip-project.org, isar-users@googlegroups.com, kas-devel References: <0c1b977d-cd7e-34aa-8d7e-1569b313f75d@siemens.com> From: Jan Kiszka Message-ID: <043f0dda-7df0-36d1-c9ae-d9d08d3298d5@siemens.com> Date: Wed, 3 Apr 2019 07:55:04 +0200 User-Agent: Mozilla/5.0 (X11; U; Linux i686 (x86_64); de; rv:1.8.1.12) Gecko/20080226 SUSE/2.0.0.12-1.1 Thunderbird/2.0.0.12 Mnenhy/0.7.5.666 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-TUID: OAdXIM2JJOAF On 03.04.19 02:56, daniel.sangorrin@toshiba.co.jp wrote: > Hi Jan, > > Yes I am following the Readme. > > The docker image id for kasproject/kas-isar is 9e9fe44e68d3 (I am using kas-docker script). And I am using That's the same version I have, and it works for me. > kas-docker --isar build kas.yml:board-qemu-amd64.yml > > Yes, it seems there are multiple errors: > /proc/sys/fs/binfmt_misc/register: Invalid argument > /test-dev-null: Permission denied > > Probably this is a bug or misconfiguration in Ubuntu. I will try to figure it out. > Adding kas-devel: Would be interesting to understand this so that we can fix it or at least document a workaround. Maybe you need to be in some privileged group in order to use privileged docker containers? That's how things work on SUSE. No one around is using Ubuntu, so that distro is likely a blind spot for our testing. Thanks Jan > -----Original Message----- > From: Jan Kiszka > Sent: Tuesday, April 2, 2019 3:14 PM > To: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) > Cc: cip-dev@lists.cip-project.org; isar-users@googlegroups.com > Subject: Re: isar error log > > On 02.04.19 05:17, daniel.sangorrin@toshiba.co.jp wrote: >> Hi Jan, >> >> I am trying to show CIP Core ISAR to some guys in Linaro Connect but I also met a binfmt related error. > > It's supposed to be fixed in the :latest kas-isar image. Are you using that? > >> I am using Ubuntu 16.04. Do you have a hint on how to solve this problem? >> I already installed qemu-user-static. The system service for binfmt seems to fail. >> >> Thanks, >> Daniel >> >> update-binfmts: warning: unable to close >> /proc/sys/fs/binfmt_misc/register: Invalid argument >> update-binfmts: warning: unable to enable binary format qemu-aarch64 >> update-binfmts: exiting due to previous errors > > That indeed indicate broken binfmt settings. > >> 2019-04-01 15:37:22 - INFO - kas 1.0 started >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - Using /repo as root for repository cip-core >> 2019-04-01 15:37:22 - INFO - /work/isar$ git cat-file -t ee5518cc6ecdade53dcafabfbb40ba4b0c505777 >> 2019-04-01 15:37:22 - INFO - Repository isar already contains ee5518cc6ecdade53dcafabfbb40ba4b0c505777 as commit >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - Using /repo as root for repository cip-core >> 2019-04-01 15:37:22 - INFO - /work/isar$ git status -s >> 2019-04-01 15:37:22 - INFO - /work/isar$ git rev-parse --verify HEAD >> 2019-04-01 15:37:22 - INFO - ee5518cc6ecdade53dcafabfbb40ba4b0c505777 >> 2019-04-01 15:37:22 - INFO - Repo isar has already been checked out with correct refspec. Nothing to do. >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - Using /repo as root for repository cip-core >> 2019-04-01 15:37:22 - INFO - /work/isar$ /tmp/tmp9u5m9ths /work/build >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - Using /repo as root for repository cip-core >> 2019-04-01 15:37:22 - INFO - /repo$ git rev-parse --show-toplevel >> 2019-04-01 15:37:22 - INFO - Using /repo as root for repository cip-core >> 2019-04-01 15:37:22 - INFO - /work/build$ /work/isar/bitbake/bin/bitbake -k -c build cip-core-image >> Loading cache: 100% >> |######################################################################################################################################| Time: 0:00:00 Loaded 19 entries from dependency cache. >> NOTE: Resolving any missing task queue dependencies Initialising >> tasks: 100% >> |##################################################################### >> ############################################################| Time: >> 0:00:00 >> NOTE: Executing RunQueue Tasks >> ERROR: isar-bootstrap-target-1.0-r0 do_bootstrap: Function failed: >> do_bootstrap (log file is located at >> /work/build/tmp/work/cip-core-amd64/isar-bootstrap-target/temp/log.do_ >> bootstrap.77) >> ERROR: Logfile of failure stored in: >> /work/build/tmp/work/cip-core-amd64/isar-bootstrap-target/temp/log.do_ >> bootstrap.77 >> Log data follows: >> | DEBUG: Executing shell function do_bootstrap >> | W: Target architecture is the same as host architecture; disabling >> | QEMU support >> | I: Running command: debootstrap --arch amd64 --verbose >> | --variant=minbase --include=locales >> | --components=main,contrib,non-free stretch >> | /work/build/tmp/work/cip-core-amd64/isar-bootstrap-target/rootfs >> | http://ftp.de.debian.org/debian >> | /usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create >> | /work/build/tmp/work/cip-core-amd64/isar-bootstrap-target/rootfs/tes >> | t-dev-null: Permission denied >> | E: Cannot install into target >> | '/work/build/tmp/work/cip-core-amd64/isar-bootstrap-target/rootfs' >> | mounted with noexec or nodev > > Hmm, there are more strange errors. Could it be that you forgot the "--isar" > after "kas-docker"? That would mean you are trying to run unprivileged which is doomed to fail. > >> | WARNING: exit code 1 from a shell command. >> | ERROR: Function failed: do_bootstrap (log file is located at >> | /work/build/tmp/work/cip-core-amd64/isar-bootstrap-target/temp/log.d >> | o_bootstrap.77) >> ERROR: Task (/work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap-target.bb:do_bootstrap) failed with exit code '1' >> ERROR: isar-bootstrap-host-1.0-r0 do_bootstrap: Function failed: >> do_bootstrap (log file is located at >> /work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stretch >> -amd64/temp/log.do_bootstrap.79) >> ERROR: Logfile of failure stored in: >> /work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stretch >> -amd64/temp/log.do_bootstrap.79 >> Log data follows: >> | DEBUG: Executing shell function do_bootstrap >> | W: Target architecture is the same as host architecture; disabling >> | QEMU support >> | I: Running command: debootstrap --arch amd64 --verbose >> | --variant=minbase --include=locales >> | --components=main,contrib,non-free stretch >> | /work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stret >> | ch-amd64/rootfs http://ftp.de.debian.org/debian >> | /usr/sbin/debootstrap: 1454: /usr/sbin/debootstrap: cannot create >> | /work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stret >> | ch-amd64/rootfs/test-dev-null: Permission denied >> | E: Cannot install into target >> | '/work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stre >> | tch-amd64/rootfs' mounted with noexec or nodev >> | WARNING: exit code 1 from a shell command. >> | ERROR: Function failed: do_bootstrap (log file is located at >> | /work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stret >> | ch-amd64/temp/log.do_bootstrap.79) >> ERROR: Task (/work/isar/meta/recipes-core/isar-bootstrap/isar-bootstrap-host.bb:do_bootstrap) failed with exit code '1' >> >> $ systemctl status systemd-binfmt.service ● systemd-binfmt.service - >> Set Up Additional Binary Formats >> Loaded: loaded (/lib/systemd/system/systemd-binfmt.service; static; vendor preset: enabled) >> Active: inactive (dead) >> Condition: start condition failed at Tue 2019-04-02 08:04:31 +07; 2h 1min ago >> none of the trigger conditions were met >> Docs: man:systemd-binfmt.service(8) >> man:binfmt.d(5) >> https://www.kernel.org/doc/Documentation/binfmt_misc.txt >> > > Jan > > -- > Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux > -- Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux