From: Marc Zyngier <maz@kernel.org>
To: Tim Harvey <tharvey@gateworks.com>
Cc: open list <linux-kernel@vger.kernel.org>,
David Daney <david.daney@cavium.com>,
Sunil Goutham <sgoutham@cavium.com>,
Jan Glauber <jglauber@cavium.com>,
Robert Richter <rrichter@marvell.com>
Subject: Re: CN80xx (octeontx/thunderx) breakage from f2d8340
Date: Thu, 12 Mar 2020 08:55:52 +0000 [thread overview]
Message-ID: <0c3c16c770d21e5ad2276c83feb27ce4@kernel.org> (raw)
In-Reply-To: <CAJ+vNU0qVnCkWpG_NKNQTdYf5LJpRrgOeWX0xH=GgavKJ1QNwg@mail.gmail.com>
Hi Tim,
On 2020-03-11 20:17, Tim Harvey wrote:
> Marc,
>
> Im seeing a failure to boot on an octeontx CN80xx (thunderx) due to
> f2d8340 ("irqchip/gic-v3: Add GICv4.1 VPEID size discovery"). I'm not
> sure if something is hanging, I just get no console output from the
> kernel.
That's odd. It probably means that a SError has been taken to EL3,
and the firmware is not equipped to deal with it. Great stuff!
> Is there perhaps something in the dt that requires change? The
> board/dts I'm using is:
> https://github.com/Gateworks/dts-newport/blob/sdk-10.1.1.0-newport/gw6404-linux.dts
> https://github.com/Gateworks/dts-newport/blob/sdk-10.1.1.0-newport/gw640x-linux.dtsi
> https://github.com/Gateworks/dts-newport/blob/sdk-10.1.1.0-newport/cn81xx-linux.dtsi
>
> Any ideas? I've cc'd the Cavium/Marvell folk to see if they know
> what's up or can reproduce on some of their hardware.
This is most probably Cavium erratum 38539. Please give [1] a go and
let me know whether it helps by replying to the patch.
Thanks,
M.
[1] https://lore.kernel.org/lkml/20200311115649.26060-1-maz@kernel.org/
--
Jazz is not dead. It just smells funny...
next prev parent reply other threads:[~2020-03-12 8:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-11 20:17 CN80xx (octeontx/thunderx) breakage from f2d8340 Tim Harvey
2020-03-12 8:55 ` Marc Zyngier [this message]
2020-03-12 9:43 ` Robert Richter
2020-03-12 9:58 ` Robert Richter
2020-03-12 16:58 ` Tim Harvey
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=0c3c16c770d21e5ad2276c83feb27ce4@kernel.org \
--to=maz@kernel.org \
--cc=david.daney@cavium.com \
--cc=jglauber@cavium.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rrichter@marvell.com \
--cc=sgoutham@cavium.com \
--cc=tharvey@gateworks.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