linaro-release team mailing list archive

[James Westby <jw+debian@xxxxxxxxxxxxxxx>]

>  in d942e43 but not in 9c1f859 in linus

That set of patches doesn't look to have anything interesting (TPM/zorro/docs/S390)
which suggests that it wasn't caused by a change to linux in
that timeframe, so either:

  1) It's not a linux change at all
  2) It was something earlier where the non-determinism meant that it didn't show up as soon as it was introduced
  3) I'm wrong about the above

If it's 1) then it may point to a change on ci.linaro.org around that time, but it's
not clear why arm-soc for-next hasn't shown this problem for such a long run
of builds now.

We seem to have elminated LAVA entirely from the equation by reproducing
with just the hwpack and rootfs.

Now let's see if we can eliminate CI. Would someone who knows how to do such things
build linus tip with omap2plus_defconfig and test it on an OMAP?

If that works, does it make a difference if you cross-build from an x86
host?

Thanks,

James


** Changed in: lava-test
       Status: New => Invalid

** Changed in: lava-lab
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Linaro
Release Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/859473

Title:
  CI kernels causing many "Illegal Instruction"s

Status in LAVA Validation Lab:
  Invalid
Status in LAVA Automated Testing Framework:
  Invalid
Status in Linaro CI:
  Confirmed

Bug description:
  http://validation.linaro.org/lava-server/dashboard/streams/anonymous
  /ci-linux-arm-soc-for-
  next/bundles/df1d0476cd481e7b13fc8fbc7876149a00da4705/5fb90782-e7d9-11e0-9729-68b599be548c/attachments/10999/

  # root@linaro:~# [rc=0]: lava-test run smem -o /lava/results/smem-025113.bundle
  # lava-test run smem -o /lava/results/smem-025113.bundle
  #
  # Illegal instruction 
  and more causes all lava-test failed.

To manage notifications about this bug go to:
https://bugs.launchpad.net/lava-lab/+bug/859473/+subscriptions