public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Miquel Raynal <miquel.raynal@bootlin.com>
To: "Daniel Glöckner" <dg@emlix.com>
Cc: "Han Xu" <han.xu@nxp.com>,
	linux-mtd@lists.infradead.org,
	"Lothar Waßmann" <LW@KARO-electronics.de>,
	"Brian Norris" <computersforpeace@gmail.com>
Subject: Re: Make NAND_BBT_NO_OOB_BBM configurable or let the gpmi driver decide?
Date: Thu, 24 Feb 2022 16:29:58 +0100	[thread overview]
Message-ID: <20220224162958.184079e4@xps13> (raw)
In-Reply-To: <3b9d1eb5-1fd7-7aab-b2b9-7cbfda8831b8@emlix.com>

Hi Daniel,

dg@emlix.com wrote on Wed, 23 Feb 2022 11:59:02 +0100:

> Am 22.02.22 um 23:02 schrieb Han Xu:
> > On 22/02/21 08:00PM, Daniel Glöckner wrote:  
> >> we are using UBI on a NAND flash with BBT and have recently observed
> >> bad blocks where nand_markbad_bbm returns an error. Since that error is
> >> returned by nand_block_markbad_lowlevel even when marking the block in
> >> the BBT succeeds, UBI goes into read-only mode. We would therefore like
> >> to set NAND_BBT_NO_OOB_BBM.  
> > 
> > Could you please describe more details about what kind of error, how to
> > reproduce it and on which kernel version?  
> 
> You need a flash that has one bad block where programming the BBM sets
> NAND_STATUS_FAIL in its status register. The latest kernels should still
> have problems when this happens in a UBI.

I believe we should try to tackle "why" this happens more than try to
workaround its consequences. Can you give more details about why we get
this status?


Thanks,
Miquèl

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

  reply	other threads:[~2022-02-24 15:30 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-21 19:00 Make NAND_BBT_NO_OOB_BBM configurable or let the gpmi driver decide? Daniel Glöckner
2022-02-22 22:02 ` Han Xu
2022-02-23 10:59   ` Daniel Glöckner
2022-02-24 15:29     ` Miquel Raynal [this message]
2022-02-24 15:55       ` Daniel Glöckner
2022-02-24 16:03         ` Miquel Raynal
2022-02-24 18:17           ` Daniel Glöckner
2022-03-14 15:45             ` Miquel Raynal
2022-03-15  7:06               ` Lothar Waßmann
2022-03-15  8:34                 ` 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=20220224162958.184079e4@xps13 \
    --to=miquel.raynal@bootlin.com \
    --cc=LW@KARO-electronics.de \
    --cc=computersforpeace@gmail.com \
    --cc=dg@emlix.com \
    --cc=han.xu@nxp.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