From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Cardoen Pieter <P.Cardoen@TELEVIC.com>
Cc: "han.xu@nxp.com" <han.xu@nxp.com>,
"boris.brezillon@free-electrons.com"
<boris.brezillon@free-electrons.com>,
"richard@nod.at" <richard@nod.at>,
"dwmw2@infradead.org" <dwmw2@infradead.org>,
"computersforpeace@gmail.com" <computersforpeace@gmail.com>,
"marek.vasut@gmail.com" <marek.vasut@gmail.com>,
"cyrille.pitchen@wedev4u.fr" <cyrille.pitchen@wedev4u.fr>,
"linux-mtd@lists.infradead.org" <linux-mtd@lists.infradead.org>
Subject: Re: GPMI nand flash ECC errors with mainline kernel
Date: Tue, 15 May 2018 13:59:00 +0200 [thread overview]
Message-ID: <20180515135900.3bf24b98@xps13> (raw)
In-Reply-To: <HE1PR0702MB362877849767B637814CF9B6FF930@HE1PR0702MB3628.eurprd07.prod.outlook.com>
Hi Cardoen,
> 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.
>
> Can someone assist me how to debug this issue?
I don't think the problem comes from changes in the core.
It is possibly related to one of these two commits:
b1206122069a mtd: rawnand: gpmi: use core timings instead of an empirical derivation
76e1a0086a0c mtd: rawnand: gpmi: support ->setup_data_interface()
Can you please revert the first one, check if it changes something, and
if it still fails revert also the second one?
Thanks,
Miquèl
> nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xdc
> nand: Micron MT29F4G08ABADAH4
> nand: 512 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
> gpmi-nand 1806000.gpmi-nand: enable the asynchronous EDO mode 5
> Bad block table not found for chip 0
> Bad block table not found for chip 0
> Scanning device for bad blocks
> Bad eraseblock 1692 at 0x00000d380000
> Bad eraseblock 1694 at 0x00000d3c0000
> Bad eraseblock 1696 at 0x00000d400000
> Bad eraseblock 1698 at 0x00000d440000
> Bad eraseblock 1700 at 0x00000d480000
> Bad eraseblock 1702 at 0x00000d4c0000
> Bad eraseblock 1704 at 0x00000d500000
> Bad block table written to 0x00001ffe0000, version 0x01
> Bad block table written to 0x00001ffc0000, version 0x01
> 1 cmdlinepart partitions found on MTD device gpmi-nand
> Creating 1 MTD partitions on "gpmi-nand":
> 0x000000000000-0x000020000000 : "nandflash"
> gpmi-nand 1806000.gpmi-nand: driver registered.
> ubi0: attaching mtd0
> ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB 0:0, read only 64 bytes, retry
> ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB 0:0, read only 64 bytes, retry
> ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB 0:0, read only 64 bytes, retry
> ubi0 error: 0xc02d66e8: error -74 (ECC error) while reading 64 bytes from PEB 0:0, read 64 bytes
> CPU: 0 PID: 1 Comm: swapper Not tainted 4.15.0+ #65
> Hardware name: Freescale i.MX6 Ultralite (Device Tree)
> Function entered at [<c010c0a0>] from [<c010a780>]
> Function entered at [<c010a780>] from [<c02d66ec>]
> Function entered at [<c02d66ec>] from [<c02d69e0>]
> Function entered at [<c02d69e0>] from [<c02db408>]
> Function entered at [<c02db408>] from [<c02dc8c0>]
> Function entered at [<c02dc8c0>] from [<c02d114c>]
> Function entered at [<c02d114c>] from [<c051c678>]
> Function entered at [<c051c678>] from [<c01024bc>]
> Function entered at [<c01024bc>] from [<c0500c70>]
> Function entered at [<c0500c70>] from [<c0317958>]
> Function entered at [<c0317958>] from [<c01010e8>]
> Exception stack(0xdf04dfb0 to 0xdf04dff8)
> dfa0: 00000000 00000000 00000000 00000000
> dfc0: 00000000 00000000 00000000 00000000 00000000 00000000 00000000 00000000
> dfe0: 00000000 00000000 00000000 00000000 00000013 00000000
> ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB 1:0, read only 64 bytes, retry
> ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB 1:0, read only 64 bytes, retry
> ubi0 warning: 0xc02d6658: error -74 (ECC error) while reading 64 bytes from PEB 1:0, read only 64 bytes, retry
> ubi0 error: 0xc02d66e8: error -74 (ECC error) while reading 64 bytes from PEB 1:0, read 64 bytes
> CPU: 0 PID: 1 Comm: swapper Not tainted 4.15.0+ #65
> Hardware name: Freescale i.MX6 Ultralite (Device Tree)
> Function entered at [<c010c0a0>] from [<c010a780>]
> Function entered at [<c010a780>] from [<c02d66ec>]
> Function entered at [<c02d66ec>] from [<c02d69e0>]
> Function entered at [<c02d69e0>] from [<c02db408>]
> Function entered at [<c02db408>] from [<c02dc8c0>]
> Function entered at [<c02dc8c0>] from [<c02d114c>]
> Function entered at [<c02d114c>] from [<c051c678>]
> Function entered at [<c051c678>] from [<c01024bc>]
> Function entered at [<c01024bc>] from [<c0500c70>]
> Function entered at [<c0500c70>] from [<c0317958>]
> Function entered at [<c0317958>] from [<c01010e8>]
> Exception stack(0xdf04dfb0 to 0xdf04dff8)
>
>
>
>
next parent reply other threads:[~2018-05-15 11:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <HE1PR0702MB362877849767B637814CF9B6FF930@HE1PR0702MB3628.eurprd07.prod.outlook.com>
2018-05-15 11:59 ` Miquel Raynal [this message]
[not found] ` <HE1PR0702MB36288289EA58B7D0B5368A9FFF930@HE1PR0702MB3628.eurprd07.prod.outlook.com>
2018-05-15 13:36 ` GPMI nand flash ECC errors with mainline kernel Miquel Raynal
[not found] ` <HE1PR0702MB3628CC11A1E13A0C740F1CDDFF930@HE1PR0702MB3628.eurprd07.prod.outlook.com>
[not found] ` <HE1PR0702MB36280A19BA89FA74BB3AACE8FF930@HE1PR0702MB3628.eurprd07.prod.outlook.com>
2018-05-17 12:58 ` Miquel Raynal
2018-05-17 13:05 ` Richard Weinberger
2018-05-15 13:49 ` Boris Brezillon
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=20180515135900.3bf24b98@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=P.Cardoen@TELEVIC.com \
--cc=boris.brezillon@free-electrons.com \
--cc=computersforpeace@gmail.com \
--cc=cyrille.pitchen@wedev4u.fr \
--cc=dwmw2@infradead.org \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--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 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.