All of lore.kernel.org
 help / color / mirror / Atom feed
From: Otto Blom <oblom586@gmail.com>
To: Richard Weinberger <richard@nod.at>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: mtd-utils io_paral test fails on NAND
Date: Tue, 26 Nov 2019 09:11:09 -0800	[thread overview]
Message-ID: <CAOfSrV2QTRbg+pD2TfRbCFfjcjR3UT6BGVSV_Nkg4YxJL6r2RA@mail.gmail.com> (raw)
In-Reply-To: <1237458020.97684.1574720847193.JavaMail.zimbra@nod.at>

Hi Richard !

nandpagetest ran for 12h+ w/o failing, so it looks like a driver
problem like you suggested.

All the times I've seen if fail (around 10) the failed page came back
with all zeros.. Which is a bit strange as I would think "random" /
duplicated page would be more likely. Maybe the page read fails
silently and the controller returns all zeros

Thanks for you help & insights in this !

/Otto

On Mon, Nov 25, 2019 at 2:27 PM Richard Weinberger <richard@nod.at> wrote:
>
> Otto,
>
> ----- Ursprüngliche Mail -----
> > Von: "Otto Blom" <oblom586@gmail.com>
> > An: "Richard Weinberger" <richard.weinberger@gmail.com>
> > CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> > Gesendet: Montag, 25. November 2019 18:22:10
> > Betreff: Re: mtd-utils io_paral test fails on NAND
>
> > Hi Richard !
> >
> > Interestingly I had flash_readtest running in a loop the whole weekend
> > without any errors. Although this test does not verify the data read
> > so it could point towards a controller / driver problem. I'm in the
> > process of upgrading the SDK from 2017.3 to 2019.2 to see if that
> > makes any difference
>
> pagetest shoud also verify the data.
>
> If it fails only on top of UBI another possible error source is
> DMA. Both UBI and UBIFS use vmalloced() buffers, a driver must not DMA
> from/to these and use bounce buffers. If the driver is buggy in this
> area everything looks shiny until you start using UBI...
>
> Is the bad data always zeros? This also does not sound like an UBI
> LEB->PEB mismatch.
>
> Thanks,
> //richard

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

  reply	other threads:[~2019-11-26 17:11 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 19:54 mtd-utils io_paral test fails on NAND Otto Blom
2019-11-22  9:53 ` Richard Weinberger
2019-11-25 17:22   ` Otto Blom
2019-11-25 22:27     ` Richard Weinberger
2019-11-26 17:11       ` Otto Blom [this message]
2019-11-26 20:26         ` Richard Weinberger
2019-12-03 17:43           ` Otto Blom
  -- strict thread matches above, loose matches on Subject: below --
2019-11-20 20:32 Otto Blom

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=CAOfSrV2QTRbg+pD2TfRbCFfjcjR3UT6BGVSV_Nkg4YxJL6r2RA@mail.gmail.com \
    --to=oblom586@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 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.