From: Matthieu CASTET <matthieu.castet@parrot.com>
To: "dedekind1@gmail.com" <dedekind1@gmail.com>
Cc: Colin Foe-Parker <colin.foeparker@aclimalabs.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: [UBIFS][CRC Mismatch]
Date: Mon, 4 Mar 2013 09:39:34 +0100 [thread overview]
Message-ID: <51345DC6.9090504@parrot.com> (raw)
In-Reply-To: <1362236681.2745.19.camel@sauron>
Artem Bityutskiy a écrit :
> On Tue, 2013-02-19 at 10:44 -0800, Colin Foe-Parker wrote:
>> Hi All,
>>
>> I am seeing an issue that I would love some outside help on.
>>
>> I am running UBIFS on TI's latest Linux 3.2.0 PSP (5.06.00.09) and
>> their AM3352 ARMv7a processor. We are using a Micron MT29F2G08ABBEAHC
>> 2 Gb SLC NAND chip. (w/ a BCH8 ECC)
>>
>> 3.) Memory Corruption: Is it possible the the write buffer can be
>> corrupted before it is written to NAND? Hence having a bad CRC value
>> in NAND?
On some of our product we saw ubifs metadata corrupted by kernel pointer. But
the crc was good (ie corruption done before crc).
But we also saw corruption during ubi scubbing. The ubi buffer was corrupted
after the nand read but before crc compute and nand write. This cause good ubi
crc but bad ubifs crc.
What you should check is the type of corruption you have (for example by
ignoring crc failure and try to parse data).
Matthieu
next prev parent reply other threads:[~2013-03-04 8:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-19 18:44 [UBIFS][CRC Mismatch] Colin Foe-Parker
2013-03-02 15:04 ` Artem Bityutskiy
2013-03-04 6:44 ` Gupta, Pekon
2013-03-04 8:39 ` Matthieu CASTET [this message]
2013-03-02 15:24 ` Artem Bityutskiy
[not found] <20980858CB6D3A4BAE95CA194937D5E73E99B6E6@DBDE01.ent.ti.com>
2013-03-04 17:23 ` Colin Foe-Parker
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=51345DC6.9090504@parrot.com \
--to=matthieu.castet@parrot.com \
--cc=colin.foeparker@aclimalabs.com \
--cc=dedekind1@gmail.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