-----Original Message-----
From: Ben Hutchings <ben.hutchings@...>
Sent: Wednesday, April 3, 2019 10:53 PM
To: sangorrin daniel(サンゴリン ダニエル ○ＳＷＣ□ＯＳＴ)
<daniel.sangorrin@...>; jan.kiszka@...
Cc: isar-users@...; cip-dev@...
Subject: Re: [cip-dev] isar error log

On Wed, 2019-04-03 at 00:56 +0000, daniel.sangorrin@... 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 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.

Might this be restricted by an AppArmor profile? aa-logprof should show
you AppArmor denials and change the relevant profile(s) to allow the
operations.

Thanks for the advice Ben.
I checked with aa-logprof but there was nothing related.
# interestingly, for some reason AppArmor was restricting some functionality in Evince

Then, I tried to update the kernel to a new version (i was using about 4.4.0-84 and the latest was around 4.4.0-145) to see if something improved but I found that the new kernel wouldn't boot properly because my disk is encrypted. So I have possibly found a regression on the 4.4 kernel, I will have to check when I get back to my desk. And there is a possibility that the reason for my problem is in the binfmt kernel module.

Thanks,
Daniel

Ben.

--
Ben Hutchings, Software Developer   Codethink Ltd
https://www.codethink.co.uk/ Dale House, 35 Dale Street
Manchester, M1 2HF, United Kingdom