From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Fabio Estevam <festevam@gmail.com>
Cc: Sascha Hauer <s.hauer@pengutronix.de>,
linux-mtd@lists.infradead.org,
Sascha Hauer <kernel@pengutronix.de>
Subject: Re: imx27: Unsupported ECC algorithm
Date: Wed, 30 Sep 2020 16:58:31 +0200 [thread overview]
Message-ID: <20200930165831.418b8edd@xps13> (raw)
In-Reply-To: <CAOMZO5D8W+Z5enehxFt7XTPn6sEXe9pWM6Tn1SixMntkZ31Wgw@mail.gmail.com>
Hello,
Fabio Estevam <festevam@gmail.com> wrote on Tue, 29 Sep 2020 13:31:03
-0300:
> Hi Miquel,
>
> On Tue, Sep 29, 2020 at 8:39 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> > linux-next from 20200928 still reports the same error:
> >
> > https://storage.kernelci.org/next/master/next-20200928/arm/imx_v4_v5_defconfig/gcc-8/lab-pengutronix/baseline-imx27-phytec-phycard-s-rdk.html
> >
> > I checked that the fix pointed out by Sascha is not present in this tree though.
> >
> > I do see it fixed in linux-next from today (20200929), but the report
> > from 20200929 is not yet available.
> >
> > I will let you know after kernelci publishes the boot results from today's next.
>
> linux-next 20200929 has an even worse log with a new division by zero:
>
> https://storage.kernelci.org/next/master/next-20200929/arm/imx_v4_v5_defconfig/gcc-8/lab-pengutronix/baseline-imx27-phytec-phycard-s-rdk.html
I found a board (NTC C.H.I.P, sun5i R8 SoC) with a parallel NAND.
with the same DT properties but a different NAND controller driver I
could not reproduce the issue.
However, I did tried with soft BCH and I found a related error which I
just fixed. I also got a bug report from Intel's robot which I also
fixed. Perhaps what you see is related (still around this ->total entry
not being set at the right moment at probe time).
If tomorrow's report still returns an error, we will need someone
to get physical access to the device to add debugging code and track
down the failure.
Thanks,
Miquèl
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2020-09-30 14:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-16 13:49 imx27: Unsupported ECC algorithm Fabio Estevam
2020-09-17 16:13 ` Miquel Raynal
2020-09-17 16:45 ` Miquel Raynal
2020-09-17 17:12 ` Fabio Estevam
2020-09-21 9:40 ` Sascha Hauer
2020-09-28 15:20 ` Miquel Raynal
2020-09-29 11:39 ` Fabio Estevam
2020-09-29 16:31 ` Fabio Estevam
2020-09-29 17:46 ` Miquel Raynal
2020-09-30 14:58 ` Miquel Raynal [this message]
2020-10-01 21:39 ` Fabio Estevam
2020-10-13 17:14 ` Lucas Stach
2020-10-13 17:36 ` Miquel Raynal
2020-10-14 12:23 ` Fabio Estevam
2020-10-14 13:26 ` Miquel Raynal
2020-10-15 19:24 ` Fabio Estevam
2020-10-16 3:04 ` Han Xu
2020-10-16 6:39 ` Sascha Hauer
2020-10-16 7:53 ` Miquel Raynal
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=20200930165831.418b8edd@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).