From: Jan Kiszka <jan.kiszka@siemens.com>
To: daniel.sangorrin@toshiba.co.jp
Cc: cip-dev@lists.cip-project.org, isar-users@googlegroups.com
Subject: Re: isar error log
Date: Tue, 2 Apr 2019 08:13:55 +0200 [thread overview]
Message-ID: <0c1b977d-cd7e-34aa-8d7e-1569b313f75d@siemens.com> (raw)
In-Reply-To: <OSAPR01MB3763A7998474AB7ABEB3DDF3D0560@OSAPR01MB3763.jpnprd01.prod.outlook.com>
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/test-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.do_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-stretch-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-stretch-amd64/rootfs/test-dev-null: Permission denied
> | E: Cannot install into target '/work/build/tmp/work/cip-core-amd64/isar-bootstrap-host-debian-stretch-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-stretch-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
next prev parent reply other threads:[~2019-04-02 6:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-02 3:17 daniel.sangorrin
2019-04-02 6:13 ` Jan Kiszka [this message]
2019-04-03 0:56 ` daniel.sangorrin
2019-04-03 5:55 ` Jan Kiszka
2019-04-11 9:08 ` daniel.sangorrin
2019-04-11 9:15 ` Jan Kiszka
2019-04-11 10:05 ` daniel.sangorrin
2019-04-11 10:13 ` daniel.sangorrin
2019-04-11 12:42 ` Jan Kiszka
2019-04-12 11:37 ` Henning Schild
2019-04-12 11:59 ` [cip-dev] " Ben Hutchings
2019-04-16 2:47 ` daniel.sangorrin
2019-04-16 3:04 ` daniel.sangorrin
2019-04-03 13:53 ` Ben Hutchings
2019-04-05 7:44 ` daniel.sangorrin
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=0c1b977d-cd7e-34aa-8d7e-1569b313f75d@siemens.com \
--to=jan.kiszka@siemens.com \
--cc=cip-dev@lists.cip-project.org \
--cc=daniel.sangorrin@toshiba.co.jp \
--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