Re: imx27: No space left to write bad block table

Fabio Estevam
2021-04-19T13:03:24Z

On Mon, Apr 19, 2021 at 9:48 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> On Mon, Apr 19, 2021 at 9:41 AM Fabio Estevam <festevam@gmail.com> wrote:
>
> > This commit landed in linux-next 20210329. I was able to find the
> > kernelci log for this version and NAND is correctly probed:
> > https://storage.kernelci.org/next/master/next-20210329/arm/imx_v4_v5_defconfig/gcc-8/lab-pengutronix/baseline-imx27-phytec-phycard-s-rdk.html
> >
> > The first NAND error starts with 20210330:
> > https://storage.kernelci.org/next/master/next-20210330/arm/imx_v4_v5_defconfig/gcc-8/lab-pengutronix/baseline-imx27-phytec-phycard-s-rdk.html
>
> linux-next 20210329 introduced the following logs that were not
> present previously:
>
> Bad block table written to 0x000007fa0000, version 0x01
> Bad block table written to 0x000007f80000, version 0x01
>
> Maybe this new 'two Bad block tables' will confuse the subsequent boots?

Also, prior to linux-next 20210329 the Bad Block table could be
correctly located:
https://storage.kernelci.org/next/master/next-20210324/arm/imx_v4_v5_defconfig/gcc-8/lab-pengutronix/baseline-imx27-phytec-phycard-s-rdk.html

Bad block table found at page 65472, version 0x01
Bad block table found at page 65408, version 0x01

which matches the Bad block table reported by Barebox.

However, in linux-next 20210329 the bad block table cannot be found anymore:

Bad block table not found for chip 0
Bad block table not found for chip 0

So in fact there is a regression starting with linux-next 20210329.

Could it be caused by bd9c9fe2ad04 ("mtd: rawnand: bbt: Skip bad
blocks when searching for the BBT in NAND")?

Thanks