On 10/02/2013 07:45 PM, Antonio Terceiro wrote:
On Mon, Sep 30, 2013 at 06:54:47PM +0300, Fathi Boudra wrote:
CC'ing LAVA guys
On 26 September 2013 15:46, Maxim Uvarov maxim.uvarov@linaro.org wrote:
As I understand this log right: https://validation.linaro.org/scheduler/job/74753/log_file
Arndale booted with standard LE rootfs. Then there is wget rootfs and chroot to it. And of course any commands under chroot will fail.
So I think for now it's impossible to run BE in lava boards unless we will set up any board with BE env or remove chroot from set up scripts.
Is chroot really needed for this? : chroot /mnt/root ln -sf /bin/true /usr/sbin/flash-kernel
This is an internal implementation detail of LAVA that in a ideal world shouldn't even show up in the logs. The job did not get to the point of actually running your code, because the _image deployment_ failed (hence "CriticalError: Deployment failed")
So LAVA needs to run some commands inside the image with chroot before it deploys the image to the device, but if you look at https://validation.linaro.org/scheduler/job/74753/log_file#L_11_26 you will see:
chroot: failed to run command `which': Exec format error
this means that the kernel on the host cannot execute the ARM binaries inside the image. I suspected that this would be because the server is lacking either qemu-user-static or binfmt-support, but both are installed so I'm not sure what went wrong there.
Matt/Dave, can you guys please investigate?
This happens because original system is little endian. And Lava does chroot to big endian root fs. And it's expected that you can not run be binaries on le system. So the only way to do is to avoid chroot.
Thank you, Maxim.