linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sergeant Peppercorn <speppercorn109@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: UBIFS ECC errors
Date: Wed, 7 Aug 2019 09:52:26 -0700	[thread overview]
Message-ID: <CAMxq0fOJ0uqqzPRW_wBiAZS=KzpRy_waGHODErhjcLgRbX5ALQ@mail.gmail.com> (raw)
In-Reply-To: <CAMxq0fPvj+gMnUysDDN8j2wXNQj3Th_HwVV2NWmm8pjSe7Q_vQ@mail.gmail.com>

Also, would this apply fo my 4.9.88 IMX kernel as well as the TI 3.12.10 kernel?

On Wed, Aug 7, 2019 at 9:51 AM Sergeant Peppercorn
<speppercorn109@gmail.com> wrote:
>
> Hi, so are you saying that I should try to merge in these two commits
> for a proper fix for this?
> 730a43fbc135 ("mtd: nand: add nand_check_erased helper functions")
> fdf2e8210529 ("mtd: nand: gpmi: Fix failure when a erased page has a
> bitflip at BBM")
>
> I am assuming these are from the mainline kernel?
>
> If not, how do I fix this? this other patch, instead or with those two commits?
> http://lists.infradead.org/pipermail/linux-mtd/2014-January/051357.html
>
> The patch doesn't seem to be able to apply cleanly to my kernel so I
> must do some deep merging. I have not looked for the two commits yet.
>
> Are there any other alternatives?
>
> Thenks in advance for any help.
>
> On Sat, Aug 3, 2019 at 1:48 AM Richard Weinberger <richard@nod.at> wrote:
> >
> > ----- 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/

  reply	other threads:[~2019-08-07 16:52 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
2019-08-05 21:35       ` Sergeant Peppercorn
2019-08-07 16:51       ` Sergeant Peppercorn
2019-08-07 16:52         ` Sergeant Peppercorn [this message]
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='CAMxq0fOJ0uqqzPRW_wBiAZS=KzpRy_waGHODErhjcLgRbX5ALQ@mail.gmail.com' \
    --to=speppercorn109@gmail.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=richard@nod.at \
    /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).