On Mon, Jun 11, 2012 at 12:50 PM, Ming Lei <ming.lei@xxxxxxxxxxxxx> wrote: > On Mon, Jun 11, 2012 at 2:21 PM, T Krishnamoorthy, Balaji > <balajitk@xxxxxx> wrote: >> Hi Ming Lei, >> Can you let me know if you noticed any write/timeout errors ? > > Nothing error logs found during writing. > > Below is one of my test case. > > root@beagleboard:~# upk > updateing kernel... > flush storage... > root@beagleboard:~# cat bin/upk > #!/bin/sh > > echo "updateing kernel..." > cp -f /mnt/nfs/t/uImage /media/mmcblk0p1/ > > echo "flush storage..." > sync > root@beagleboard:~# diff /mnt/nfs/t/uImage /media/mmcblk0p1/uImage > Binary files /mnt/nfs/t/uImage and /media/mmcblk0p1/uImage differ > root@beagleboard:~# umount /media/mmcblk0p1 > root@beagleboard:~# mount -t vfat /dev/mmcblk0p1 /media/mmcblk0p1 > root@beagleboard:~# > root@beagleboard:~# > root@beagleboard:~# diff /mnt/nfs/t/uImage /media/mmcblk0p1/uImage > Binary files /mnt/nfs/t/uImage and /media/mmcblk0p1/uImage differ > Ming, Just to keep you posted, Balaji and myself are trying to reproduce the issue and haven't hit the problem yet. This patch was in use internaly for sometime before we sent it upstream. Meanwhile, is is possible for you to reproduce this problem with MMC_DEBUG enabled ? That would be helpful. ~Venkat. -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
