From: hejianet <hejianet@linux.vnet.ibm.com>
To: linux-mtd@lists.infradead.org, Thomas.Betker@rohde-schwarz.com
Subject: Re: [question]MTD:unstable bit issues?
Date: Wed, 24 Oct 2012 16:52:40 +0800 [thread overview]
Message-ID: <5087AC58.1000402@linux.vnet.ibm.com> (raw)
In-Reply-To: <OFCD7F9EAE.28A631AD-ONC1257AA1.002B4604-C1257AA1.002D248C@rohde-schwarz.com>
Hi Thomas
Yes, we use jffs2.
How did u solve your bug? :)
On 2012-10-24 16:13, Thomas.Betker@rohde-schwarz.com wrote:
> Hello Jia:
>
>> -----------------------------------------------------
>> 2)a 4k bytes hole with all 0 in the flash file.
>> -----------------------------------------------------
>> -original-file DD AF C8 EE 57 EB 84 CE A1 7F B1 38 E7 22 51 2F
>> - 94 AE 77 5B 48 EA 61 8C 09 BB C5 74 6E B1 87 D2
>> - A9 32 8D 2A E7 7F D2 C3 DB 1A 92 E7 66 7C B8 4E
>> ......
>>
>> +file-in-flash 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> + 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>> ......
>> -----------------------------------------------------
> We have also seen this "4k zeros" issue for some time. I never found out
> was was happening because the issue was suddenly no longer reproducible.
> :-(
>
> In our case, though, we didn't have NAND flash, but JFFF2 with serial NOR
> flash. So I would guess that this is not a NAND problem.
>
> Which file system do you run? Is it JFFS2?
>
> 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 8:53 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 [this message]
2012-10-24 9:01 ` Thomas.Betker
2012-10-24 9:21 ` hejianet
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=5087AC58.1000402@linux.vnet.ibm.com \
--to=hejianet@linux.vnet.ibm.com \
--cc=Thomas.Betker@rohde-schwarz.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