On Thu, 21 Jun 2018 at 15:02, Zoran S zoran.stojsavljevic.de@gmail.com wrote:

Hello Folks,

Long time no see. Seems that I am back (for limited time) to Lava testing, and after all the setups and catches 22, I managed to get to the bottom of it, within few days.

I have interesting problem to report.

vagrant@stretch:/etc/lava-server/dispatcher-config/device-types$ dpkg -l lava-server lava-dispatcher Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name Version Architecture Description

+++-==========================================-==========================-==========================-========================================================================================== ii lava-dispatcher 2018.5-3~bpo9+1 amd64 Linaro Automated Validation Architecture dispatcher ii lava-server 2018.5-3~bpo9+1 all Linaro Automated Validation Architecture server

## Issue Background Issue CIP testing #16 seems to be very similar: Beaglebone Black health-check job is failing at restart ## Issue description Wrong Ramdisk Image Format Ramdisk image is corrupt or invalid ## Acceptance criteria The tftp 0x88080000 22/tftp-deploy-on2jld77/ramdisk/ramdisk.cpio.gz.uboot Using cpsw devtftp 0x88080000 22/tftp-deploy-on2jld77/ramdisk/ramdisk.cpio.gz.uboot

The initramdisk is built by the following instructions:

https://wiki.linuxfoundation.org/civilinfrastructureplatform/cipsystembuildh...

I used both BusyBox 28.0 and latest stable BusyBox 28.4 (failure seems to be the same)!

Should download seamlessly, but it does not. It reports that the image is corrupt. The full log is at: local test of ramdisk test on bbb - Lava job 22 https://pastebin.com/y9n4GM5G

The .yaml file is at: [lava 2018.5-3] job_name: local test of ramdisk test on bbb https://pastebin.com/kqS2dqWM _______

Namely, the download order is somehow scrambled!

​Check this thread on this list from last month:

https://lists.linaro.org/pipermail/lava-users/2018-May/001064.html

Specifically https://lists.linaro.org/pipermail/lava-users/2018-May/001068.html and the confirmation of the fix: https://lists.linaro.org/pipermail/lava-users/2018-May/001069.html ​ I can't be certain because although you attached the test job log file, you didn't attach the device configuration.

Other possibilities include something genuinely wrong with that ramdisk. You attached a test job submission where the standard ARMMP ramdisk is commented out. Does the test job work with all of the standard ARMMP BBB files in place in the test job?

Kernelci uses OE based ramdisks, so try one of theirs? Or try one of the ramdisks from completed test jobs on validation.linaro.org, https://validation.linaro.org/scheduler/job/1883601

Thank you, Zoran Stojsavljevic