From: Kevin Hilman <khilman@kernel.org>
To: linux-samsung-soc@vger.kernel.org
Cc: linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org,
Olof Johansson <olof@lixom.net>, Arnd Bergmann <arnd@arndb.de>
Subject: exynos boot falures in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117))
Date: Mon, 17 Nov 2014 07:57:03 -0800 [thread overview]
Message-ID: <7hoas54y7k.fsf@deeprootsystems.com> (raw)
In-Reply-To: <E1XqKYI-0000pQ-4b@ip-10-35-177-41.ec2.internal> (Kevin's boot bot's message of "Mon, 17 Nov 2014 11:33:02 +0000")
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 <khilman@kernel.org> 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
next parent reply other threads:[~2014-11-17 15:57 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1XqKYI-0000pQ-4b@ip-10-35-177-41.ec2.internal>
2014-11-17 15:57 ` Kevin Hilman [this message]
2014-11-17 16:57 ` exynos boot falures in linux-next Krzysztof Kozłowski
2014-11-17 16:57 ` Krzysztof Kozłowski
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 22:24 ` Kevin Hilman
2014-11-17 23:25 ` Javier Martinez Canillas
2014-11-17 23:25 ` Javier Martinez Canillas
2014-11-18 2:30 ` Inki Dae
2014-11-18 2:30 ` Inki Dae
2014-11-18 3:49 ` Kevin Hilman
2014-11-18 3:49 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:01 ` Kevin Hilman
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-19 17:06 ` Javier Martinez Canillas
2014-11-20 1:55 ` Kukjin Kim
2014-11-20 1:55 ` Kukjin Kim
2014-12-02 8:32 ` Javier Martinez Canillas
2014-12-02 8:32 ` Javier Martinez Canillas
[not found] ` <7h61ed4xm3.fsf@deeprootsystems.com>
2014-11-17 18:21 ` mirabox boot fails in linux-next (was: next boot: 94 boots: 79 pass, 13 fail, 2 untried (next-20141117)) Thomas Petazzoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7hoas54y7k.fsf@deeprootsystems.com \
--to=khilman@kernel.org \
--cc=arnd@arndb.de \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=olof@lixom.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.