RE: isar error log

[<daniel.sangorrin@toshiba.co.jp>]

> -----Original Message-----
> From: Jan Kiszka <jan.kiszka@siemens.com>
> Sent: Thursday, April 11, 2019 6:16 PM
> To: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) <daniel.sangorrin@toshiba.co.jp>
> Cc: cip-dev@lists.cip-project.org; isar-users@googlegroups.com; kas-devel@googlegroups.com
> Subject: Re: isar error log
> 
> On 11.04.19 11:08, daniel.sangorrin@toshiba.co.jp wrote:
> >> From: Jan Kiszka <jan.kiszka@siemens.com>
> >> 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.
> >
> > OK, so I figured out that Ubuntu 16.04 was using the service "binfmt-support", not "systemd-binfmt".
> > For that reason, the "systemd-binfmt" service was inactive. However, "binfmt-support" is working fine.
> > I also checked that the post-install script of the qemu-user-static package had run correctly
> > and there were binfmt configuration files at /var/lib/binfmts/
> 
> But what prevented the container to tune the host kernel according to its needs?
> That is the intended resolution for the host not having the same settings as the
> container (or any at all).

To be honest I don't really know what binfmt is all about yet, so I can't even understand what you mean about "tuning the kernel".

By the way, I managed to update to the latest Ubuntu 4.4 kernel (145) and the problem persists. I tried to reinstall qemu-user-static etc but still fails humm
.
Also i just tested on Ubuntu 18.04 and there I can build with ISAR without problems. So I might just leave it unsolved and update to 18.04...

Thanks,
Daniel





> 
> Jan
> 
> >
> > I am going to try with Ubuntu 18.04 (which worked fine for Suzuki-san) and then try to compare both.
> >
> > Thanks,
> > Daniel
> >
> >
> >
> >
> >
> >
> >>
> >> Thanks
> >> Jan
> >>
> >>> -----Original Message-----
> >>> From: Jan Kiszka <jan.kiszka@siemens.com>
> >>> Sent: Tuesday, April 2, 2019 3:14 PM
> >>> To: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ) <daniel.sangorrin@toshiba.co.jp>
> >>> 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
> 
> --
> Siemens AG, Corporate Technology, CT RDA IOT SES-DE
> Corporate Competence Center Embedded Linux