Hello

This is a bug report concerning the erase-block-summary (EBS) feature:

We're using JFFS2 as our root filesystem on our embedded device. Our 
device is a custom hardware based around a Hynix ARM H7202 processor. 
We're using Intel Strata Flash (NOR). See any of the attached kernel log 
files for more information.

JFFS2 works fine so far (without EBS). We hope to improve the mount time 
with the EBS feature. We're currently using the 2.6.13 kernel, and I 
patched the MTD subsystem with a current version of the MTD CVS 
(09-09-2005). The patched kernel boots happily when EBS is disable, both 
with sumtool-processed images and with normal non-processed images. (see 
without-ebs-with-sumtool.txt and without-ebs-without-sumtool.txt logfiles).

As soon as I enable EBS I get a kernel panic (see 
with-ebs-with-sumtool.txt logfile). I'm pretty sure that the image is 
not corrupt, as the first two tests with EBS disable show. Also, I'm 
using a script to upload new kernel and rootfs images. So there should 
not have been anything gone wrong during the copy process!

Here are the steps I used to build the root filesystem:

mkfs.jffs2 -p 6291456 -d ./rootfs -e 128KiB -l -v -U -D 
./devicetable.txt -o ./rootfs.tmp
sumtool -i ./rootfs.tmp -o ./rootfs.img -e 128KiB -l -v

If you need more information, just let me know.

Best regards,
Simon Kallweit