From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Cardoen Pieter <P.Cardoen@TELEVIC.com>
Cc: "richard@nod.at" <richard@nod.at>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>,
Boris Brezillon <Boris.Brezillon@bootlin.com>
Subject: Re: ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB
Date: Tue, 22 May 2018 09:29:41 +0200 [thread overview]
Message-ID: <20180522092941.05c3c223@xps13> (raw)
In-Reply-To: <AM0PR0702MB36185844E179A06774067996FF940@AM0PR0702MB3618.eurprd07.prod.outlook.com>
Hi Pieter,
Please always add Boris in cc please.
On Tue, 22 May 2018 07:19:54 +0000, Cardoen Pieter
<P.Cardoen@TELEVIC.com> wrote:
> Dear
>
>
> Can someone advice me with this question. It is blocking me and I don't know how to debug this.
>
>
> I am currently trying to use the mainline kernel on a custom imx6ul board with an SLC NAND flash device (29F4G08ABADAH4). When the rootfs is mounted, I get continuously ECC errors (see log below).
>
> I am however sure that the rootfs is programmed. The device boots with an older kernel version on the same device.
>
> I also noticed that with my previous kernel version, it used mtd->_read in function mtd_read while now it is using mtd->_read_oob.
>
> When the gpmi driver is loaded, the device gets scanned for bad blocks. In that case nand_read_oob is executed and this results in a call to nand_do_read_oob:
>
> if (!ops->datbuf)
> ret = nand_do_read_oob(mtd, from, ops);
> else
> ret = nand_do_read_ops(mtd, from, ops);
>
> Can someone assist me how to debug this issue?
As requested in a previous thread by Boris, can you please share the
exact version of each kernel you used there? What version work, what
version does not.
Thanks,
Miquèl
prev parent reply other threads:[~2018-05-22 7:29 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-17 13:38 ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB Cardoen Pieter
2018-05-22 7:19 ` Cardoen Pieter
2018-05-22 7:29 ` Miquel Raynal [this message]
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=20180522092941.05c3c223@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=Boris.Brezillon@bootlin.com \
--cc=P.Cardoen@TELEVIC.com \
--cc=linux-mtd@lists.infradead.org \
--cc=richard@nod.at \
/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