* Problems with JFFS2/MTD upgrade to latest in CVS.
@ 2001-06-26 22:23 Vipin Malik
2001-06-26 22:26 ` David Woodhouse
0 siblings, 1 reply; 5+ messages in thread
From: Vipin Malik @ 2001-06-26 22:23 UTC (permalink / raw)
To: David Woodhouse; +Cc: jffs-dev, MTD for Linux
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
....
....
....
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with JFFS2/MTD upgrade to latest in CVS.
2001-06-26 22:23 Problems with JFFS2/MTD upgrade to latest in CVS Vipin Malik
@ 2001-06-26 22:26 ` David Woodhouse
2001-06-26 23:06 ` Vipin Malik
0 siblings, 1 reply; 5+ messages in thread
From: David Woodhouse @ 2001-06-26 22:26 UTC (permalink / raw)
To: Vipin Malik; +Cc: jffs-dev, nico, MTD for Linux
vipin.malik@daniel.com 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with JFFS2/MTD upgrade to latest in CVS.
2001-06-26 22:26 ` David Woodhouse
@ 2001-06-26 23:06 ` Vipin Malik
2001-07-02 8:35 ` David Woodhouse
0 siblings, 1 reply; 5+ messages in thread
From: Vipin Malik @ 2001-06-26 23:06 UTC (permalink / raw)
To: David Woodhouse; +Cc: jffs-dev, nico, MTD for Linux
>
> > 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with JFFS2/MTD upgrade to latest in CVS.
2001-06-26 23:06 ` Vipin Malik
@ 2001-07-02 8:35 ` David Woodhouse
2001-07-02 16:00 ` Nicolas Pitre
0 siblings, 1 reply; 5+ messages in thread
From: David Woodhouse @ 2001-07-02 8:35 UTC (permalink / raw)
To: Vipin Malik; +Cc: jffs-dev, nico, MTD for Linux
vipin.malik@daniel.com said:
> > > 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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Problems with JFFS2/MTD upgrade to latest in CVS.
2001-07-02 8:35 ` David Woodhouse
@ 2001-07-02 16:00 ` Nicolas Pitre
0 siblings, 0 replies; 5+ messages in thread
From: Nicolas Pitre @ 2001-07-02 16:00 UTC (permalink / raw)
To: David Woodhouse; +Cc: Vipin Malik, jffs-dev, MTD for Linux
On Mon, 2 Jul 2001, David Woodhouse wrote:
>
> vipin.malik@daniel.com said:
> > > > 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
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2001-07-02 15:55 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2001-06-26 22:23 Problems with JFFS2/MTD upgrade to latest in CVS Vipin Malik
2001-06-26 22:26 ` David Woodhouse
2001-06-26 23:06 ` Vipin Malik
2001-07-02 8:35 ` David Woodhouse
2001-07-02 16:00 ` Nicolas Pitre
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox