Slub debugging NAND error in 2.6.25.10.atmel.2

[Haavard Skinnemoen]

"Eirik Aanonsen" <eaa at wprmedical.com> wrote:
> The fault from my posts here seems to be related to a wrong definition related to my board. I had to change the include/linux/mtd/nand.h
> Where I had to replace:
> #define NAND_MAX_OOBSIZE	64
> #define NAND_MAX_PAGESIZE	2048
> With:
> #define NAND_MAX_OOBSIZE	128
> #define NAND_MAX_PAGESIZE	4096
> Nice the nand driver did not allocate enogh memory to handle ny nand flash. This was what caused the overwriting of the memory in my case.

Ah. That makes sense. It probably explains that weird oops loop you got
too -- all kinds of weird things can happen when memory is overwritten
like this.

> It could prove useifull to have these values in KConfig instead in an header, since the size of these values differ a lot from chip to chip?

I think they should just be adjusted. At least that's what the comment
directly above them says:

/* This constant declares the max. oobsize / page, which
 * is supported now. If you add a chip with bigger oobsize/page
 * adjust this accordingly.
 */

Haavard