From: JerinJacob <jerin.jacob@maxim-ic.com>
To: "Artem.Bityutskiy@nokia.com" <Artem.Bityutskiy@nokia.com>
Cc: "linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
"Hunter Adrian \(Nokia-D/Helsinki\)" <adrian.hunter@nokia.com>
Subject: Re: UBIFS Error
Date: Fri, 11 Sep 2009 17:48:13 +0530 [thread overview]
Message-ID: <4AAA4005.9080707@maxim-ic.com> (raw)
In-Reply-To: <4AA90351.3050000@nokia.com>
Artem Bityutskiy wrote:
> On 09/10/2009 03:53 PM, ext JerinJacob wrote:
>
>> Hi Artem,
>>
>> Thanks for the support.
>> We are using 2.6.30.
>>
>
> And finally, could you please try to reproduce this problem with
> nandsim:
> http://www.linux-mtd.infradead.org/faq/nand.html#L_nand_nandsim
>
>>> Unfortunately, I couldn't reproduce the problem with nandsim.It
works with nansim.
However i couldn't test with 1GiB nandsim as it needs 1GiB ram.Tested
with 512MiB nandsim.
I guess it is a could be data corruption either in platform specific
driver or ubifs.
Is there any way we can validate the platform specific nand driver ?
Please let me know your views on this?
Actually we are in the process of migrating from yaffs to ubifs, The
same test application works with
yaffs as well.
next prev parent reply other threads:[~2009-09-11 12:18 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-08 6:02 UBIFS Error JerinJacob
2009-09-08 7:57 ` Adrian Hunter
2009-09-08 12:16 ` JerinJacob
2009-09-10 12:01 ` JerinJacob
2009-09-10 12:13 ` Artem Bityutskiy
2009-09-10 12:53 ` JerinJacob
2009-09-10 13:46 ` Artem Bityutskiy
2009-09-10 14:22 ` JerinJacob
2009-09-11 12:18 ` JerinJacob [this message]
2009-09-14 14:27 ` Artem Bityutskiy
2009-09-14 14:29 ` Artem Bityutskiy
2009-09-15 8:28 ` JerinJacob
2009-09-17 8:38 ` JerinJacob
2009-09-28 11:22 ` Artem Bityutskiy
2009-09-29 5:48 ` JerinJacob
2009-09-30 5:37 ` Artem Bityutskiy
2009-09-14 15:07 ` JerinJacob
2009-09-14 15:08 ` Artem Bityutskiy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4AAA4005.9080707@maxim-ic.com \
--to=jerin.jacob@maxim-ic.com \
--cc=Artem.Bityutskiy@nokia.com \
--cc=adrian.hunter@nokia.com \
--cc=linux-mtd@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).