From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: Andy Gross <agross@kernel.org>,
kernel-build-reports@lists.linaro.org,
linux-next@vger.kernel.org, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master boot: 257 boots: 8 failed, 237 passed with 8 offline, 2 untried/unknown, 2 conflicts (next-20191028)
Date: Mon, 28 Oct 2019 11:40:19 -0700 [thread overview]
Message-ID: <20191028184019.GR571@minitux> (raw)
In-Reply-To: <20191028174857.GG5015@sirena.co.uk>
On Mon 28 Oct 10:48 PDT 2019, Mark Brown wrote:
Hi Mark
> On Mon, Oct 28, 2019 at 08:03:08AM -0700, kernelci.org bot wrote:
>
> Today's -next (anf Friday's) fails to boot on db820c:
>
> > defconfig:
> > gcc-8:
> > apq8096-db820c: 1 failed lab
>
> It looks like it deadlocks somewhere, the last things in the log are a
> failure to start ufshcd-qcom and then an RCU stall some time later:
>
db820c has been failing intermittently for a while now, it seems that
booting with kpti enabled causes something to go wrong. There are
nothing strange in the kernel logs and ftrace seems to indicate that all
the CPUs are idling nicely.
Regards,
Bjorn
> 03:03:27.191914 [ 21.156672] ufshcd-qcom 624000.ufshc: ufshcd_populate_vreg: Unable to find vdd-hba-supply regulator, assuming enabled
> 03:03:27.198061 <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=qup-i2c-driver-present RESULT=pass>
> 03:03:27.208499 [ 21.175985] ufshcd-qcom 624000.ufshc: ufs_qcom_init: required phy device. hasn't probed yet. err = -517
> 03:03:27.216720 [ 21.176014] ufshcd-qcom 624000.ufshc: ufshcd_variant_hba_init: variant qcom init failed err -517
> 03:03:27.226220 <LAVA_SIGNAL_TESTCASE TEST_CASE_ID=qup-i2c-blsp-i2c2-probed RESULT=pass>
> 03:03:27.239850 [ 21.211424] ufshcd-qcom 624000.ufshc: Initialization failed
> 03:03:48.157338 [ 42.128777] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
> 03:03:48.167648 [ 42.128802] rcu: 3-...!: (0 ticks this GP) idle=dde/1/0x4000000000000000 softirq=1715/1715 fqs=60
> 03:03:48.171895 [ 42.133839] (detected by 0, t=5252 jiffies, g=2301, q=787)
>
> Full details, including the whole log, at:
>
> https://kernelci.org/boot/id/5db6bf0d59b514a35660ee72/
next prev parent reply other threads:[~2019-10-28 18:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5db7032c.1c69fb81.888b0.b521@mx.google.com>
2019-10-28 17:48 ` next/master boot: 257 boots: 8 failed, 237 passed with 8 offline, 2 untried/unknown, 2 conflicts (next-20191028) Mark Brown
2019-10-28 18:40 ` Bjorn Andersson [this message]
2019-10-28 19:11 ` Mark Brown
2019-10-28 20:02 ` Bjorn Andersson
2019-10-28 20:14 ` Will Deacon
2019-10-28 20:23 ` Mark Brown
2019-10-28 15:03 kernelci.org bot
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=20191028184019.GR571@minitux \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=broonie@kernel.org \
--cc=kernel-build-reports@lists.linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).