From: Russell King - ARM Linux admin <linux@armlinux.org.uk>
To: Guillaume Tucker <guillaume.tucker@collabora.com>
Cc: kernelci-results@groups.io,
Linus Walleij <linus.walleij@linaro.org>,
Nick Desaulniers <ndesaulniers@google.com>,
Ard Biesheuvel <ardb@kernel.org>,
Kees Cook <keescook@chromium.org>,
Abbott Liu <liuwenliang@huawei.com>,
linux-kernel@vger.kernel.org,
"kernelci@groups.io" <kernelci@groups.io>,
Ingo Molnar <mingo@kernel.org>,
linux-arm-kernel@lists.infradead.org
Subject: Re: next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3
Date: Fri, 18 Dec 2020 14:00:18 +0000 [thread overview]
Message-ID: <20201218140018.GZ1551@shell.armlinux.org.uk> (raw)
In-Reply-To: <3e1680ed-94b8-74c9-ffe6-c2bd71f2a705@collabora.com>
On Fri, Dec 18, 2020 at 01:48:09PM +0000, Guillaume Tucker wrote:
> Please see the bisection report below about a boot failure on
> ox820-cloudengines-pogoplug-series-3. There was also a bisection
> yesterday with next-20201216 which landed on the same commit, on
> the same platform and also with oxnas_v6_defconfig. I'm not
> aware of any other platform on kernelci.org showing the same
> regression.
Ah, I bet I know what's happening.
We test for the presence of VFP by issuing an instruction to read
FPSID. If VFP is not present, this will raise an undefined instruction
exception, and we expect to head into the vfp_testing_entry code.
I bet Pogoplug, being an ARM11 MPCore platform, either raises an
exception here.
We probably need to also rework the code in vfp_init() as well to
register a temporary hook when reading the FPSID.
--
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!
next prev parent reply other threads:[~2020-12-18 14:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5fdc89c3.1c69fb81.c9707.68bb@mx.google.com>
2020-12-18 13:48 ` next/master bisection: baseline.login on ox820-cloudengines-pogoplug-series-3 Guillaume Tucker
2020-12-18 14:00 ` Russell King - ARM Linux admin [this message]
2020-12-18 14:01 ` Ard Biesheuvel
2020-12-18 19:12 ` Ard Biesheuvel
2020-12-18 19:12 ` Ard Biesheuvel
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=20201218140018.GZ1551@shell.armlinux.org.uk \
--to=linux@armlinux.org.uk \
--cc=ardb@kernel.org \
--cc=guillaume.tucker@collabora.com \
--cc=keescook@chromium.org \
--cc=kernelci-results@groups.io \
--cc=kernelci@groups.io \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuwenliang@huawei.com \
--cc=mingo@kernel.org \
--cc=ndesaulniers@google.com \
/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