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

Fabio Estevam
2021-04-19T12:49:28Z

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?