All of lore.kernel.org
 help / color / mirror / Atom feed
From: Boris Brezillon <bbrezillon@kernel.org>
To: Martin Kepplinger <martin.kepplinger@ginzinger.com>
Cc: Manfred Schlaegl <manfred.schlaegl@ginzinger.com>,
	richard@nod.at, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org, marek.vasut@gmail.com,
	linux-mtd@lists.infradead.org, Fabio Estevam <festevam@gmail.com>,
	miquel.raynal@bootlin.com, han.xu@nxp.com,
	computersforpeace@gmail.com, dwmw2@infradead.org
Subject: Re: [PATCH v2] mtd: rawnand: gpmi: fix MX28 bus master lockup problem
Date: Wed, 6 Feb 2019 09:42:26 +0100	[thread overview]
Message-ID: <20190206094226.1dadbf61@kernel.org> (raw)
In-Reply-To: <20190205155251.18733-1-martin.kepplinger@ginzinger.com>

Hi Martin,

On Tue, 5 Feb 2019 16:52:51 +0100
Martin Kepplinger <martin.kepplinger@ginzinger.com> wrote:

> Disable BCH soft reset according to MX23 erratum #2847 ("BCH soft
> reset may cause bus master lock up") for MX28 too. It has the same
> problem.
> 
> Observed problem: once per 100,000+ MX28 reboots NAND read failed on
> DMA timeout errors:
> [    1.770823] UBI: attaching mtd3 to ubi0
> [    2.768088] gpmi_nand: DMA timeout, last DMA :1
> [    3.958087] gpmi_nand: BCH timeout, last DMA :1
> [    4.156033] gpmi_nand: Error in ECC-based read: -110
> [    4.161136] UBI warning: ubi_io_read: error -110 while reading 64
> bytes from PEB 0:0, read only 0 bytes, retry
> [    4.171283] step 1 error
> [    4.173846] gpmi_nand: Chip: 0, Error -1
> 
> Without BCH soft reset we successfully executed 1,000,000 MX28 reboots.
> 
> I have a quote from NXP regarding this problem, from July 18th 2016:
> 
> "As the i.MX23 and i.MX28 are of the same generation, they share many
> characteristics. Unfortunately, also the erratas may be shared.
> In case of the documented erratas and the workarounds, you can also
> apply the workaround solution of one device on the other one. This have
> been reported, but I’m afraid that there are not an estimated date for
> updating the Errata documents.
> Please accept our apologies for any inconveniences this may cause."
> 
> Fixes: 6f2a6a52560a ("mtd: nand: gpmi: reset BCH earlier, too, to avoid
> NAND startup problems")

Please make sure this Fixes line is not wrapped next time.

Thanks,

Boris

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

WARNING: multiple messages have this Message-ID (diff)
From: Boris Brezillon <bbrezillon@kernel.org>
To: Martin Kepplinger <martin.kepplinger@ginzinger.com>
Cc: <han.xu@nxp.com>, <miquel.raynal@bootlin.com>, <richard@nod.at>,
	<dwmw2@infradead.org>, <computersforpeace@gmail.com>,
	<marek.vasut@gmail.com>, <linux-mtd@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <stable@vger.kernel.org>,
	Manfred Schlaegl <manfred.schlaegl@ginzinger.com>,
	Fabio Estevam <festevam@gmail.com>
Subject: Re: [PATCH v2] mtd: rawnand: gpmi: fix MX28 bus master lockup problem
Date: Wed, 6 Feb 2019 09:42:26 +0100	[thread overview]
Message-ID: <20190206094226.1dadbf61@kernel.org> (raw)
In-Reply-To: <20190205155251.18733-1-martin.kepplinger@ginzinger.com>

Hi Martin,

On Tue, 5 Feb 2019 16:52:51 +0100
Martin Kepplinger <martin.kepplinger@ginzinger.com> wrote:

> Disable BCH soft reset according to MX23 erratum #2847 ("BCH soft
> reset may cause bus master lock up") for MX28 too. It has the same
> problem.
> 
> Observed problem: once per 100,000+ MX28 reboots NAND read failed on
> DMA timeout errors:
> [    1.770823] UBI: attaching mtd3 to ubi0
> [    2.768088] gpmi_nand: DMA timeout, last DMA :1
> [    3.958087] gpmi_nand: BCH timeout, last DMA :1
> [    4.156033] gpmi_nand: Error in ECC-based read: -110
> [    4.161136] UBI warning: ubi_io_read: error -110 while reading 64
> bytes from PEB 0:0, read only 0 bytes, retry
> [    4.171283] step 1 error
> [    4.173846] gpmi_nand: Chip: 0, Error -1
> 
> Without BCH soft reset we successfully executed 1,000,000 MX28 reboots.
> 
> I have a quote from NXP regarding this problem, from July 18th 2016:
> 
> "As the i.MX23 and i.MX28 are of the same generation, they share many
> characteristics. Unfortunately, also the erratas may be shared.
> In case of the documented erratas and the workarounds, you can also
> apply the workaround solution of one device on the other one. This have
> been reported, but I’m afraid that there are not an estimated date for
> updating the Errata documents.
> Please accept our apologies for any inconveniences this may cause."
> 
> Fixes: 6f2a6a52560a ("mtd: nand: gpmi: reset BCH earlier, too, to avoid
> NAND startup problems")

Please make sure this Fixes line is not wrapped next time.

Thanks,

Boris

  parent reply	other threads:[~2019-02-06  8:42 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-05 15:52 [PATCH v2] mtd: rawnand: gpmi: fix MX28 bus master lockup problem Martin Kepplinger
2019-02-05 15:52 ` Martin Kepplinger
2019-02-05 15:52 ` Martin Kepplinger
2019-02-05 16:28 ` Han Xu
2019-02-05 16:28   ` Han Xu
2019-02-06  8:35 ` [v2] " Boris Brezillon
2019-02-06  8:35   ` Boris Brezillon
2019-02-06  8:42 ` Boris Brezillon [this message]
2019-02-06  8:42   ` [PATCH v2] " Boris Brezillon
     [not found] ` <20190207163215.9174B2190A@mail.kernel.org>
2019-02-08 10:49   ` Martin Kepplinger

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=20190206094226.1dadbf61@kernel.org \
    --to=bbrezillon@kernel.org \
    --cc=computersforpeace@gmail.com \
    --cc=dwmw2@infradead.org \
    --cc=festevam@gmail.com \
    --cc=han.xu@nxp.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=manfred.schlaegl@ginzinger.com \
    --cc=marek.vasut@gmail.com \
    --cc=martin.kepplinger@ginzinger.com \
    --cc=miquel.raynal@bootlin.com \
    --cc=richard@nod.at \
    --cc=stable@vger.kernel.org \
    /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.