From: Sasha Levin <sasha.levin@oracle.com>
To: Kevin Hilman <khilman@kernel.org>
Cc: stable@vger.kernel.org, Tyler Baker <tyler.baker@linaro.org>
Subject: Re: stable-sasha boot: 342 boots: 6 failed, 336 passed (v3.18.19-51-gdf0e5109cfea)
Date: Fri, 07 Aug 2015 12:40:32 -0400 [thread overview]
Message-ID: <55C4DF80.9000606@oracle.com> (raw)
In-Reply-To: <CAMAWPa_AyUHEhqZ8+g8csEZXp1CH=kRJ6rDqTdL8+H4u=OYvBQ@mail.gmail.com>
On 08/07/2015 12:39 PM, Kevin Hilman wrote:
> On Fri, Aug 7, 2015 at 9:34 AM, kernelci.org bot <bot@kernelci.org> wrote:
>> > stable-sasha boot: 342 boots: 6 failed, 336 passed (v3.18.19-51-gdf0e5109cfea)
>> >
>> > Full Boot Summary: http://kernelci.org/boot/all/job/stable-sasha/kernel/v3.18.19-51-gdf0e5109cfea/
>> > Full Build Summary: http://kernelci.org/build/stable-sasha/kernel/v3.18.19-51-gdf0e5109cfea/
>> >
>> > Tree: stable-sasha
>> > Branch: local/linux-3.18.y-queue
>> > Git Describe: v3.18.19-51-gdf0e5109cfea
>> > Git Commit: df0e5109cfea25f842bf99f567aac20ac9ef78fe
>> > Git URL: git://git.kernel.org/pub/scm/linux/kernel/git/sashal/linux-stable.git
>> > Tested: 77 unique boards, 18 SoC families, 27 builds out of 143
>> >
>> > Boot Failures Detected: http://kernelci.org/boot/?v3.18.19-51-gdf0e5109cfea&fail
>> >
>> > arm:
>> >
>> > exynos_defconfig:
>> > exynos5420-arndale-octa_rootfs:nfs: 1 failed lab
>> > exynos5800-peach-pi_rootfs:nfs: 1 failed lab
>> >
>> > multi_v7_defconfig:
>> > hisi-x5hd2-dkb_rootfs:nfs: 1 failed lab
>> >
>> > multi_v7_defconfig+CONFIG_THUMB2_KERNEL=y:
>> > qcom-apq8074-dragonboard: 1 failed lab
>> > qcom-msm8974-sony-xperia-honami: 1 failed lab
>> >
>> > hisi_defconfig:
>> > hisi-x5hd2-dkb_rootfs:nfs: 1 failed lab
> These NFS boot failures are expected fails because NFS isn't enabled
> by default in v3.14, we need to blacklist these.
>
> The qcom Thumb2 errors are new and rather peculiar and seem to be
> alignment related as they can be made to boot by simply adding a
> 4-char localversion string! I'm still looking into that, but it's not
> directly related to the stable queue.
Interesting! Do you actually boot in on metal, or is it qemu?
Thanks,
Sasha
next prev parent reply other threads:[~2015-08-07 16:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <55c4de06.8f0cb40a.482e8.ffffd1dd@mx.google.com>
2015-08-07 16:39 ` stable-sasha boot: 342 boots: 6 failed, 336 passed (v3.18.19-51-gdf0e5109cfea) Kevin Hilman
2015-08-07 16:40 ` Sasha Levin [this message]
2015-08-07 16:54 ` Kevin Hilman
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=55C4DF80.9000606@oracle.com \
--to=sasha.levin@oracle.com \
--cc=khilman@kernel.org \
--cc=stable@vger.kernel.org \
--cc=tyler.baker@linaro.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 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.