From: Stephen Boyd <sboyd@codeaurora.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
Mark Brown <broonie@kernel.org>, Kukjin Kim <kgene@kernel.org>,
Guenter Roeck <groeck@google.com>,
Ulf Hansson <ulf.hansson@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
linux-samsung-soc@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
"kernelci.org bot" <bot@kernelci.org>,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 270 boots: 35 failed, 213 passed with 20 offline, 2 untried/unknown (next-20171207)
Date: Fri, 8 Dec 2017 08:59:43 -0800 [thread overview]
Message-ID: <20171208165943.GC4283@codeaurora.org> (raw)
In-Reply-To: <7ad6d330-d277-85ae-b891-cb76367461ce@samsung.com>
On 12/08, Marek Szyprowski wrote:
> Hi Krzysztof,
>
> On 2017-12-08 13:33, Krzysztof Kozlowski wrote:
> >On Fri, Dec 8, 2017 at 1:27 PM, Mark Brown <broonie@kernel.org> wrote:
> >>On Fri, Dec 08, 2017 at 12:20:07PM +0000, Mark Brown wrote:
> >>>On Thu, Dec 07, 2017 at 03:54:47PM -0800, kernelci.org bot wrote:
> >>>
> >>>Today's -next failed to boot on peach-pi:
> >>>
> >>>> exynos_defconfig:
> >>>> exynos5800-peach-pi:
> >>>> lab-collabora: new failure (last pass: next-20171205)
> >>>with details at https://kernelci.org/boot/id/5a2a2e7859b5141bc2afa17c/
> >>>(including logs and comparisons with other boots, the last good boot was
> >>>Wednesday). It looks like it hangs somewhere late on in boot, the last
> >>>output on the console is:
> >>>
> >>>[ 4.827139] smsc95xx 3-1.1:1.0 eth0: register 'smsc95xx' at usb-xhci-hcd.3.auto-1.1, smsc95xx USB 2.0 Ethernet, 94:eb:2c:00:03:c0
> >>>[ 5.781037] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
> >>>[ 5.786247] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
> >>>[ 5.819200] dma-pl330 3880000.adma: PM domain MAU will not be powered off
> >>>[ 64.529228] random: crng init done
> >>>
> >>>and there's failures earlier to instantiate the display.
> >>I just noticed that further up the log there's a lockdep splat with a
> >>conflict between the genpd and clock API locking - an ABBA issue with
> >>genpd->mlock and the clock API prepare_lock.
> >+Cc Marek Szyprowski,
> >
> >The lockdep issue and display failures (including regulator warning)
> >were present for some time. They also appear in boot log for
> >next-20171206 (https://storage.kernelci.org/next/master/next-20171206/arm/exynos_defconfig/lab-collabora/boot-exynos5800-peach-pi.html).
> >The difference is that 20171208 hangs on "random: crng init done"
> >which did not appear before at all.
I haven't looked at the lockdep splat yet, but is that happening
because of runtime PM usage by the clk framework?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
WARNING: multiple messages have this Message-ID (diff)
From: sboyd@codeaurora.org (Stephen Boyd)
To: linux-arm-kernel@lists.infradead.org
Subject: next/master boot: 270 boots: 35 failed, 213 passed with 20 offline, 2 untried/unknown (next-20171207)
Date: Fri, 8 Dec 2017 08:59:43 -0800 [thread overview]
Message-ID: <20171208165943.GC4283@codeaurora.org> (raw)
In-Reply-To: <7ad6d330-d277-85ae-b891-cb76367461ce@samsung.com>
On 12/08, Marek Szyprowski wrote:
> Hi Krzysztof,
>
> On 2017-12-08 13:33, Krzysztof Kozlowski wrote:
> >On Fri, Dec 8, 2017 at 1:27 PM, Mark Brown <broonie@kernel.org> wrote:
> >>On Fri, Dec 08, 2017 at 12:20:07PM +0000, Mark Brown wrote:
> >>>On Thu, Dec 07, 2017 at 03:54:47PM -0800, kernelci.org bot wrote:
> >>>
> >>>Today's -next failed to boot on peach-pi:
> >>>
> >>>> exynos_defconfig:
> >>>> exynos5800-peach-pi:
> >>>> lab-collabora: new failure (last pass: next-20171205)
> >>>with details at https://kernelci.org/boot/id/5a2a2e7859b5141bc2afa17c/
> >>>(including logs and comparisons with other boots, the last good boot was
> >>>Wednesday). It looks like it hangs somewhere late on in boot, the last
> >>>output on the console is:
> >>>
> >>>[ 4.827139] smsc95xx 3-1.1:1.0 eth0: register 'smsc95xx' at usb-xhci-hcd.3.auto-1.1, smsc95xx USB 2.0 Ethernet, 94:eb:2c:00:03:c0
> >>>[ 5.781037] dma-pl330 3880000.adma: Loaded driver for PL330 DMAC-241330
> >>>[ 5.786247] dma-pl330 3880000.adma: DBUFF-4x8bytes Num_Chans-6 Num_Peri-16 Num_Events-6
> >>>[ 5.819200] dma-pl330 3880000.adma: PM domain MAU will not be powered off
> >>>[ 64.529228] random: crng init done
> >>>
> >>>and there's failures earlier to instantiate the display.
> >>I just noticed that further up the log there's a lockdep splat with a
> >>conflict between the genpd and clock API locking - an ABBA issue with
> >>genpd->mlock and the clock API prepare_lock.
> >+Cc Marek Szyprowski,
> >
> >The lockdep issue and display failures (including regulator warning)
> >were present for some time. They also appear in boot log for
> >next-20171206 (https://storage.kernelci.org/next/master/next-20171206/arm/exynos_defconfig/lab-collabora/boot-exynos5800-peach-pi.html).
> >The difference is that 20171208 hangs on "random: crng init done"
> >which did not appear before at all.
I haven't looked at the lockdep splat yet, but is that happening
because of runtime PM usage by the clk framework?
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2017-12-08 16:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5a29d4c7.4fabdf0a.716d7.8485@mx.google.com>
2017-12-08 12:20 ` next/master boot: 270 boots: 35 failed, 213 passed with 20 offline, 2 untried/unknown (next-20171207) Mark Brown
2017-12-08 12:20 ` Mark Brown
2017-12-08 12:27 ` Mark Brown
2017-12-08 12:27 ` Mark Brown
2017-12-08 12:33 ` Krzysztof Kozlowski
2017-12-08 12:33 ` Krzysztof Kozlowski
2017-12-08 13:27 ` Marek Szyprowski
2017-12-08 13:27 ` Marek Szyprowski
2017-12-08 16:59 ` Stephen Boyd [this message]
2017-12-08 16:59 ` Stephen Boyd
2017-12-11 9:28 ` Marek Szyprowski
2017-12-11 9:28 ` Marek Szyprowski
2017-12-11 10:43 ` Marek Szyprowski
2017-12-11 10:43 ` Marek Szyprowski
2017-12-11 22:35 ` Shuah Khan
2017-12-11 22:35 ` Shuah Khan
2017-12-19 20:05 ` Stephen Boyd
2017-12-19 20:05 ` Stephen Boyd
2017-12-20 11:28 ` Marek Szyprowski
2017-12-20 11:28 ` Marek Szyprowski
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=20171208165943.GC4283@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=bot@kernelci.org \
--cc=broonie@kernel.org \
--cc=groeck@google.com \
--cc=kernel-build-reports@lists.linaro.org \
--cc=kgene@kernel.org \
--cc=krzk@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=ulf.hansson@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.