From: Richard Weinberger <richard@nod.at>
To: Otto Blom <oblom586@gmail.com>
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: mtd-utils io_paral test fails on NAND
Date: Tue, 26 Nov 2019 21:26:47 +0100 (CET) [thread overview]
Message-ID: <698719689.98401.1574800007975.JavaMail.zimbra@nod.at> (raw)
In-Reply-To: <CAOfSrV2QTRbg+pD2TfRbCFfjcjR3UT6BGVSV_Nkg4YxJL6r2RA@mail.gmail.com>
Otto,
----- Ursprüngliche Mail -----
> Von: "Otto Blom" <oblom586@gmail.com>
> An: "richard" <richard@nod.at>
> CC: "linux-mtd" <linux-mtd@lists.infradead.org>
> Gesendet: Dienstag, 26. November 2019 18:11:09
> Betreff: Re: mtd-utils io_paral test fails on NAND
> 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
If I was in your situation I'd try to figure where the 0x00 bytes come from.
Does the driver write zeros? Maybe the page is zero initialized and the controller
completely fails to transfer data and does not signal it?
Since nandpagetest works, but UBI not it points into the direction of DMA.
On the other hand, UBI uses offsets. Maybe this is broken in the driver...
I had more than once the case where a driver worked like charm if you asked
it for a single page or a whole block but failed if you asked for N pages
at a given offset.
Thanks,
//richard
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-11-26 20:27 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
2019-11-26 20:26 ` Richard Weinberger [this message]
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=698719689.98401.1574800007975.JavaMail.zimbra@nod.at \
--to=richard@nod.at \
--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).