[cip-dev] [isar-cip-core] cip arm64 build breaks

[cip-dev] [isar-cip-core] cip arm64 build breaks

[Venkata.Pyla]

Hi Jan,

Thanks for the work to support secureboot in arm64.

I am building the arm64 image to check secureboot support in arm64, got the below error and do you have any idea about this error.

---------------------------------------
$ ./kas-container build kas-cip.yml:kas/board/qemu-arm64.yml:kas/opt/5.10.yml:kas/opt/bullseye.yml
:
.
I: Extracting liblzma5...
I: Extracting zlib1g...
W: Failure trying to run: chroot "/build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/rootfs" /sbin/ldconfig
W: See /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/rootfs/debootstrap/debootstrap.log for details
WARNING: exit code 1 from a shell command.
ERROR: Logfile of failure stored in: /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/temp/log.do_bootstrap.307
:
.
---------------------------------------
When I see the bootstrap log at the end it shows "Segmentation fault (core dumped)"

Thanks,
Venkata.

Re: [cip-dev] [isar-cip-core] cip arm64 build breaks

[Jan Kiszka]

On 10.05.22 14:06, Venkata.Pyla@toshiba-tsip.com wrote:
> Hi Jan,
> 
> Thanks for the work to support secureboot in arm64.
> 
> I am building the arm64 image to check secureboot support in arm64, got the below error and do you have any idea about this error.
> 
> ---------------------------------------
> $ ./kas-container build kas-cip.yml:kas/board/qemu-arm64.yml:kas/opt/5.10.yml:kas/opt/bullseye.yml
> :
> .
> I: Extracting liblzma5...
> I: Extracting zlib1g...
> W: Failure trying to run: chroot "/build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/rootfs" /sbin/ldconfig
> W: See /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/rootfs/debootstrap/debootstrap.log for details
> WARNING: exit code 1 from a shell command.
> ERROR: Logfile of failure stored in: /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/temp/log.do_bootstrap.307
> :
> .
> ---------------------------------------
> When I see the bootstrap log at the end it shows "Segmentation fault (core dumped)"
> 
> Thanks,
> Venkata.
> 
> 

Is your kas-container recent?

Do you happen to have qemu-user-static installed also on the host? If
so, please try to remove it then?

Note that CI also passes.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux

RE: [cip-dev] [isar-cip-core] cip arm64 build breaks

[Venkata.Pyla]

>-----Original Message-----
>From: Jan Kiszka <jan.kiszka@siemens.com>
>Sent: 10 May 2022 17:51
>To: pyla venkata(ＴＳＩＰ) <Venkata.Pyla@toshiba-tsip.com>; cip-
>dev@lists.cip-project.org
>Cc: dinesh kumar(ＴＳＩＰ) <dinesh.kumar@toshiba-tsip.com>; hayashi
>kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ) <kazuhiro3.hayashi@toshiba.co.jp>
>Subject: Re: [cip-dev] [isar-cip-core] cip arm64 build breaks
>
>On 10.05.22 14:06, Venkata.Pyla@toshiba-tsip.com wrote:
>> Hi Jan,
>>
>> Thanks for the work to support secureboot in arm64.
>>
>> I am building the arm64 image to check secureboot support in arm64, got the
>below error and do you have any idea about this error.
>>
>> ---------------------------------------
>> $ ./kas-container build
>> kas-cip.yml:kas/board/qemu-arm64.yml:kas/opt/5.10.yml:kas/opt/bullseye
>> .yml
>> :
>> .
>> I: Extracting liblzma5...
>> I: Extracting zlib1g...
>> W: Failure trying to run: chroot
>> "/build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/
>> rootfs" /sbin/ldconfig
>> W: See
>> /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/r
>> ootfs/debootstrap/debootstrap.log for details
>> WARNING: exit code 1 from a shell command.
>> ERROR: Logfile of failure stored in:
>> /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/t
>> emp/log.do_bootstrap.307
>> :
>> .
>> ---------------------------------------
>> When I see the bootstrap log at the end it shows "Segmentation fault (core
>dumped)"
>>
>> Thanks,
>> Venkata.
>>
>>
>
>Is your kas-container recent?
It is recent.

>
>Do you happen to have qemu-user-static installed also on the host? If so, please
>try to remove it then?
This was the culprit, I removed it from my host machine and the build is working.

Thanks a lot for the help. 

>
>Note that CI also passes.
>
>Jan
>
>--
>Siemens AG, Technology
>Competence Center Embedded Linux

Re: [cip-dev] [isar-cip-core] cip arm64 build breaks

[Jan Kiszka]

On 10.05.22 16:57, Venkata.Pyla@toshiba-tsip.com wrote:
> 
> 
>> -----Original Message-----
>> From: Jan Kiszka <jan.kiszka@siemens.com>
>> Sent: 10 May 2022 17:51
>> To: pyla venkata(ＴＳＩＰ) <Venkata.Pyla@toshiba-tsip.com>; cip-
>> dev@lists.cip-project.org
>> Cc: dinesh kumar(ＴＳＩＰ) <dinesh.kumar@toshiba-tsip.com>; hayashi
>> kazuhiro(林 和宏 □ＳＷＣ◯ＡＣＴ) <kazuhiro3.hayashi@toshiba.co.jp>
>> Subject: Re: [cip-dev] [isar-cip-core] cip arm64 build breaks
>>
>> On 10.05.22 14:06, Venkata.Pyla@toshiba-tsip.com wrote:
>>> Hi Jan,
>>>
>>> Thanks for the work to support secureboot in arm64.
>>>
>>> I am building the arm64 image to check secureboot support in arm64, got the
>> below error and do you have any idea about this error.
>>>
>>> ---------------------------------------
>>> $ ./kas-container build
>>> kas-cip.yml:kas/board/qemu-arm64.yml:kas/opt/5.10.yml:kas/opt/bullseye
>>> .yml
>>> :
>>> .
>>> I: Extracting liblzma5...
>>> I: Extracting zlib1g...
>>> W: Failure trying to run: chroot
>>> "/build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/
>>> rootfs" /sbin/ldconfig
>>> W: See
>>> /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/r
>>> ootfs/debootstrap/debootstrap.log for details
>>> WARNING: exit code 1 from a shell command.
>>> ERROR: Logfile of failure stored in:
>>> /build/tmp/work/cip-core-bullseye-arm64/isar-bootstrap-target/1.0-r0/t
>>> emp/log.do_bootstrap.307
>>> :
>>> .
>>> ---------------------------------------
>>> When I see the bootstrap log at the end it shows "Segmentation fault (core
>> dumped)"
>>>
>>> Thanks,
>>> Venkata.
>>>
>>>
>>
>> Is your kas-container recent?
> It is recent.
> 
>>
>> Do you happen to have qemu-user-static installed also on the host? If so, please
>> try to remove it then?
> This was the culprit, I removed it from my host machine and the build is working.
> 

Recurring topic, unfortunately. Still waiting for binfmt namespaces to
resolve this.

Jan

-- 
Siemens AG, Technology
Competence Center Embedded Linux