Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
MIME-Version: 1.0
References: <CAJKOXPfx6HeJgTu9TiusGACyt+uXVSmnpibO0m-qzCvFQNGK7g@mail.gmail.com>
 <CAOMZO5A-XTtMD0g0ESHA=7bM4=HQjgTpzQq2BSYnPyd_1eG=qw@mail.gmail.com>
In-Reply-To: <CAOMZO5A-XTtMD0g0ESHA=7bM4=HQjgTpzQq2BSYnPyd_1eG=qw@mail.gmail.com>
From:   Krzysztof Kozlowski <krzk@kernel.org>
Date:   Tue, 2 Jul 2019 15:10:56 +0200
Message-ID: <CAJKOXPfQHVGiLsL+FZ2jk-am=Xp6L5w=tLEQsGrP2TNLPgQ=vw@mail.gmail.com>
Subject: Re: [BUG BISECT] Net boot fails on VF50 after "dmaengine: fsl-edma:
 support little endian for edma driver"
To:     Fabio Estevam <festevam@gmail.com>
Cc:     Peng Ma <peng.ma@nxp.com>, Vinod Koul <vkoul@kernel.org>,
        dmaengine@vger.kernel.org,
        linux-kernel <linux-kernel@vger.kernel.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Tue, 2 Jul 2019 at 15:04, Fabio Estevam <festevam@gmail.com> wrote:
>
> Hi Krzysztof,
>
> On Tue, Jul 2, 2019 at 9:13 AM Krzysztof Koz=C5=82owski
> <k.kozlowski.k@gmail.com> wrote:
> >
> > Hi,
> >
> > Bisect pointed commit:
> > commit 002905eca5bedab08bafd9e325bbbb41670c7712
> > Author: Peng Ma <peng.ma@nxp.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 =3D "dmamux0", "dmamux1";
>                                 clocks =3D <&clks VF610_CLK_DMAMUX0>,
>                                         <&clks VF610_CLK_DMAMUX1>;
> +                               big-endian;
>                                 status =3D "disabled";
>                         };
>
> @@ -491,6 +492,7 @@
>                                 clock-names =3D "dmamux0", "dmamux1";
>                                 clocks =3D <&clks VF610_CLK_DMAMUX2>,
>                                         <&clks VF610_CLK_DMAMUX3>;
> +                               big-endian;
>                                 status =3D "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