Altera_Forum
Honored Contributor
11 years agofacing problem in mounting the jffs2 in linux 2.6.33.7
hi all,
i am trying to mount the rootfs.jffs2 for mpc8309twr board i have successfully created the image and wrote the image to MX29GL256E nor flash using u-boot 2010 and i have given the bootargs as bootargs=root=/dev/mtdblock1 rootfstype=jffs2 rw console=ttyS0,115200 when i run the kernel and dtb the repeatedly i am getting meaasges like jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000000: 0x2705 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000004: 0x7054 instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x00000008: 0x4efa instead jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x0000000c: 0x001e instead and Further such events for this erase block will not be printed Old JFFS2 bitmask found at 0x00033be8 You cannot use older JFFS2 filesystems with newer kernels and Empty flash at 0x001e9058 ends at 0x001e905c Empty flash at 0x001e912c ends at 0x001e9130 Empty flash at 0x001e9a40 ends at 0x001e9a44 Empty flash at 0x001e9d90 ends at 0x001e9d94 Empty flash at 0x001ea334 ends at 0x001ea338 soon..... after that it ends at Cowardly refusing to erase blocks on filesystem with no valid JFFS2 nodes empty_blocks 16, bad_blocks 0, c->nr_blocks 32 VFS: Cannot open root device "mtdblock1" or unknown-block(31,1) Please append a correct "root=" boot option; here are the available partitions: 1f00 1024 mtdblock0 (driver?) 1f01 4096 mtdblock1 (driver?) 1f02 2048 mtdblock2 (driver?) 1f03 1024 mtdblock3 (driver?) Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(31,1) Call Trace: [c782dee0] [c0008484] 0xc0008484 (unreliable) [c782df10] [c002587c] 0xc002587c [c782df60] [c0335b5c] 0xc0335b5c [c782dfb0] [c0335dac] 0xc0335dac [c782dfd0] [c033525c] 0xc033525c [c782dff0] [c0011994] 0xc0011994 Rebooting in 180 seconds.. i am not getting the exact reason of this behavior of my kernel can any one help me from this :( please find the attachment of problem_case.txt which contains the kernel logs. thanks in advance, K.Praveen.