From: Otto Blom <oblom586@gmail.com>
To: Richard Weinberger <richard.weinberger@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd-utils io_paral test fails on NAND
Date: Mon, 25 Nov 2019 09:22:10 -0800 [thread overview]
Message-ID: <CAOfSrV0ZuG5qz0aW1bU30iZ2RX2vi4Y5aYF128XjkRUd1h+EhA@mail.gmail.com> (raw)
In-Reply-To: <CAFLxGvziLKNA0gcPo+EGwfpuv6Fe6=sNOfhEa1DR7sN0oOxzMg@mail.gmail.com>
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
Thanks,
/Otto
On Fri, Nov 22, 2019 at 1:53 AM Richard Weinberger
<richard.weinberger@gmail.com> wrote:
>
> On Thu, Nov 21, 2019 at 8:54 PM Otto Blom <oblom586@gmail.com> wrote:
> >
> > Hello All !
> >
> > A couple of updates on this problem. Turns out io_read also fails in
> > the same way as io_paral - A page of data comes back as all zeros.
> > Interestingly I added a retry option to see if it is a read or write
> > problem and turns out every single time so far the data is correct
> > when I read it a second time.
> >
> > In summary when I run runubitests.sh it passes about 70% of the time,
> > io_paral fails 25% and io_read the remaining 5%
> >
> > Any recommendations on what to try next ?
>
> Test one layer deeper. e.g. flash_readtest.
>
> --
> Thanks,
> //richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-11-25 17:22 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 [this message]
2019-11-25 22:27 ` Richard Weinberger
2019-11-26 17:11 ` Otto Blom
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=CAOfSrV0ZuG5qz0aW1bU30iZ2RX2vi4Y5aYF128XjkRUd1h+EhA@mail.gmail.com \
--to=oblom586@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard.weinberger@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).