From: "Franklin S Cooper Jr." <fcooper@ti.com>
To: <boris.brezillon@free-electrons.com>,
<computersforpeace@gmail.com>, <linux-mtd@lists.infradead.org>
Subject: Testing generic empty page bit flips recovery
Date: Wed, 30 Dec 2015 08:10:20 -0600 [thread overview]
Message-ID: <5683E5CC.6020008@ti.com> (raw)
I am trying to follow up on this discussion from this patch
set (https://patchwork.ozlabs.org/patch/539059/) which
suggested that Michael instead test the generic bitflips
recovery that is implemented by Boris "mtd: nand: properly
handle bitflips in erased pages" patchset
(http://lists.infradead.org/pipermail/linux-mtd/2015-September/061617.html).
I would like to test Boris patchset but first I need to
recreate the error that his patch is fixing.
The error that the patchset is attempting to fix isn't
something I have ever encountered before. Currently I am
trying to reproduce this issue on a TI K2E evm that uses the
davinci nand driver. I flashed the nand's file-system
partition with a ubi filesystem and the board is currently
set to boot using the file-system on the nand. After about
60 secs I cut the power from the board and boot the board
again. What I would expect is that the board will eventually
fail to mount the ubi filesystem but currently the board has
ran for over 24 hours and powered on and off over 1400 times
and its still mounting the file-system perfectly fine.
Any suggestions on a test case that I can use to force the
empty page bit flips error?
next reply other threads:[~2015-12-30 14:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-12-30 14:10 Franklin S Cooper Jr. [this message]
2015-12-30 14:40 ` Testing generic empty page bit flips recovery 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.
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=5683E5CC.6020008@ti.com \
--to=fcooper@ti.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@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.