From: Holger Schurig <h.schurig@mn-logistik.de>
To: "George G. Davis" <gdavis@mvista.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: mkfs.jffs2 buggy?
Date: Fri, 31 Jan 2003 17:06:20 +0100 [thread overview]
Message-ID: <200301311706.20580.h.schurig@mn-logistik.de> (raw)
In-Reply-To: <3E3A9B1F.F97D9D28@mvista.com>
> > 0x6574
>
> 'At'
>
> > 0x665f
>
> 'b_'
>
> > 0x6873
>
> 'hs'
>
> > 0x3030
>
> '00'
>
> > 0x3030
>
> '00'
>
> Hmm, is that interesting or merely a coincidence?
I think this is a conincidence.
From my flash-tester I had in every sector a text like this:
bdi>mdb 0x00a00000
00a00000 : 74 65 73 74 5f 66 6c 61 test_fla
00a00008 : 73 68 3a 20 30 30 61 30 sh: 00a0
00a00010 : 30 30 30 30 ff ff ff ff 0000....
00a00018 : ff ff ff ff ff ff ff ff ........
bdi>mdb 0x00a00000
00a40000 : 74 65 73 74 5f 66 6c 61 test_fla
00a40008 : 73 68 3a 20 30 30 61 34 sh: 00a4
00a40010 : 30 30 30 30 ff ff ff ff 0000....
00a40018 : ff ff ff ff ff ff ff ff ........
I used this to make sure that each sector get's address indeed, and that no
overwrapping happens, e.g. by bad soldered address lines.
However, the found characters can't be from those sectors, so it looks very
much like a conincidence. My memory area looks, in the flash, currently like
this:
00000 40000 80000 c0000
00000000: used used used used
00100000: test jffs jffs jffs
00200000: jffs jffs jffs jffs
00300000: jffs jffs jffs jffs
00400000: jffs jffs jffs jffs
00500000: jffs jffs jffs jffs
00600000: jffs jffs jffs jffs
00700000: jffs jffs jffs jffs
00800000: jffs jffs jffs jffs
00900000: jffs jffs jffs test
00a00000: test test test test
00b00000: test test test test
00c00000: test test test test
00d00000: test test test test
00e00000: test test test test
00f00000: test test test test
01000000: test test test test
01100000: test test test test
01200000: test test test test
01300000: test test test test
01400000: test test test test
01500000: test test test test
01600000: test test test test
01700000: test test test test
01800000: test test test test
01900000: test test test test
01a00000: test test test test
01b00000: test test test test
01c00000: test test test test
01d00000: test test test test
01e00000: test test test test
01f00000: test test test test
test: means that a valid test mark like above has been found
jffs: means that in the first byte I found 0x85 and in the second 0x19
free: the whole page contained \xFF
used: the page contained other stuff
prev parent reply other threads:[~2003-01-31 15:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-31 14:31 mkfs.jffs2 buggy? Holger Schurig
2003-01-31 15:49 ` George G. Davis
2003-01-31 16:06 ` Holger Schurig [this message]
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=200301311706.20580.h.schurig@mn-logistik.de \
--to=h.schurig@mn-logistik.de \
--cc=gdavis@mvista.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