From: hejianet <hejianet@linux.vnet.ibm.com>
To: linux-mtd@lists.infradead.org
Subject: Re: [question]MTD:unstable bit issues?
Date: Wed, 24 Oct 2012 17:21:08 +0800 [thread overview]
Message-ID: <5087B304.8010903@linux.vnet.ibm.com> (raw)
In-Reply-To: <OF4005835E.007816E8-ONC1257AA1.0030E2F0-C1257AA1.003189CF@rohde-schwarz.com>
Hi Thomas
till now, we have no evidence that it is a jffs2.
we only observed a ubi error msg(not 100% sure it caused this hole):
Oct 15 20:09:10 (none) kernel: UBI error: ubi_io_write error -5 while writing 2048 bytes to PEB 1663:20480, written 0 bytes
Besides, it only appeared in power-cut stress cut, so I suspect it is relevant
to "unstable bits issue". from google information, this issue appears in both
nand and nor flash, but more frequently in nand.
On 2012-10-24 17:01, Thomas.Betker@rohde-schwarz.com wrote:
> Hello Jia:
>
>> Yes, we use jffs2.
>> How did u solve your bug? :)
>>>> -----------------------------------------------------
>>>> 2)a 4k bytes hole with all 0 in the flash file.
>>>> -----------------------------------------------------
> Unfortunately, we didn't solve it. Some day, it was simply gone; I have no
> idea what had changed. I couldn't reproduce it anymore, so I couldn't do
> any further analysis.
>
> Anyway, most likely this is not a NAND issue or MTD issue, but a JFFS2
> issue. And I would certainly want to hear about it if you manage to find
> and fix it ...
>
> Best regards,
> Thomas
>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>
>
>
next prev parent reply other threads:[~2012-10-24 9:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 5:14 [question]MTD:unstable bit issues? hejianet
2012-10-24 8:13 ` Thomas.Betker
2012-10-24 8:52 ` hejianet
2012-10-24 9:01 ` Thomas.Betker
2012-10-24 9:21 ` hejianet [this message]
2012-11-12 15:39 ` Artem Bityutskiy
2012-10-24 9:53 ` Jamie Lokier
2012-11-12 15:37 ` Artem Bityutskiy
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=5087B304.8010903@linux.vnet.ibm.com \
--to=hejianet@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.