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

Fabio Estevam
2021-04-19T13:57:44Z

Hi Miquel,

On Mon, Apr 19, 2021 at 10:40 AM Miquel Raynal
<miquel.raynal@bootlin.com> wrote:

> I am pretty sure now the commit I pointed earlier today is the root
> cause (but I don't know why, yet). Somehow it skips the bad block table
> which is more or less declared like a bad block from a 'low level'
> point of view (so that the user cannot erase/overwrite it). Here,
> the kernel does not find the valid BBT. It then creates a new couple of
> BBT. But doing so at the next boot, the recently created BBT won't be
> detected anymore... until there are no more free blocks reserved for
> that and that's where the probe fails.
>
> So yes, the NAND controller driver probes correctly with next-20210329
> but in fact the real bad block table is not found and this is the root
> cause.

Ok, good. I will submit a revert then.

Thanks