Hi Jason,
2010/12/24 Ming Lei <[email protected]>:
> 2010/12/24 Ming Lei <[email protected]>:
>> Hi,
>>
>> 2010/12/24 Charles Manning <[email protected]>:
>>
>>> THis might be due to the way the omap2.c driver is now screwed up so that it
>>> does not read when not u32 aligned.
>>>
>>> Try this:
>>> http://www.spinics.net/linux/lists/linux-omap/msg42422.html
>>>
>>> Please report back if that fixes the problem for you.
>>
>> No, the patch doesn't fix the issue.
>
> #mount -t jffs2 /dev/mtdblock4 /mnt/cf
>
> mount: /dev/mtdblock4: can't read superblock
>
> [ 41.216796] nand_do_read_oob: Attempt to read past end of page
> [ 41.216827] cannot read OOB for EB at 00000000, requested 152
> bytes, read 0 bytes, error -22
When I revert the patch below from Jason,
http://marc.info/?l=linux-kernel&m=129015697513966&w=2
mount will be OK but with some info printed, see below:
r...@beagleboard:~# mount -t jffs2 /dev/mtdblock4 /mnt/cf
[ 39.662963] JFFS2 notice: (1324) jffs2_build_xattr_subsystem:
complete building xattr subsystem, 0
of xdatum (0 unchecked, 0 orphan) and 0 of xref (0 dead, 0 orphan) found.
#mount
......
/dev/mtdblock4 on /media/cf type jffs2 (rw,relatime)
So seems the patch from Jason does cause the issue, maybe should be
dropped or fixed further.
thanks,
--
Lei Ming
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
