linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Boris Brezillon <boris.brezillon@collabora.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: linux-mtd@lists.infradead.org, kernel@pengutronix.de
Subject: Re: Prevent Nand page writes on Power failure
Date: Thu, 21 Feb 2019 09:10:55 +0100	[thread overview]
Message-ID: <20190221091055.266b9627@collabora.com> (raw)
In-Reply-To: <20190220135820.b2ku2unaxxdqflut@pengutronix.de>

Hi Sascha,

On Wed, 20 Feb 2019 14:58:20 +0100
Sascha Hauer <s.hauer@pengutronix.de> wrote:

> Hi All,
> 
> I have hardware here for which the normal way to turn off is just to cut
> the power. When the powercut happens during a NAND page write then we
> get more or less completely written pages during next boot. Very rarely
> it seems to happen that such a half written page with only very few
> flipped bits is erroneously detected as empty and written again which
> then results in ECC errors when reading the data.

This should definitely be fixed, maybe by lowering the bitflip
threshold when doing the empty check. Do you know the ECC strength and
the number of bitflips you have when that problem occurs?

Regards,

Boris

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  parent reply	other threads:[~2019-02-21  8:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-20 13:58 Prevent Nand page writes on Power failure Sascha Hauer
2019-02-21  0:05 ` Richard Weinberger
2019-02-21  8:39   ` Sascha Hauer
2019-02-21  9:28     ` Richard Weinberger
2019-02-21  8:10 ` Boris Brezillon [this message]
2019-02-21 10:17   ` Sascha Hauer
2019-02-21 10:36     ` Boris Brezillon
2019-02-21 11:21       ` Sascha Hauer
2019-02-21 11:37         ` Boris Brezillon
2019-02-21 12:17           ` Richard Weinberger
2019-02-21 13:27           ` Sascha Hauer
2019-02-25  8:56 ` Sascha Hauer
2019-02-25 11:28   ` Richard Weinberger
2019-02-26  9:10     ` Sascha Hauer

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=20190221091055.266b9627@collabora.com \
    --to=boris.brezillon@collabora.com \
    --cc=kernel@pengutronix.de \
    --cc=linux-mtd@lists.infradead.org \
    --cc=s.hauer@pengutronix.de \
    /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).