linux-kernel - Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma: support little endian for edma driver"

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] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 2 Jul 2019 15:10:56 +0200
From:   Krzysztof Kozlowski <krzk@...nel.org>
To:     Fabio Estevam <festevam@...il.com>
Cc:     Peng Ma <peng.ma@....com>, Vinod Koul <vkoul@...nel.org>,
        dmaengine@...r.kernel.org,
        linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma:
 support little endian for edma driver"

On Tue, 2 Jul 2019 at 15:04, Fabio Estevam <festevam@...il.com> wrote:
>
> Hi Krzysztof,
>
> On Tue, Jul 2, 2019 at 9:13 AM Krzysztof Kozłowski
> <k.kozlowski.k@...il.com> wrote:
> >
> > Hi,
> >
> > Bisect pointed commit:
> > commit 002905eca5bedab08bafd9e325bbbb41670c7712
> > Author: Peng Ma <peng.ma@....com>
> > Date:   Thu Jun 13 10:27:08 2019 +0000
> >     dmaengine: fsl-edma: support little endian for edma driver
> >
> > as a reason of NFSv4 root boot failures. Toradex Colibri VF50 (Cortex
> > A5) on Toradex Iris board.
> >
> > The user-space starts but hangs - a lot of messages are missing or
> > seriously delayed.
> >
> > Please revert the patch of fix it. If needed I can provide more
> > details about test system - let me know.
> >
> > Full log attached.
>
> Does this fix the problem?
>
> --- a/arch/arm/boot/dts/vfxxx.dtsi
> +++ b/arch/arm/boot/dts/vfxxx.dtsi
> @@ -92,6 +92,7 @@
>                                 clock-names = "dmamux0", "dmamux1";
>                                 clocks = <&clks VF610_CLK_DMAMUX0>,
>                                         <&clks VF610_CLK_DMAMUX1>;
> +                               big-endian;
>                                 status = "disabled";
>                         };
>
> @@ -491,6 +492,7 @@
>                                 clock-names = "dmamux0", "dmamux1";
>                                 clocks = <&clks VF610_CLK_DMAMUX2>,
>                                         <&clks VF610_CLK_DMAMUX3>;
> +                               big-endian;
>                                 status = "disabled";
>                         };
>
> I am not saying this is the proper fix as we should not break old dtb's.

Hi,

No, unfortunately it does not help.

Best regards,
Krzysztof