From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sean Nyekjaer <sean@geanix.com>
Cc: mkl@pengutronix.de, linux-mtd@lists.infradead.org,
miquel.raynal@bootlin.com
Subject: Re: [Bug] mtd: rawnand: gpmi
Date: Tue, 10 Sep 2019 11:55:15 +0200 [thread overview]
Message-ID: <20190910095515.yjg6zcoqrtwylyg3@pengutronix.de> (raw)
In-Reply-To: <6a333d0f-09b2-d0d1-a3a5-955b31b6291e@geanix.com>
On Thu, Sep 05, 2019 at 10:26:06PM +0200, Sean Nyekjaer wrote:
> Hi,
>
> I have been troubleshooting some CAN problems on our imx6ull with a raw nand
> flash.
> I normally run with a 4.19 series kernel, but to verify those CAN problems
> have been resolved in newer kernels i have been trying ~5.3-rc6.
>
> [ 1.231060] ---[ end trace 12b9d19a5aac4c9f ]---
> [ 1.234710] Bad block table not found for chip 0
> [ 1.236076] Bad block table not found for chip 0
> [ 1.236113] Scanning device for bad blocks
> [ 1.244907] random: fast init done
> [ 1.701764] Bad eraseblock 798 at 0x00000c780000
> [ 2.132734] Bad eraseblock 1536 at 0x000018000000
> [ 2.133094] Bad eraseblock 1537 at 0x000018040000
> [ 2.434057] Bad block table written to 0x00001ffc0000, version 0x01
> [ 2.437254] Bad block table written to 0x00001ff80000, version 0x01
What about this "Bad block table written" message? You should see this
exactly once. Do you see this multiple times, especially when switching
kernels between the good one and the bad one?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2019-09-10 9:55 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-05 20:26 [Bug] mtd: rawnand: gpmi Sean Nyekjaer
2019-09-05 20:39 ` Marc Kleine-Budde
[not found] ` <E8555824-943E-45B4-A0ED-D42E13156EEC@geanix.com>
2019-09-06 7:01 ` Marc Kleine-Budde
2019-09-06 7:12 ` Sascha Hauer
2019-09-06 9:59 ` Sean Nyekjaer
2019-09-06 10:13 ` Sascha Hauer
2019-09-06 11:06 ` Sean Nyekjaer
2019-09-06 13:28 ` Sascha Hauer
2019-09-06 15:05 ` Sean Nyekjaer
2019-09-10 9:55 ` Sascha Hauer [this message]
2019-09-10 10:18 ` Sean Nyekjaer
2019-09-10 10:48 ` Sascha Hauer
2019-09-10 11:00 ` Sean Nyekjaer
2019-09-10 11:08 ` Sascha Hauer
2019-09-10 11:51 ` Sean Nyekjaer
2019-09-19 11:21 ` Sean Nyekjaer
2019-09-19 11:27 ` Miquel Raynal
2019-09-19 12:15 ` Sean Nyekjaer
2019-09-20 6:54 ` Sean Nyekjaer
2019-09-20 9:17 ` Sascha Hauer
2019-09-23 10:37 ` Sean Nyekjaer
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=20190910095515.yjg6zcoqrtwylyg3@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=mkl@pengutronix.de \
--cc=sean@geanix.com \
/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).