From: Kevin Hilman <khilman@baylibre.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "kernelci.org bot" <bot@kernelci.org>,
kernel-build-reports@lists.linaro.org,
Kukjin Kim <kgene@kernel.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
linux-samsung-soc@vger.kernel.org
Subject: Re: mainline boot: 179 boots: 1 failed, 168 passed with 10 offline (v4.9-rc8-78-g318c8932ddec)
Date: Fri, 09 Dec 2016 15:03:16 -0800 [thread overview]
Message-ID: <m2h96caeob.fsf@baylibre.com> (raw)
In-Reply-To: <20161209125802.GA4229@kozik-lap> (Krzysztof Kozlowski's message of "Fri, 9 Dec 2016 14:58:02 +0200")
Krzysztof Kozlowski <krzk@kernel.org> writes:
> On Thu, Dec 08, 2016 at 04:17:27PM -0800, Kevin Hilman wrote:
>> + Exynos maintainers (for new regresion on exynos5250-snow)
>>
>> kernelci.org bot <bot@kernelci.org> writes:
>>
>> > mainline boot: 179 boots: 1 failed, 168 passed with 10 offline (v4.9-rc8-78-g318c8932ddec)
>> >
>> > Full Boot Summary: https://kernelci.org/boot/all/job/mainline/kernel/v4.9-rc8-78-g318c8932ddec/
>> > Full Build Summary: https://kernelci.org/build/mainline/kernel/v4.9-rc8-78-g318c8932ddec/
>> >
>> > Tree: mainline
>> > Branch: local/master
>> > Git Describe: v4.9-rc8-78-g318c8932ddec
>> > Git Commit: 318c8932ddec5c1c26a4af0f3c053784841c598e
>> > Git URL: http://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
>> > Tested: 57 unique boards, 21 SoC families, 29 builds out of 207
>> >
>> > Boot Regressions Detected:
>> >
>> > arm:
>> >
>> > multi_v7_defconfig+CONFIG_SMP=n:
>> > exynos5250-snow:
>> > lab-collabora: new failure (last pass: v4.9-rc8-51-gbc3913a5378c)
>> >
>> > Boot Failure Detected:
>> >
>> > arm:
>> >
>> > multi_v7_defconfig+CONFIG_SMP=n
>> > exynos5250-snow: 1 failed lab
>
> Nothing was happening recently around Exynos code (at least mach/dts).
> Was the 318c8932ddec5c1c26a4af0f3c053784841c598e pointed out by bisect?
The bisect[1] pointed to this, but that doesn't smell right, and I
wasn't able to dig into it any further:
2513940989fa2c56d0aeb4f5792d22804d92ab4c is the first bad commit
commit 2513940989fa2c56d0aeb4f5792d22804d92ab4c
Author: Michael Ellerman <mpe@ellerman.id.au>
Date: Fri Nov 25 09:45:28 2016 +1100
Full bisect log is here[1].
Kevin
[1] https://ci.linaro.org/view/people/job/tbaker-boot-bisect-bot/171/console
prev parent reply other threads:[~2016-12-09 23:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5849e989.0209c20a.75a7.6441@mx.google.com>
[not found] ` <m2shpyarc8.fsf@baylibre.com>
2016-12-09 12:58 ` mainline boot: 179 boots: 1 failed, 168 passed with 10 offline (v4.9-rc8-78-g318c8932ddec) Krzysztof Kozlowski
2016-12-09 23:03 ` Kevin Hilman [this message]
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=m2h96caeob.fsf@baylibre.com \
--to=khilman@baylibre.com \
--cc=bot@kernelci.org \
--cc=javier@osg.samsung.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-samsung-soc@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 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.