From: Richard Weinberger <richard.weinberger@gmail.com>
To: Otto Blom <oblom586@gmail.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mtd-utils io_paral test fails on NAND
Date: Fri, 22 Nov 2019 10:53:00 +0100 [thread overview]
Message-ID: <CAFLxGvziLKNA0gcPo+EGwfpuv6Fe6=sNOfhEa1DR7sN0oOxzMg@mail.gmail.com> (raw)
In-Reply-To: <CAOfSrV1CNn6EpPkAkP8F2VQUrit_B-t89sSxW=08zyKVOdt9AA@mail.gmail.com>
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-22 9:53 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 [this message]
2019-11-25 17:22 ` Otto Blom
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='CAFLxGvziLKNA0gcPo+EGwfpuv6Fe6=sNOfhEa1DR7sN0oOxzMg@mail.gmail.com' \
--to=richard.weinberger@gmail.com \
--cc=linux-mtd@lists.infradead.org \
--cc=oblom586@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).