From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Mark Brown <broonie@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, Andy Gross <agross@kernel.org>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
kernel-build-reports@lists.linaro.org
Subject: Re: next/master boot: 254 boots: 16 failed, 231 passed with 4 offline, 1 untried/unknown, 2 conflicts (next-20190726)
Date: Sun, 18 Aug 2019 21:35:08 -0700 [thread overview]
Message-ID: <20190819043508.GY26807@tuxbook-pro> (raw)
In-Reply-To: <20190726134843.GC55803@sirena.org.uk>
On Fri 26 Jul 06:48 PDT 2019, Mark Brown wrote:
> On Fri, Jul 26, 2019 at 05:18:01AM -0700, kernelci.org bot wrote:
>
> The past few versions of -next failed to boot on apq8096-db820c:
>
> > defconfig:
> > gcc-8:
> > apq8096-db820c: 1 failed lab
>
> with an RCU stall towards the end of boot:
>
> 00:03:40.521336 [ 18.487538] qcom_q6v5_pas adsp-pil: adsp-pil supply px not found, using dummy regulator
> 00:04:01.523104 [ 39.499613] rcu: INFO: rcu_preempt detected stalls on CPUs/tasks:
> 00:04:01.533371 [ 39.499657] rcu: 2-...!: (0 ticks this GP) idle=9ca/1/0x4000000000000000 softirq=1450/1450 fqs=50
> 00:04:01.537544 [ 39.504689] (detected by 0, t=5252 jiffies, g=2425, q=619)
> 00:04:01.541727 [ 39.513539] Task dump for CPU 2:
> 00:04:01.547929 [ 39.519096] seq R running task 0 199 198 0x00000000
>
> Full details and logs at:
>
> https://kernelci.org/boot/id/5d3aa7ea59b5142ba868890f/
>
> The last version that worked was from the 15th and there seem to be
> similar issues in mainline since -rc1.
As you might have seen this problem has come and gone on the
apq8096-db820c and I've finally managed to narrow it down a little bit.
The problem first appears on next-20190701, with the introduction of
CONFIG_RANDOMIZE_BASE in the defconfig, but after further efforts I've
concluded that disabling kpti removes or hides the problem.
With kpti=no on the command line I've now successfully booted the db820c
100+ times without problems (a clear improvement from the 75% failure
rate with kpti=yes).
Unfortunately I'm not yet certain why this is causing issues and I'm
also seeing the same rcu stall on SDA845 under certain (erroneous?)
conditions (where I don't expect them).
Regards,
Bjorn
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2019-08-19 4:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5d3aef79.1c69fb81.111b9.a701@mx.google.com>
2019-07-26 13:48 ` next/master boot: 254 boots: 16 failed, 231 passed with 4 offline, 1 untried/unknown, 2 conflicts (next-20190726) Mark Brown
2019-07-29 0:56 ` Bjorn Andersson
2019-08-19 4:35 ` Bjorn Andersson [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=20190819043508.GY26807@tuxbook-pro \
--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-kernel@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).