Skip to contentSkip to conversation

Problems with JFFS2/MTD upgrade to latest in CVS.

DISCUSSION Vipin Malik 3 participants 5 messages Jun 26, 2001 – Jul 2, 2001 Memory technology devices (MTD)

lore
Share & tools
lore
#0 lore raw

Hmm, I upgraded from an <older> version (before the dir change)of JFFS2 & MTD (that I've been testing) to the latest one in CVS
and to the 2.4.5 kernel.

When I mounted my JFFS2 flash partition again, I got the following on the console.
Now the system periodically does not respond for multiple "seconds" to CR's on the bash prompt.

What's going on?

Vipin

jffs2_scan_empty(): Empty block at 0x00000000 ends at 0x00000000 (with 0x00031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00080000 ends at 0x00080000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x000c0000 ends at 0x000c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00100000 ends at 0x00100000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00140000 ends at 0x00140000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00180000 ends at 0x00180000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x001c0000 ends at 0x001c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00200000 ends at 0x00200000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00240000 ends at 0x00240000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00280000 ends at 0x00280000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x002c0000 ends at 0x002c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00300000 ends at 0x00300000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00340000 ends at 0x00340000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00380000 ends at 0x00380000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x003c0000 ends at 0x003c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00400000 ends at 0x00400000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00440000 ends at 0x00440000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00480000 ends at 0x00480000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x004c0000 ends at 0x004c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00500000 ends at 0x00500000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00540000 ends at 0x00540000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00580000 ends at 0x00580000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x005c0000 ends at 0x005c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00600000 ends at 0x00600000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00640000 ends at 0x00640000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00680000 ends at 0x00680000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x006c0000 ends at 0x006c0000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00700000 ends at 0x00700000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00740000 ends at 0x00740000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x00780000 ends at 0x00780000 (with 0x20031985)! Marking dirty
jffs2_scan_empty(): Empty block at 0x007c0000 ends at 0x007c0000 (with 0x00031985)! Marking dirty
Waiting for chip to read, status = 4
Waiting for chip to read, status = 4
Waiting for chip to read, status = 7
Waiting for chip to read, status = 4
Waiting for chip to read, status = 7
Waiting for chip to read, status = 4
Waiting for chip to read, status = 4
Waiting for chip to read, status = 4
....
....
....

#1 lore raw
Quoted 11 lines · [email protected] said:

Hmm, I upgraded from an <older> version (before the dir change)of JFFS2 & MTD (that I've been testing) to the latest one in CVS and to the 2.4.5 kernel.

When I mounted my JFFS2 flash partition again, I got the following on the console. Now the system periodically does not respond for multiple "seconds" to CR's on the bash prompt.

What's going on?

jffs2_scan_empty(): Empty block at 0x00000000 ends at 0x00000000 (with 0x00031985)! Marking dirty

Does reverting to an older version of scan.c fix this?

	cvs up -r 1.46 scan.c 

--
dwmw2

#2 lore raw
Quoted 9 lines
Quoted 4 lines

What's going on?

jffs2_scan_empty(): Empty block at 0x00000000 ends at 0x00000000 (with 0x00031985)! Marking dirty

Does reverting to an older version of scan.c fix this?

        cvs up -r 1.46 scan.c

Yes!

Vipin

#3 lore raw
Quoted 6 lines · [email protected] said:
Quoted 4 lines
Quoted 1 line

jffs2_scan_empty(): Empty block at 0x00000000 ends at 0x00000000 (with 0x00031985)! Marking dirty

Does reverting to an older version of scan.c fix this?

        cvs up -r 1.46 scan.c

Yes!

Nicolas - should I just revert to 1.46? Is there anything in 1.48 you'd like to (fix and) keep?

----------------------------
revision 1.48
date: 2001/06/13 23:01:47; author: nico; state: Exp; lines: +9 -3 OK... We can't be sure that empty blocks are actually fully erased. Queue them for erase again. (sigh)
----------------------------
revision 1.47
date: 2001/06/13 20:44:16; author: nico; state: Exp; lines: +21 -7 If flash does not contain any JFFS2 node, don't touch it as before. If flash is entirely empty, then go ahead now.
This also speeds up mount on partially erased flash since completely empty flash blocks aren't erased unnecessarily.

--
dwmw2

#4 lore raw
Quoted 11 lines · David Woodhouse
Quoted 6 lines · [email protected] said:
Quoted 4 lines
Quoted 1 line

jffs2_scan_empty(): Empty block at 0x00000000 ends at 0x00000000 (with 0x00031985)! Marking dirty

Does reverting to an older version of scan.c fix this?

        cvs up -r 1.46 scan.c

Yes!

Nicolas - should I just revert to 1.46? Is there anything in 1.48 you'd like to (fix and) keep?

Well... What's the problem already? I fear I didn't follow the conversation closely enough lately.

Nicolas