Linux-mtd Archive on
 help / color / Atom feed
From: Otto Blom <>
To: Richard Weinberger <>
Cc: linux-mtd <>
Subject: Re: mtd-utils io_paral test fails on NAND
Date: Tue, 3 Dec 2019 09:43:58 -0800
Message-ID: <> (raw)
In-Reply-To: <>

Hi Richard !

I updated to Petalinux 2019.2 and while it still fails it now fails in
a different manner. Previously only the reads failed and it was a full
page missing. Now the writes fails and its no longer full pages. 64
bytes at the start of the page has seemingly random data, then correct
data for 960 bytes, then another 128bytes of random data followed by
correct data. So this feels more like some kind of DMA problem. I'll
contact Xilinx to see what they say

Thanks for your help !


On Tue, Nov 26, 2019 at 12:26 PM Richard Weinberger <> wrote:
> Otto,
> ----- Ursprüngliche Mail -----
> > Von: "Otto Blom" <>
> > An: "richard" <>
> > CC: "linux-mtd" <>
> > 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

  reply index

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 19:54 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
2019-12-03 17:43           ` Otto Blom [this message]
  -- strict thread matches above, loose matches on Subject: below --
2019-11-20 20:32 Otto Blom

Reply instructions:

You may reply publically 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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='' \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Linux-mtd Archive on

Archives are clonable:
	git clone --mirror linux-mtd/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 linux-mtd linux-mtd/ \
	public-inbox-index linux-mtd

Example config snippet for mirrors

Newsgroup available over NNTP:

AGPL code for this site: git clone