On Friday 17 July 2009 03:02:31 Matthew L. Creech wrote:
> On Thu, Jul 16, 2009 at 9:15 AM, Rupesh Kumar<Rupesh.Kumar@lntemsys.com>
wrote:
> > In another try, i created yaffs2 RFS when booted with ramdisk
> > image(mounted empty flash partition as yaffs2 and copied RFS contents to
> > that) and then booted with that, it worked and board booted with yaffs2
> > RFS.
> > But, in this case during boot up it complains of bad blocks. and, when i
> > create/write some files to yaffs2 partition, it complains of "yaffs2
> > Chunks not erased " and also increases no of bad blocks. :(
> > I am not able to understand why writing in yaffs2 shall mark nand block
> > as bad :(
>
> Have you tried using a recent [mainline] kernel? I'm running a
> mostly-vanilla 2.6.29 kernel on a custom MPC8313-based board with a
> large-page (2k) NAND, and YAFFS gives me no errors when used similarly
> (using erase & populate, not mkyaffs2image). It flags bad blocks, of
> course, but they're real - maybe 5-10 total on a 1GB chip, and they're
> detected at mount time (it sounds like your errors are occurring after
> that).
>
> It might be worth taking a few minutes to build a more recent version
> and see if it makes your problems go away, if that's possible.
The problem is most likely in the ECC/bad block marking in mtd. Since this
varies from driver to driver, it is not a Linux version issue per se.
-- Charles
(text/plain)