From: Arnd Bergmann <arnd@arndb.de>
To: linux-sh@vger.kernel.org
Subject: Re: stable boot: 93 boots: 92 pass, 1 fail (v3.17.6)
Date: Mon, 08 Dec 2014 11:35:41 +0000 [thread overview]
Message-ID: <2553650.3KSUKtTdo3@wuerfel> (raw)
On Sunday 07 December 2014 21:49:05 Kevin's boot bot wrote:
> Full Build report: http://status.armcloud.us/build/stable/kernel/v3.17.6/
> Full Boot report: http://status.armcloud.us/boot/all/job/stable/kernel/v3.17.6/
>
> Tree/Branch: stable
> Git describe: v3.17.6
>
> Failed boot tests
> ========> emev2-kzm9d: FAIL: arm-shmobile_defconfig
> http://storage.armcloud.us/kernel-ci/stable/v3.17.6/arm-shmobile_defconfig/boot-emev2-kzm9d.html
>
I tried to look at the reports, but the links don't work. Going
back in the archive, I see that it was still working until v3.17.2,
broken in v3.17.4/.5/.6 and the boot report for v3.17.3 seemed to run
into an unrelated issue. Mainline was always fine since 3.17, only
the stable kernels had problems:
http://storage.armcloud.us/kernel-ci/stable/v3.17.2/arm-shmobile_defconfig/boot-emev2-kzm9d.html
http://storage.armcloud.us/kernel-ci/stable/v3.17.3/arm-shmobile_defconfig/boot-emev2-kzm9d.html
http://storage.armcloud.us/kernel-ci/stable/v3.17.4/arm-shmobile_defconfig/boot-emev2-kzm9d.html
It may be worth having the sh team investigate the problem some more,
to see if a bad patch made it into stable kernels.
Arnd
next reply other threads:[~2014-12-08 11:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-08 11:35 Arnd Bergmann [this message]
2014-12-08 13:48 ` stable boot: 93 boots: 92 pass, 1 fail (v3.17.6) Geert Uytterhoeven
2014-12-08 15:39 ` Arnd Bergmann
2014-12-08 16:23 ` Tyler Baker
2014-12-08 16:45 ` Kevin Hilman
2014-12-08 17:03 ` Geert Uytterhoeven
2014-12-08 17:17 ` Kevin Hilman
2014-12-08 17:35 ` Kevin Hilman
2014-12-09 0:27 ` Simon Horman
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=2553650.3KSUKtTdo3@wuerfel \
--to=arnd@arndb.de \
--cc=linux-sh@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox