linux-kernel - Re: CN80xx (octeontx/thunderx) breakage from f2d8340

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAJ+vNU0VEgO1gWK11Wi0RPwU95EsqkKZSH=EMVhZoQUxikLOJg@mail.gmail.com>
Date:   Thu, 12 Mar 2020 09:58:57 -0700
From:   Tim Harvey <tharvey@...eworks.com>
To:     Marc Zyngier <maz@...nel.org>
Cc:     open list <linux-kernel@...r.kernel.org>,
        David Daney <david.daney@...ium.com>,
        Sunil Goutham <sgoutham@...ium.com>,
        Jan Glauber <jglauber@...ium.com>,
        Robert Richter <rrichter@...vell.com>,
        Sunil Goutham <sgoutham@...vell.com>
Subject: Re: CN80xx (octeontx/thunderx) breakage from f2d8340

On Thu, Mar 12, 2020 at 1:55 AM Marc Zyngier <maz@...nel.org> wrote:
>
> 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.
>
>
> [1] https://lore.kernel.org/lkml/20200311115649.26060-1-maz@kernel.org/

Marc,

Yup, this was it! We need to make sure this gets merged into 5.6. I
didn't have the original patch but attempted to reply via mailto:
link.

Best regards,

Tim