From: Miquel Raynal <miquel.raynal@bootlin.com>
To: Kostya Porotchkin <kostap@marvell.com>
Cc: Daniel Mack <daniel@zonque.org>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Richard Weinberger <richard@nod.at>,
linux-mtd@lists.infradead.org,
David Woodhouse <dwmw2@infradead.org>,
Brian Norris <computersforpeace@gmail.com>,
Marek Vasut <marek.vasut@gmail.com>,
Mike Dunn <mikedunn@newsguy.com>,
Sergey Larin <cerg2010cerg2010@mail.ru>
Subject: Re: [EXT] Re: nand speed test
Date: Mon, 20 Aug 2018 09:46:30 +0200 [thread overview]
Message-ID: <20180820094630.392f050f@xps13> (raw)
In-Reply-To: <1c78935418904123a9cc27a65ec9d3e4@IL-EXCH02.marvell.com>
Hi Kostya,
Kostya Porotchkin <kostap@marvell.com> wrote on Sun, 19 Aug 2018
14:12:16 +0000:
> Hi, Miguel,
>
> We clearly have a problem with BBT on this 8K-page NAND.
> The Linux driver is unable to find BBT after reboot, even if it reports that the new table was written upon previous boot.
> It looks like the u-boot also lost the BBT information after reboot.
> So something is not yet working well with this 4GB device.
>
> Marvell>> nand info
>
> Device 0: nand0, sector size 1024 KiB
> Page size 8192 b
> OOB size 448 b
> Erase size 1048576 b
> subpagesize 8192 b
> options 0x 200
> bbt options 0x a0000
> Marvell>> nand bad
>
> Device 0 bad blocks:
> ff800000
> ff900000
> ffa00000
> ffb00000
> ffc00000
> ffd00000
> ffe00000
> fff00000
This enlarging list is very likely to show a mismatch between U-Boot
and Linux ECC configuration, you should check that first. It will
probably explain why BBT is not recognized.
Thanks,
Miquèl
next prev parent reply other threads:[~2018-08-20 7:46 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-04 20:59 [PATCH v2 1/4] mtd: rawnand: Remove docg4 Boris Brezillon
2018-08-04 20:59 ` [PATCH v2 2/4] ARM: pxa: palmtreo: Drop docg4 specific init Boris Brezillon
2018-08-19 19:38 ` Robert Jarzmik
2018-09-04 20:57 ` Miquel Raynal
2018-09-09 19:11 ` Robert Jarzmik
[not found] ` <1c78935418904123a9cc27a65ec9d3e4@IL-EXCH02.marvell.com>
2018-08-20 7:46 ` Miquel Raynal [this message]
2018-08-20 7:50 ` [EXT] Re: nand speed test Kostya Porotchkin
2018-08-04 20:59 ` [PATCH v2 3/4] mtd: rawnand: Make maxchips an unsigned int Boris Brezillon
2018-08-04 20:59 ` [PATCH v2 4/4] mtd: rawnand: Do not treat !maxchips specially in nand_scan_with_ids() Boris Brezillon
2018-08-05 19:12 ` [PATCH v2 1/4] mtd: rawnand: Remove docg4 Robert Jarzmik
2018-08-05 19:51 ` Boris Brezillon
2018-09-06 20:12 ` 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=20180820094630.392f050f@xps13 \
--to=miquel.raynal@bootlin.com \
--cc=cerg2010cerg2010@mail.ru \
--cc=computersforpeace@gmail.com \
--cc=daniel@zonque.org \
--cc=dwmw2@infradead.org \
--cc=haojian.zhuang@gmail.com \
--cc=kostap@marvell.com \
--cc=linux-mtd@lists.infradead.org \
--cc=marek.vasut@gmail.com \
--cc=mikedunn@newsguy.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 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).