If it's the driver, like Charles said, it won't be any of these, but the
(kernel) source for the mtd device you are using.
-Ketil
On Nov 30, 2011 6:12 AM, "Brilliantov Kirill Vladimirovich" <
brilliantov@byterg.ru> wrote:
> Charles Manning wrote on 11/30/2011 06:57 AM:
>
>>
>> This problem is most likely caused by some sort of corruption of the tags
>> in
>> the driver.
>>
>>
>>
> Thank your for your reply, Charles!
> What function or file can I check?
> $ find fs/yaffs2/ -name *.c -o -name *.h
> fs/yaffs2/moduleconfig.h
> fs/yaffs2/yaffs_checkptrw.h
> fs/yaffs2/yaffs_tagscompat.c
> fs/yaffs2/yaffs_mtdif2.c
> fs/yaffs2/yaffs_qsort.h
> fs/yaffs2/yaffs_ecc.c
> fs/yaffs2/yaffs_nand.c
> fs/yaffs2/yaffs_nandemul2k.h
> fs/yaffs2/yaffs_packedtags2.h
> fs/yaffs2/yaffs_tagscompat.h
> fs/yaffs2/yaffs_getblockinfo.h
> fs/yaffs2/yaffs_mtdif.h
> fs/yaffs2/yaffs_mtdif1.c
> fs/yaffs2/yaffs_checkptrw.c
> fs/yaffs2/yaffs_guts.h
> fs/yaffs2/yaffs_guts.c
> fs/yaffs2/yaffs_tagsvalidity.h
> fs/yaffs2/yaffs_tagsvalidity.c
> fs/yaffs2/yaffs_fs.c
> fs/yaffs2/yaffs_mtdif1.h
> fs/yaffs2/yaffs_packedtags2.c
> fs/yaffs2/yaffs_mtdif.c
> fs/yaffs2/yaffs_qsort.c
> fs/yaffs2/yportenv.h
> fs/yaffs2/yaffs_ecc.h
> fs/yaffs2/yaffs_nand.h
> fs/yaffs2/yaffs_mtdif2.h
> fs/yaffs2/devextras.h
> fs/yaffs2/yaffs_packedtags1.c
> fs/yaffs2/yaffs_packedtags1.h
> fs/yaffs2/yaffsinterface.h
>
>
> --
> Best regards,
> Brilliantov Kirill Vladimirovich
>
>
> ______________________________**_________________
> yaffs mailing list
> yaffs@lists.aleph1.co.uk
> http://lists.aleph1.co.uk/cgi-**bin/mailman/listinfo/yaffs<http://lists.aleph1.co.uk/cgi-bin/mailman/listinfo/yaffs>
>
(text/plain)