[Yaffs] Yaffs2 erasure issue on MT29 NAND part

Top Page
Attachments:
Message as email
+ (text/plain)
Delete this message
Reply to this message
Author: Andrew McKay
Date:  
To: yaffs
Subject: [Yaffs] Yaffs2 erasure issue on MT29 NAND part
Hi,

I'm using YAFFS2 on a Micron 2GB NAND part (MT29F16G08). I'm using kernel
version 2.6.20.4. I have back ported a patch for 128Bit OOB support at the MTD
level and things seem to be working fine from that perspective. However during
bootup I see messages like:

**>> Erasure failed 302
**>> Block 302 retired
Block 302 is in state 9 after gc, should be erased
page 134426 in gc has no object: 0 0 0
**>> Erasure failed 2100
**>> Block 2100 retired
Block 2100 is in state 9 after gc, should be erased

This message repeats every time the board is booted. I would assume that if a
block is retired it should be listed in the bad block list during boot up. This
device has a long long list of bad blocks (some of them may have gotten that way
during development of my NAND driver). Another board we are using has less bad
blocks but also has messages that it retired a block, and yet on next boot it
does it again.

Anybody have any hints as to what I should be looking for, or whether this is
really an issue or not?

Thanks,
Andrew
Iders Inc.