Testing a device using mtd_stresstest
pev at sketchymonkey.com
Fri Feb 11 09:25:07 EST 2011
Sometimes... When they are I've manually marked blocks as bad and
re-started the test run :-D I had wondered about whether it was blocks
naturally failing with use, but some of these blocks haven't been (Ok,
SHOULDNT have been!) erased anywhere near 100,000 times so I'm
suspicious about this. When I looked into it I noted that the
mtd_stresstest.ko doesn't mark blocks as bad ever so this is
potentially something that would occur. However, nandtest.c in
mtd-utils I notice *does* support marking of bad blocks during
testing. Should I consider using this instead? I'm not sure what the
relationship between these test tools is...?
On 11 February 2011 13:58, Karl Beldan <karl.beldan at gmail.com> wrote:
> On Mon, Feb 7, 2011 at 2:44 PM, David Peverley <pev at sketchymonkey.com>
>> Hi Artem,
>> Many thanks for the response ;
>> > MTD code is currently broken and CONFIG_MTD_NAND_VERIFY_WRITE causes
>> > errors when sub-pages are used. You should either disable this
>> > configuration option or fix MTD. We have this in our FAQ:
>> > http://www.linux-mtd.infradead.org/faq/ubi.html#L_subpage_verify_fail
>> I'm not sure what the implication of this is ; I understand that this
>> will cause the subpage test to fail with CONFIG_MTD_NAND_VERIFY_WRITE
>> enabled. However, the FAQ I had discounted as we use YAFFS2 and not
>> UBIFS. Given that should I still disable the write verify? At the
>> moment I'm inclined to leave it enabled as it seems to be regularly
>> catching failures that should not occur, such as the stress-test
>> failures noted.
>> We've also noticed that every so often we see "uncorrectable error:"
>> messages from nand_ecc.c - do you have any suggestions as to where to
>> start investigating here? So far I can't find a pattern to occurrences
>> or a regular way to reproduce.
> By any chance, wouldn't those "uncorrectable errors" happen to be within the
> same pages/blocks each time ?
More information about the linux-mtd