From: Mark Brown <broonie@kernel•org>
To: Will Deacon <will@kernel•org>
Cc: Bjorn Andersson <bjorn.andersson@linaro•org>,
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,
Catalin Marinas <catalin.marinas@arm•com>
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 20:23:46 +0000 [thread overview]
Message-ID: <20191028202346.GJ5015@sirena.co.uk> (raw)
In-Reply-To: <20191028201418.GA8317@willie-the-truck>
[-- Attachment #1: Type: text/plain, Size: 731 bytes --]
On Mon, Oct 28, 2019 at 08:14:18PM +0000, Will Deacon wrote:
> Hmm. Is this a recent thing? Neither kpti nor the snapdragon 820 are
It's in mainline, don't seem to have any results from Bjorn's lab for
stable.
> particular new. Might be worth checking that CONFIG_QCOM_FALKOR_ERRATUM_1003
> is enabled and getting patched in at runtime -- we had hardware issues
> during kpti development with this CPU.
It's enabled in defconfig:
https://storage.kernelci.org/next/master/next-20191028/arm64/defconfig/gcc-8/kernel.config
but I can't see any sign that it's been announced in the boot log:
https://storage.kernelci.org/next/master/next-20191028/arm64/defconfig/gcc-8/lab-bjorn/boot-apq8096-db820c.html
so that might be it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2019-10-28 20:23 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
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 [this message]
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=20191028202346.GJ5015@sirena.co.uk \
--to=broonie@kernel$(echo .)org \
--cc=agross@kernel$(echo .)org \
--cc=bjorn.andersson@linaro$(echo .)org \
--cc=catalin.marinas@arm$(echo .)com \
--cc=kernel-build-reports@lists$(echo .)linaro.org \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
--cc=linux-arm-msm@vger$(echo .)kernel.org \
--cc=linux-next@vger$(echo .)kernel.org \
--cc=will@kernel$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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