Hi, Mans has found what was causing gdb to crash:
<mru> it's crashing in get_linux_version() <mru> in gdb/arm-linux-nat.c <mru> on the 3rd strtoul call <mru> probably totally hating the fact version is reported as 3.1 so it's unrelated to the SIGILL issues. So that means that getting a core from a SIGILL would still be interesting. If someone can combine the hwpack and rootfs I referenced before, boot it ulimit -c 1024 hwclock then it should dump a core that may give us some more info. Getting a fixed gdb on to the system would also be possible so that the commands could be run directly, rather than working on the core. Thanks, James -- 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 _______________________________________________ Mailing list: https://launchpad.net/~linaro-release Post to : [email protected] Unsubscribe : https://launchpad.net/~linaro-release More help : https://help.launchpad.net/ListHelp
