linaro-release team mailing list archive

[Michael Hudson-Doyle <michael.hudson+lp@xxxxxxxxxx>]

I've tried to reproduce this, but l-m-c is failing for me:

$ sudo linaro-media-create --rootfs ext2 --mmc /dev/sde --dev panda --hwpack ~/Downloads/hwpack_linaro-omap3_20111007-0028_armel_supported.tar.gz --binary ~/Downloads/nano-n-tar-20111005-1.tar.gz --hwpack-force-yes
...


Writing inode tables: done                            
Writing superblocks and filesystem accounting information: done

This filesystem will be automatically checked every 25 mounts or
180 days, whichever comes first.  Use tune2fs -c or -i to override.
cp: cannot stat `/tmp/tmpKxd3zn/binary/usr/lib/u-boot/omap4_panda/u-boot.bin': No such file or directory
Traceback (most recent call last):
  File "/usr/bin/linaro-media-create", line 171, in <module>
    args.is_live, args.is_lowmem, args.consoles)
  File "/usr/lib/pymodules/python2.7/linaro_image_tools/media_create/boards.py", line 743, in populate_boot
    proc.wait()
  File "/usr/lib/pymodules/python2.7/linaro_image_tools/cmd_runner.py", line 100, in wait
    raise SubcommandNonZeroReturnValue(self._my_args, returncode)
linaro_image_tools.cmd_runner.SubcommandNonZeroReturnValue: Sub process "['cp', '-v', '/tmp/tmpKxd3zn/binary/usr/lib/u-boot/omap4_panda/u-boot.bin', '/tmp/tmpKxd3zn/boot-disc']" returned a non-zero value: 1

This is exactly like bug 842421, but that was reported to be a hwpack
that was too new for the l-m-c, and I get this with lp:linaro-image-
tools tip (as well as the version from the ppa, and a few other versions
I tried).  Boo! :(

-- 
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:
  Recently there have been lots of validation failures for kernels from
  CI.

  These failures manifest as "Illegal Instruction" errors all over the logs
  (not just during tests, but booting as well.)

  It seems that the kernel is causing a lot of SIGILLs, but we don't know
  why yet.

  To reproduce
  ------------

  Combining

  http://ci.linaro.org/kernel_hwpack/omap3/hwpack_linaro-omap3_20111007-0028_armel_supported.tar.gz
  http://snapshots.linaro.org/11.05-daily/linaro-nano/20111005/1/images/tar/nano-n-tar-20111005-1.tar.gz

  with linaro-media-create (--rootfs ext2) should give you an image that
  shows the problem.

  Information wanted
  ------------------

  There are currently two things that we would like more information on to try
  and narrow down the cause of the problem.

  1) A core file from a crashing application

  To get this

    Create the image as described above
    Boot in to it
    Run "ulimit -c 1024"
    Run "hwclock"
    Watch it crash with "Illegal Instruction (core dumped)"
    Get that core from the filesystem.

  2) Test a defconfig build

  If this succeeds then it suggests a problem with the way that the kernel is
  being built on ci.linaro.org.

  To do this

    Get the tip of linus' tree
    Build with omap2plus_defconfig
    Boot the resulting kernel

  If that shows no SIGILL problems, then try a cross-build from an x86
  host.

  If neither of those show problems then we can concentrate on
  ci.linaro.org.

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