On Mon, May 09, 2016 at 12:49:49AM -0700, kernelci.org bot wrote: > stable-queue boot: 73 boots: 1 failed, 69 passed with 3 offline (v4.4.9-67-gc8dd5c83d962) > > Full Boot Summary: https://kernelci.org/boot/all/job/stable-queue/kernel/v4.4.9-67-gc8dd5c83d962/ > Full Build Summary: https://kernelci.org/build/stable-queue/kernel/v4.4.9-67-gc8dd5c83d962/ > > Tree: stable-queue > Branch: local/linux-4.4.y.queue > Git Describe: v4.4.9-67-gc8dd5c83d962 > Git Commit: c8dd5c83d96233934e9559124ba8f6f4fb598ec2 > Git URL: git://server.roeck-us.net/git/linux-stable.git > Tested: 16 unique boards, 6 SoC families, 17 builds out of 107 > > Boot Failure Detected: https://kernelci.org/boot/?v4.4.9-67-gc8dd5c83d962&fail > > arm: > > socfpga_defconfig: > socfpga_cyclone5_socrates: 1 failed lab Same question here: https://storage.kernelci.org/stable-queue/v4.4.9-67-gc8dd5c83d962/arm-socfpga_defconfig/lab-pengutronix/boot-socfpga_cyclone5_socrates.html It looks like the kernel booted just fine, but no root filesystem was found. Is that the fault of this set of patches, or did something "external" happen? still confused, greg k-h -- To unsubscribe from this list: send the line "unsubscribe stable" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html