Re: next-clang/master boot: 80 boots: 8 failed, 72 passed (next-20190709)

On Tue, Jul 9, 2019 at 7:16 PM kernelci.org bot bot@kernelci.org wrote:

next-clang/master boot: 80 boots: 8 failed, 72 passed (next-20190709)

Full Boot Summary: https://staging.kernelci.org/boot/all/job/next-clang/branch/master/kernel/ne... Full Build Summary: https://staging.kernelci.org/build/next-clang/branch/master/kernel/next-2019...

Tree: next-clang Branch: master Git Describe: next-20190709 Git Commit: 4608a726c66807c27bc7d91bdf8a288254e29985 Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git Tested: 21 unique boards, 9 SoC families, 8 builds out of 119

Boot Regressions Detected:

arm:

multi_v7_defconfig:
    clang-8:
      sun8i-h2-plus-orangepi-r1:
          lab-baylibre-dev: new failure (last pass: next-20190625)
      sun8i-h2-plus-orangepi-zero:
          lab-baylibre-dev: new failure (last pass: next-20190705)

multi_v7_defconfig+CONFIG_SMP=n:
    clang-8:
      sun8i-h2-plus-orangepi-r1:
          lab-baylibre-dev: new failure (last pass: next-20190625)
      sun8i-h2-plus-orangepi-zero:
          lab-baylibre-dev: new failure (last pass: next-20190705)

sunxi_defconfig:
    clang-8:
      sun8i-h2-plus-orangepi-r1:
          lab-baylibre-dev: new failure (last pass: next-20190625)
      sun8i-h2-plus-orangepi-zero:
          lab-baylibre-dev: new failure (last pass: next-20190705)

Boot Failures Detected:

arm: multi_v7_defconfig+CONFIG_SMP=n: clang-8: bcm2836-rpi-2-b: 1 failed lab sun8i-h2-plus-orangepi-r1: 1 failed lab sun8i-h2-plus-orangepi-zero: 1 failed lab

multi_v7_defconfig:
    clang-8:
        bcm2836-rpi-2-b: 1 failed lab
        sun8i-h2-plus-orangepi-r1: 1 failed lab
        sun8i-h2-plus-orangepi-zero: 1 failed lab

sunxi_defconfig:
    clang-8:
        sun8i-h2-plus-orangepi-r1: 1 failed lab
        sun8i-h2-plus-orangepi-zero: 1 failed lab

---

For more info write to info@kernelci.org

Once, I get some more free time, I would like to start addressing these. From what I can tell from looking at a few, there's no output in the logs. I'd expect that for some kind of early crash. The question is, how does one go about debugging failed early boots? Looks like the zImages are available, but what would the debug cycle look like for gcc builds?