From: "Daniel Glöckner" <dg@emlix.com>
To: Miquel Raynal <miquel.raynal@bootlin.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:55:27 +0100 [thread overview]
Message-ID: <0a5497bf-7716-e8c8-7e79-7df6602d5104@emlix.com> (raw)
In-Reply-To: <20220224162958.184079e4@xps13>
Am 24.02.22 um 16:29 schrieb Miquel Raynal:
> dg@emlix.com wrote on Wed, 23 Feb 2022 11:59:02 +0100:
>> Am 22.02.22 um 23:02 schrieb Han Xu:>>> 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?
Uhm, the block is bad, broken. It shows the same behavior even after
power cycling. The other blocks are ok. I don't think it is our fault
that it died so early.
Best regards,
Daniel
--
Dipl.-Math. Daniel Glöckner, emlix GmbH, http://www.emlix.com
Fon +49 551 30664-0, Fax +49 551 30664-11,
Gothaer Platz 3, 37083 Göttingen, Germany
Sitz der Gesellschaft: Göttingen, Amtsgericht Göttingen HR B 3160
Geschäftsführung: Heike Jordan, Dr. Uwe Kracke
Ust-IdNr.: DE 205 198 055
emlix - your embedded linux partner
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/
next prev parent reply other threads:[~2022-02-24 15:56 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
2022-02-24 15:55 ` Daniel Glöckner [this message]
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=0a5497bf-7716-e8c8-7e79-7df6602d5104@emlix.com \
--to=dg@emlix.com \
--cc=LW@KARO-electronics.de \
--cc=computersforpeace@gmail.com \
--cc=han.xu@nxp.com \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.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