From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: Steve deRosier <derosier@gmail.com>
Cc: Boris Brezillon <boris.brezillon@free-electrons.com>,
Brian Norris <computersforpeace@gmail.com>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: Testing generic empty page bit flips recovery
Date: Wed, 30 Dec 2015 11:02:11 -0600 [thread overview]
Message-ID: <56840E13.1020206@ti.com> (raw)
In-Reply-To: <CALupW3BqcfHJWYBPjQJr-tBhPZNxSWWBouBF31UY2Cc=h9vwfA@mail.gmail.com>
On 12/30/2015 10:52 AM, Steve deRosier wrote:
> On Wed, Dec 30, 2015 at 8:40 AM, Franklin S Cooper Jr. <fcooper@ti.com> wrote:
>> One thing that confuses me is if I repeatedly call nanddump
>> I continue to get the "ECC: 4 corrected bitflips" message
>> and the "ECC corrected" count increases by 4 each time. If
>> these bits are being corrected which is apparent from
>> looking at the output of nanddump shouldn't sequential calls
>> indicate that no bitflips needed to be corrected since it
>> was corrected previously?
>>
> Hi Franklin,
>
> I'm making a guess at the source of your confusion, but I've had to
> answer this to repeated colleagues recently, so I'll give it a try.
>
> I think you're expecting the "correction" to actually be written and
> fixed on-flash. This is not the case.
>
> Bitflip corrections are applied as the flash data is read. Every time.
> So once a bit is flipped on the NAND, it will always stay that way on
> the physical device until erased and rewritten. Which doesn't happen
> for something as minor as a single bit-flip. So from that point on, it
> will always read and correct the flip and report it to the kernel log.
>
> UBI will move the data once the threshold gets hit, but up until that
> point it will continue to read the same bitflip and correct it.
>
> Hope that helps.
>
> - Steve
Steve,
That makes perfect sense. Thanks for explaining.
next prev parent reply other threads:[~2015-12-30 17:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 14:10 Testing generic empty page bit flips recovery Franklin S Cooper Jr.
2015-12-30 14:40 ` Boris Brezillon
2015-12-30 15:33 ` Franklin S Cooper Jr.
2015-12-30 15:55 ` Boris Brezillon
2015-12-30 16:02 ` Boris Brezillon
2015-12-30 16:40 ` Franklin S Cooper Jr.
2015-12-30 16:52 ` Steve deRosier
2015-12-30 17:02 ` Franklin S Cooper Jr. [this message]
2015-12-30 16:59 ` Boris Brezillon
2015-12-30 17:45 ` Franklin S Cooper Jr.
2015-12-30 17:53 ` Boris Brezillon
2015-12-30 18:07 ` Franklin S Cooper Jr.
2015-12-30 19:43 ` Boris Brezillon
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=56840E13.1020206@ti.com \
--to=fcooper@ti.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=derosier@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.