From: Wolfgang Grandegger <wg@grandegger.com>
To: linux-mtd@lists.infradead.org
Subject: i.MX28 nand driver broken in Linux 4.18
Date: Fri, 8 Feb 2019 10:27:19 +0100 [thread overview]
Message-ID: <8ec3f0b1-b288-d208-c0e4-431b49719d08@grandegger.com> (raw)
Hello,
I'm upgrading the BSP of my i.MX28 board to Linux 4.18. Unfortunately,
the NAND driver does not working any longer. Here is the output of
"nandtest" including the kernel messages:
root@m28evk:~# nandtest -k /dev/mtd3
ECC corrections: 0
ECC failures : 0
Bad blocks : 0
BBT blocks : 0
00000000: reading (2 of 4)...gpmi-nand 8000c000.gpmi-nand: DMA timeout, last DMA
gpmi-nand 8000c000.gpmi-nand: Show GPMI registers :
gpmi-nand 8000c000.gpmi-nand: offset 0x000 : 0x2180083e
gpmi-nand 8000c000.gpmi-nand: offset 0x010 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x020 : 0x000011ff
gpmi-nand 8000c000.gpmi-nand: offset 0x030 : 0x0000083e
gpmi-nand 8000c000.gpmi-nand: offset 0x040 : 0x44dc0800
gpmi-nand 8000c000.gpmi-nand: offset 0x050 : 0x46800800
gpmi-nand 8000c000.gpmi-nand: offset 0x060 : 0x0104000c
gpmi-nand 8000c000.gpmi-nand: offset 0x070 : 0x00010101
gpmi-nand 8000c000.gpmi-nand: offset 0x080 : 0x90000000
gpmi-nand 8000c000.gpmi-nand: offset 0x090 : 0x09020101
gpmi-nand 8000c000.gpmi-nand: offset 0x0a0 : 0x01000030
gpmi-nand 8000c000.gpmi-nand: offset 0x0b0 : 0x0f000003
gpmi-nand 8000c000.gpmi-nand: offset 0x0c0 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x0d0 : 0x03010000
gpmi-nand 8000c000.gpmi-nand: Show BCH registers :
gpmi-nand 8000c000.gpmi-nand: offset 0x000 : 0x00000100
gpmi-nand 8000c000.gpmi-nand: offset 0x010 : 0x0000fe04
gpmi-nand 8000c000.gpmi-nand: offset 0x020 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x030 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x040 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x050 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x060 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x070 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x080 : 0x030a4200
gpmi-nand 8000c000.gpmi-nand: offset 0x090 : 0x083e4200
gpmi-nand 8000c000.gpmi-nand: offset 0x0a0 : 0x070a8200
gpmi-nand 8000c000.gpmi-nand: offset 0x0b0 : 0x10da8200
gpmi-nand 8000c000.gpmi-nand: offset 0x0c0 : 0x070a8200
gpmi-nand 8000c000.gpmi-nand: offset 0x0d0 : 0x10da8200
gpmi-nand 8000c000.gpmi-nand: offset 0x0e0 : 0x070a8200
gpmi-nand 8000c000.gpmi-nand: offset 0x0f0 : 0x10da8200
gpmi-nand 8000c000.gpmi-nand: offset 0x100 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x110 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x120 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x130 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x140 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: offset 0x150 : 0x20484342
gpmi-nand 8000c000.gpmi-nand: offset 0x160 : 0x01000000
gpmi-nand 8000c000.gpmi-nand: offset 0x170 : 0x00000000
gpmi-nand 8000c000.gpmi-nand: BCH Geometry :
GF length : 13
ECC Strength : 8
Page Size in Bytes : 2110
Metadata Size in Bytes : 10
ECC Chunk Size in Bytes: 512
ECC Chunk Count : 4
Payload Size in Bytes : 2048
Auxiliary Size in Bytes: 16
Auxiliary Status Offset: 12
Block Mark Byte Offset : 1999
Block Mark Bit Offset : 0
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Error in ECC-based read: -22
00000000: reading (3 of 4)...gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Error in ECC-based read: -22
00000000: reading (4 of 4)...gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Error in ECC-based read: -22
00000000: erasing... gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
00000000: writing...gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Chip: 0, Error -22
gpmi-nand 8000c000.gpmi-nand: Error in ECC-based write: -22
write: Invalid argument
...
I have already applied the patch:
[PATCH] mtd: rawnand: gpmi: fix MX28 bus master lockup problem
but it didn't help. It works fine with Linux 4.14. Are there any known
issues with 4.18?
Thanks,
Wolfgang.
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next reply other threads:[~2019-02-08 9:27 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-08 9:27 Wolfgang Grandegger [this message]
2019-03-04 11:54 ` i.MX28 nand driver broken in Linux 4.18 Miquel Raynal
2019-03-04 20:46 ` Wolfgang Grandegger
2019-03-05 14:52 ` Wolfgang Grandegger
2019-03-06 13:59 ` Miquel Raynal
2019-03-23 19:55 ` Wolfgang Grandegger
2019-04-01 9:23 ` Miquel Raynal
2019-04-01 20:08 ` Wolfgang Grandegger
2019-04-02 9:16 ` Miquel Raynal
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=8ec3f0b1-b288-d208-c0e4-431b49719d08@grandegger.com \
--to=wg@grandegger.com \
--cc=linux-mtd@lists.infradead.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 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).