FYI... Various new exynos5 boot failures starting next-20141117. Looking in the boot logs, the boot stops during DRM initialization.
Note that the boot failures are only on exynos_defconfig, and not multi_v7_defconfig. Excerpt from boot report below, or recent exynos boots can also be explored here: http://status.armcloud.us/boot/?exynos Kevin Kevin's boot bot <[email protected]> writes: > Full Build report: http://status.armcloud.us/build/next/kernel/next-20141117/ > Full Boot report: > http://status.armcloud.us/boot/all/job/next/kernel/next-20141117/ > > Tree/Branch: next > Git describe: next-20141117 > > Failed boot tests > ================= [...] > exynos5422-odroid-xu3: FAIL: arm-exynos_defconfig > > http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-exynos_defconfig/boot-exynos5422-odroid-xu3.html > exynos5250-arndale: FAIL: arm-exynos_defconfig > > http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-exynos_defconfig/boot-exynos5250-arndale.html > exynos5800-peach-pi: FAIL: arm-exynos_defconfig > > http://storage.armcloud.us/kernel-ci/next/next-20141117/arm-exynos_defconfig/boot-exynos5800-peach-pi.html -- To unsubscribe from this list: send the line "unsubscribe linux-samsung-soc" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
