linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
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 12:48:07 +0200	[thread overview]
Message-ID: <20190910104807.7r3x2crdhpcteomn@pengutronix.de> (raw)
In-Reply-To: <a0f518e3-2465-8e64-418b-cac27cde98de@geanix.com>

On Tue, Sep 10, 2019 at 12:18:25PM +0200, Sean Nyekjaer wrote:
> 
> 
> On 10/09/2019 11.55, Sascha Hauer wrote:
> > > [    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
> 
> Not exactly sure what you mean, but here is the dumps:
> 
> Before (mtd: rawnand: gpmi: Implement exec_op)
> [    3.389352] Bad block table written to 0x00001ffc0000, version 0x01
> [    3.399019] Bad block table written to 0x00001ff80000, version 0x01
> 
> After
> [    3.301096] Bad block table written to 0x00001ffc0000, version 0x01
> [    3.310599] Bad block table written to 0x00001ff80000, version 0x01

The Bad block table is written once. When you see this message multiple
times then this means that Linux can't read the BBT and writes it again.
So the question is: Start the good kernel multiple times. Do you see
this message once or on each boot? Then start the bad Kernel multiple
times. Do you see the message once or on each boot?

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/

  reply	other threads:[~2019-09-10 10:48 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
2019-09-10 10:18   ` Sean Nyekjaer
2019-09-10 10:48     ` Sascha Hauer [this message]
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=20190910104807.7r3x2crdhpcteomn@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).