From: Richard Weinberger <richard@nod.at>
To: Sergeant Peppercorn <speppercorn109@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS ECC errors
Date: Sat, 3 Aug 2019 10:48:49 +0200 (CEST) [thread overview]
Message-ID: <1019514474.57102.1564822129140.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAMxq0fO=0P8972FKvscmNxCBxq0m8_f2DST-Oa9HtNeUA-FKsA@mail.gmail.com>
----- Ursprüngliche Mail -----
> Von: "Sergeant Peppercorn" <speppercorn109@gmail.com>
> An: "Richard Weinberger" <richard.weinberger@gmail.com>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> Gesendet: Freitag, 2. August 2019 18:14:55
> Betreff: Re: UBIFS ECC errors
> Hi, many thanks for the reply.
>
> I have seen posts on bitflips in empty space issues before, but don't
> remember seeing any fixes. Does this mean the kernel UBI drivers must
> be patched? Can you elaborate on what fixes or where to find patches,
> etc, or what to do about this, then? All I care about is getting this
> to work, and hopefully without needing to reformat the root file
> system on 50,000 units in the field.
Your kernel is pretty old, so I guess you don't have this commit:
730a43fbc135 ("mtd: nand: add nand_check_erased helper functions")
Bitflips in empty pages should be handled in the NAND layer.
Please don't blindly apply this patch, it may have dependencies or will
uncover other bugs. Such as fix:
fdf2e8210529 ("mtd: nand: gpmi: Fix failure when a erased page has a bitflip at BBM")
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-08-03 8:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 16:24 UBIFS ECC errors Sergeant Peppercorn
2019-08-01 8:03 ` Richard Weinberger
2019-08-02 16:14 ` Sergeant Peppercorn
2019-08-03 8:48 ` Richard Weinberger [this message]
2019-08-05 21:35 ` Sergeant Peppercorn
2019-08-07 16:51 ` Sergeant Peppercorn
2019-08-07 16:52 ` Sergeant Peppercorn
2019-08-13 21:35 ` Richard Weinberger
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=1019514474.57102.1564822129140.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--cc=linux-mtd@lists.infradead.org \
--cc=speppercorn109@gmail.com \
/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).