linux-mtd.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Sean Nyekjaer <sean@geanix.com>
To: Sascha Hauer <s.hauer@pengutronix.de>
Cc: mkl@pengutronix.de, linux-mtd@lists.infradead.org,
	miquel.raynal@bootlin.com
Subject: Re: [Bug] mtd: rawnand: gpmi
Date: Tue, 10 Sep 2019 13:00:30 +0200	[thread overview]
Message-ID: <b26d583f-454f-fbf1-280d-f1753cc13896@geanix.com> (raw)
In-Reply-To: <20190910104807.7r3x2crdhpcteomn@pengutronix.de>



On 10/09/2019 12.48, Sascha Hauer wrote:
> 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
> 

U-boot:
=> nand erase.chip

NAND erase.chip: device 0 whole chip
Skipping bad block at  0x0c780000
Skipping bad block at  0x18000000
Skipping bad block at  0x18040000
Skipping bad block at  0x1ff00000
Skipping bad block at  0x1ff40000
Skipping bad block at  0x1ff80000
Skipping bad block at  0x1ffc0000

Look weird it marks the bbt location bad ?
Or is it a uboot feature?
I have tried another board, and uboot marks the bbt location bad on that 
as well

First boot:
[    4.149870] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xdc 
 

[    4.156589] nand: Toshiba NAND 512MiB 3,3V 8-bit
[    4.161500] nand: 512 MiB, SLC, erase size: 256 KiB, page size: 4096, 
OOB size: 128 

[    4.175918] Bad block table not found for chip 0
[    4.184059] Bad block table not found for chip 0
[    4.188808] Scanning device for bad blocks
[    4.690183] Bad eraseblock 798 at 0x00000c780000
[    5.155504] Bad eraseblock 1536 at 0x000018000000
[    5.161008] Bad eraseblock 1537 at 0x000018040000
[    5.487883] Bad block table written to 0x00001ffc0000, version 0x01 
 

[    5.498577] Bad block table written to 0x00001ff80000, version 0x01
[    5.506251] 3 fixed-partitions partitions found on MTD device 
gpmi-nand 

[    5.513214] Creating 3 MTD partitions on "gpmi-nand":
[    5.518423] 0x000000000000-0x000000800000 : "boot"
[    5.534167] 0x000000800000-0x00001ca00000 : "ubi"
[    5.906810] 0x00001ca00000-0x000020000000 : "testing"
[    5.958044] gpmi-nand 1806000.gpmi-nand: driver registered.

Second boot:
[    1.377261] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xdc 
 

[    1.377312] nand: Toshiba NAND 512MiB 3,3V 8-bit 

[    1.377363] nand: 512 MiB, SLC, erase size: 256 KiB, page size: 4096, 
OOB size: 128 

[    1.382752] random: fast init done 
 

[    1.384410] Bad block table not found for chip 0 
 

[    1.387878] Bad block table not found for chip 0
[    1.387928] Scanning device for bad blocks
[    1.900584] Bad eraseblock 798 at 0x00000c780000
[    2.373883] Bad eraseblock 1536 at 0x000018000000
[    2.374633] Bad eraseblock 1537 at 0x000018040000
[    2.705792] Bad block table written to 0x00001ffc0000, version 0x01 
 

[    2.709983] Bad block table written to 0x00001ff80000, version 0x01
[    2.711142] 3 fixed-partitions partitions found on MTD device 
gpmi-nand 

[    2.711193] Creating 3 MTD partitions on "gpmi-nand":
[    2.711313] 0x000000000000-0x000000800000 : "boot"
[    2.722427] 0x000000800000-0x00001ca00000 : "ubi"
[    3.103921] 0x00001ca00000-0x000020000000 : "testing"
[    3.152034] gpmi-nand 1806000.gpmi-nand: driver registered.

______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

  reply	other threads:[~2019-09-10 11:01 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
2019-09-10 11:00       ` Sean Nyekjaer [this message]
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=b26d583f-454f-fbf1-280d-f1753cc13896@geanix.com \
    --to=sean@geanix.com \
    --cc=linux-mtd@lists.infradead.org \
    --cc=miquel.raynal@bootlin.com \
    --cc=mkl@pengutronix.de \
    --cc=s.hauer@pengutronix.de \
    /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).